yep, the exception is trapped. But an error handler would be called. You need to register an error handler with the container that will rethrow the runtime exception, I think then it will get back to amq.
On 5 May 2011 11:25, karen <jaskaran1...@gmail.com> wrote: > Hi Gary > > Thanks alot. I now understand that the spring framework is catching the > exception. > I used the SimpleMessageListenerContainer as you advised. > > But again did not get the DLQ exception string. I think the same thing is > happening in this container as well. > I have attached the activemq and wrapper log file for referance. > > Is there any work around! Can i use an exception listener to set a custom > property for the message myself. Please advise. > > http://activemq.2283324.n4.nabble.com/file/n3498021/ActiveMQLog.txt > ActiveMQLog.txt > http://activemq.2283324.n4.nabble.com/file/n3498021/wrapper.log wrapper.log > > Thanks > > Also for referance Below is the exception i see now in the eclipse console > for the SimpleMessageListenerContainer :- > 2011-05-05 15:42:54,359 WARN > [org.springframework.jms.listener.SimpleMessageListenerContainer] - > <Execution of JMS message listener failed, and no ErrorHandler has been > set.> > java.lang.RuntimeException: Pls work force a redelivery > at > com.pearson.rel.webapp.listener.jms.TestMessagesListener.onMessage(TestMessagesListener.java:11) > at > org.springframework.jms.listener.adapter.MessageListenerAdapter.onMessage(MessageListenerAdapter.java:339) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:535) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:495) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467) > at > org.springframework.jms.listener.AbstractMessageListenerContainer.executeListener(AbstractMessageListenerContainer.java:439) > at > org.springframework.jms.listener.SimpleMessageListenerContainer.processMessage(SimpleMessageListenerContainer.java:311) > at > org.springframework.jms.listener.SimpleMessageListenerContainer$2.onMessage(SimpleMessageListenerContainer.java:287) > at > org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1230) > at > org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:134) > at > org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:205) > at > org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:127) > at > org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-5-5-Not-able-to-get-the-DLQ-DELIVERY-FAILURE-CAUSE-PROPERTY-value-tp3492931p3498021.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
