[esb-issues] [JBoss JIRA] Updated: (JBESB-1216) dynamic_router quickstart exceptions
Mark Little (JIRA)
jira-events at lists.jboss.org
Wed Oct 24 08:31:02 EDT 2007
[ http://jira.jboss.com/jira/browse/JBESB-1216?page=all ]
Mark Little updated JBESB-1216:
-------------------------------
Component/s: Examples
> dynamic_router quickstart exceptions
> ------------------------------------
>
> Key: JBESB-1216
> URL: http://jira.jboss.com/jira/browse/JBESB-1216
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Examples
> Affects Versions: 4.2.1 IR2
> Reporter: Tom Cunningham
> Assigned To: Mark Little
> Fix For: 4.2.1 triage
>
>
> After deploying the dynamic_router quickstart to a completely fresh ESB server, I followed the next step in the instructions and got this exception:
> % ant receive-destination1
> Server shows :
> 15:47:56,596 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> 15:48:07,943 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/C/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-4 RelatesTo: jms:correlationID#ID:JBM-512 ]
> org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor
> at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127)
> at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
> at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:273)
> at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
> 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)
> Caused by: java.lang.NullPointerException
> at java.lang.String.<init>(String.java:479)
> at org.jboss.soa.esb.samples.quickstart.dynamicRouter.MyControlAction.processControlMessage(MyControlAction.java:61)
> 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)
> ... 6 more
> 15:48:07,948 WARN [ActionProcessingPipeline] No fault address defined for fault message! header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/C/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-4 RelatesTo: jms:correlationID#ID:JBM-512 ]
--
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