[
http://jira.jboss.com/jira/browse/JBMESSAGING-809?page=all ]
Clebert Suconic updated JBMESSAGING-809:
----------------------------------------
Description:
Imagine two threads... producer/consumer...
If the server crashed after the message was sent, when the client fails over to a new
server it will try to send or ack the message again, even if it was ACKED before.
There is also a possibility of the consumer ACK synchronized.. For this case you have the
related issue JBMESSAGING-815
was:
Imagine two threads... producer/consumer...
If the server crashes when both ACK and send are still coming back from the execution (at
the same time)... there is a chance of creating a message.
I have created MultiThreadFailoverTest::testFailureOnSendReceiveSynchronized for this...
But I have seen testMultiThreadFailover failing ocasionally.
testFailureOnSendReceiveSynchronized poisons the server is a special way to cause the
synchronization issue in a predictable way.
Extra message created if server fails right after send is completed
-------------------------------------------------------------------
Key: JBMESSAGING-809
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-809
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta2
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Critical
Fix For: 1.2.0.CR1
Imagine two threads... producer/consumer...
If the server crashed after the message was sent, when the client fails over to a new
server it will try to send or ack the message again, even if it was ACKED before.
There is also a possibility of the consumer ACK synchronized.. For this case you have the
related issue JBMESSAGING-815
--
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