[
http://jira.jboss.com/jira/browse/JBMESSAGING-809?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-809:
---------------------------------------------
This task was about fixing FailoverTest::testFailureRightAfterSend
As a fix, we are double checking if ACKs were previously ACKed (not throwing exceptions if
they were already ACKed)
or verifying if the message was already included, by checking if the message was already
included, with an extra select during failover.
However, a complete fix for this would be JBMESSAGING-815 and JBMESSAGING-604
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 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.
--
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