Ryan,
The StatisticsService will try do keep count of the amount of messages
processed by every component / endpoint. Looking at the code, this
exception could be raised during startup when a MessageExchange is being
sent to an endpoint before it has been registered in the ESB. I have
never seen this exception myself, but I do think the StatisticsService
should be able to handle this (by at least not throwing a
NullPointerException). Could you raise a JIRA issue for this?
Regards,
Gert
Ryan Moquin wrote:
I've been working on some new services which have been giving me some
trouble. One of the exceptions is a bit weird and doesn't seem to have any
indication where it came from or what it is. I also have also only seen it
once so far while testing things. Is this exception benign or does it mean
anything in particular that is important? Is is it just something that
could happen while servicemix is starting up?
WARN - DeliveryChannelImpl - Error calling listener: null
java.lang.NullPointerException
at
org.apache.servicemix.jbi.monitoring.StatisticsService.onExchangeAccepted(StatisticsService.java:307)
at
org.apache.servicemix.jbi.monitoring.StatisticsService$3.exchangeAccepted(StatisticsService.java:186)
at
org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:598)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:167)
at
org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
Thanks!
Ryan
