|
If you were logged in you would be able to see more operations.
|
|
|
| Labels: |
|
| User impact: |
High
|
| Effort points: |
1
|
| Log Output: |
[01-27 16:30:14] ERROR DefaultExceptionStrategy [jmsConnector1.dispatcher.1]: Caught exception in Exception Strategy: Don't understand null destinations
javax.jms.InvalidDestinationException: Don't understand null destinations
at org.apache.activemq.ActiveMQMessageConsumer.<init>(ActiveMQMessageConsumer.java:142)
at org.apache.activemq.ActiveMQQueueReceiver.<init>(ActiveMQQueueReceiver.java:73)
at org.apache.activemq.ActiveMQSession.createReceiver(ActiveMQSession.java:1194)
at org.apache.activemq.ActiveMQSession.createReceiver(ActiveMQSession.java:1168)
at org.apache.activemq.ActiveMQQueueSession.createReceiver(ActiveMQQueueSession.java:214)
at org.mule.transport.jms.Jms102bSupport.createConsumer(Jms102bSupport.java:139)
at org.mule.transport.jms.JmsMessageDispatcher.createReplyToConsumer(JmsMessageDispatcher.java:398)
at org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:218)
at org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:72)
at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:264)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)
[01-27 16:30:14] ERROR DefaultExceptionStrategy [jmsConnector1.dispatcher.1]: Caught exception in Exception Strategy: Don't understand null destinations
javax.jms.InvalidDestinationException: Don't understand null destinations
at org.apache.activemq.ActiveMQMessageConsumer.<init>(ActiveMQMessageConsumer.java:142)
at org.apache.activemq.ActiveMQQueueReceiver.<init>(ActiveMQQueueReceiver.java:73)
at org.apache.activemq.ActiveMQSession.createReceiver(ActiveMQSession.java:1194)
at org.apache.activemq.ActiveMQSession.createReceiver(ActiveMQSession.java:1168)
at org.apache.activemq.ActiveMQQueueSession.createReceiver(ActiveMQQueueSession.java:214)
at org.mule.transport.jms.Jms102bSupport.createConsumer(Jms102bSupport.java:139)
at org.mule.transport.jms.JmsMessageDispatcher.createReplyToConsumer(JmsMessageDispatcher.java:398)
at org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:218)
at org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:72)
at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:264)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)
|
| Similar Issues: |
|
Ross, your recent refactoring of replyTo handling in JmsMessageDispatcher introduced some regressions. Before it, the jms transport test in CE all ran without a single unexpected log warning or error. Many log errors now, though.
I've roughly pinpointed it to around r13803 in JmsMessageDispatcher. Once I rolled back to this revision, the errors in the log were gone. You can reproduce, e.g. by running the JmsSingleTransactionComponentTestCase. It looks as though the dispatcher tries to register a consumer for a temp destination, even when it's explicitly disabled with the attribute or not required for the flow.
|
|
Description
|
Ross, your recent refactoring of replyTo handling in JmsMessageDispatcher introduced some regressions. Before it, the jms transport test in CE all ran without a single unexpected log warning or error. Many log errors now, though.
I've roughly pinpointed it to around r13803 in JmsMessageDispatcher. Once I rolled back to this revision, the errors in the log were gone. You can reproduce, e.g. by running the JmsSingleTransactionComponentTestCase. It looks as though the dispatcher tries to register a consumer for a temp destination, even when it's explicitly disabled with the attribute or not required for the flow. |
Show » |
|
Bug
Closed
Blocker
JMS replyTo refactoring introduced regressions