servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bartosz Kowalewski (JIRA)" <>
Subject [jira] Commented: (SM-1162) StatisticsService - NPE
Date Wed, 05 Dec 2007 08:44:27 GMT


Bartosz Kowalewski commented on SM-1162:

I've just attached a patch for this issue ( As Guillaume
said on the forum, it is a really simple task to add a check for a NPE. This patch only adds
an 'if' statement and the NPE dissapears. Unfortunately the problem should be investigated,
I'm not sure what causes SM to log monitoring data for an unregistered endpoint. It could
be a WSN2005 issue or even a general SM one. I'm not familiar with the source code. 

For now, the patch works okay, but I think that it's not enough to close this bug.

> StatisticsService - NPE
> -----------------------
>                 Key: SM-1162
>                 URL:
>             Project: ServiceMix
>          Issue Type: Bug
>            Reporter: Bartosz Kowalewski
>         Attachments:
> This issue is closely related to a forum thread, located at:
>   ----------------------------
> 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(
>         at org.apache.servicemix.jbi.monitoring.StatisticsService$3.exchangeAcce
> pted(
>         at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBoun
> d(
>         at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlo
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.j
> ava:167)
>         at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$
> a:134)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec
>         at java.util.concurrent.ThreadPoolExecutor$
> .java:675)
>         at
> 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.

View raw message