[
https://issues.apache.org/activemq/browse/SM-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bartosz Kowalewski updated SM-1162:
-----------------------------------
Attachment: SM-1162-StatisticsService.java.patch
> StatisticsService - NPE
> -----------------------
>
> Key: SM-1162
> URL: https://issues.apache.org/activemq/browse/SM-1162
> Project: ServiceMix
> Issue Type: Bug
> Reporter: Bartosz Kowalewski
> Attachments: SM-1162-StatisticsService.java.patch
>
>
> This issue is closely related to a forum thread, located at:
> http://www.nabble.com/StatisticsService---NPE-tf4887610s12049.html#a13989623 .
> ----------------------------
> We're using WSN2005 API from the inside of a SU (bean:endpoint). An external
> Java client is used to subscribe to WSN2005 component through http-binding
> and to receive future notifications. After a notification is delivered to the
> subscriber, the exeption provided below is printed on the ServiceMix side.
> WARN - DeliveryChannelImpl - Error calling listener: null
> java.lang.NullPointerException
> at
> org.apache.servicemix.jbi.monitoring.StatisticsService.onExchangeAcce
> pted(StatisticsService.java:307)
> at
> org.apache.servicemix.jbi.monitoring.StatisticsService$3.exchangeAcce
> pted(StatisticsService.java:186)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
> d(DeliveryChannelImpl.java:598)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
> w.java:170)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
> ava:167)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.jav
> a:134)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
> utor.java:650)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
> .java:675)
> at java.lang.Thread.run(Thread.java:595)
> It does not disturb the delivery but it is always printed. It just looks as
> if SM is trying to log something for an endpoint that isn't registered in the
> monitoring service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
