-
Bug
-
Resolution: Fixed
-
Normal
-
FP-Akka-1.4.1
-
None
-
None
Bob tested FP-Akka 1.4.2 on a 1000 record USNM data set and found that it didn't complete. Underlying cause appears to be that the data set doesn't contain an eventDate (though it does contain year/month/day terms), so that null pointer exceptions are thrown.
At least 2 issues here, one is the starvation of PullRequestor (need for a contract for behavior of actors that are composed with PullRequestor), the other handling of records where atomic date fields are included but eventDate is not (or generally the behavior of actors when the fields they expect aren't present in the data).
[ERROR] [06/09/2015 09:46:57.145] [FpSystem-akka.actor.default-dispatcher-6] [akka://FpSystem/user/dateValidator/workerRouter] null
java.lang.NullPointerException
at org.filteredpush.kuration.services.InternalDateValidationService.isRange(InternalDateValidationService.java:778)
at org.filteredpush.kuration.services.InternalDateValidationService.validateDate(InternalDateValidationService.java:89)
at org.filteredpush.akka.actors.InternalDateValidator$InternalDateValidatorInvocation.onReceive(InternalDateValidator.java:225)
at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:159)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:425)
at akka.actor.ActorCell.invoke(ActorCell.scala:386)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:230)
at akka.dispatch.Mailbox.run(Mailbox.scala:212)
at akka.dispatch.ForkJoinExecutorConfigurator$MailboxExecutionTask.exec(AbstractDispatcher.scala:506)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:262)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:975)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1478)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)