[esb-issues] [JBoss JIRA] Work started: (JBESB-1472) DataCollector does not check for NP during getClassPatterns

Mark Little (JIRA) jira-events at lists.jboss.org
Sun Jan 13 09:26:24 EST 2008


     [ http://jira.jboss.com/jira/browse/JBESB-1472?page=all ]

Work on JBESB-1472 started by Mark Little.

> DataCollector does not check for NP during getClassPatterns
> -----------------------------------------------------------
>
>                 Key: JBESB-1472
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1472
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Management
>    Affects Versions: 4.2.1
>            Reporter: Mark Little
>         Assigned To: Mark Little
>             Fix For: 4.2.1 CP1
>
>
> 09:52:08,935 WARN  [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <ws\
> a:Address jms://localhost/queue/DataCollectorQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:spec\
> ification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true\
> />, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-0 RelatesTo: jms:correlationID#3690b2f9-6fea-48f6-b987-e4aab46de89c ]
> java.lang.NullPointerException
>         at org.jboss.soa.esb.monitoring.client.DataCollector.getClassPatterns(DataCollector.java:89)
>         at org.jboss.soa.esb.monitoring.client.DataCollector.collectData(DataCollector.java:159)
>         at org.jboss.soa.esb.monitoring.client.DataCollectorAction.collectStatistics(DataCollectorAction.java:72)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
>         at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:347)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:613)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list