You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2008/10/21 09:42:52 UTC

[jira] Updated: (SM-1456) Statistics Service throws NPE on startup.

     [ https://issues.apache.org/activemq/browse/SM-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Freeman Fang updated SM-1456:
-----------------------------

    Fix Version/s: 3.3.1
                   3.4
                       (was: 3.3)

> Statistics Service throws NPE on startup.
> -----------------------------------------
>
>                 Key: SM-1456
>                 URL: https://issues.apache.org/activemq/browse/SM-1456
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-components
>         Environment: Windows XP
>            Reporter: Ryan Moquin
>            Priority: Minor
>             Fix For: 3.3.1, 3.4
>
>
> I received this exception on startup, upon some discussion on the list, it appears that maybe a service sent a message to the Statistics Service before it was ready and generated an NPE.  Something should be done to prevent this from happening.
> 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)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.