Hi Adrian,
Thanks for the explanation on the problem. I will give it a try for that patch.
Could I know where should I get it?
Will the solution you suggested (update the redelivery status prior the msg
delivery to the client) be applied to the latest Jboss AS also? or it is a
temporary
Ok, I think I understand what the problem is.
The issue is that the failover node doesn't know that the message was already
delivered. The node (the original node) that did know has crashed.
The problem comes because the failover node uses the transaction log
to recover the state to the last
Bug report:
http://jira.jboss.com/jira/browse/JBAS-4870
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4096083#4096083
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4096083
___
Hi Adrian, thanks for your reply.
Below is the sysout of the jms message.
1st received msg
| [13:10:07-16:16:22,461][JMS SessionPool Worker-19][
INFO][GN.APP.WORKFLOW][]Msg received: org.jboss.mq.SpyObjectMessage {
| Header {
|jmsDestination : QUEUE.sendSignalQueue
|
Show System.out.println(message) for both deliveries of the message.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094563#4094563
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094563
Hi all,
Did I omit something in my description or the information I provided is not
sufficient for the case?
Thanks for your help.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4093945#4093945
Reply to the post :
