[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-815: ------------------------------------- This cannot be fixed until we implement duplicate message detection, which is scheduled for 1.2.1, therefore I am moving it to 1.2.1 -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-815: --------------------------------------------- org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest tests that are currently failing and commented out: 1. testFailureOnSendReceiveSynchronized() junit.framework.AssertionFailedError at org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest.testFailureOnSendReceiveSynchronized(MultiThreadFailoverTest.java:233) 2. testMultiThreadFailoverSeveralThreads() expected:<3647> but was:<3649> junit.framework.AssertionFailedError: expected:<3647> but was:<3649> at org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest.multiThreadFailover(MultiThreadFailoverTest.java:430) at org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest.testMultiThreadFailoverSeveralThreads(MultiThreadFailoverTest.java:267) 3. testMultiThreadFailoverSeveralThreadsTransacted() expected:<9398> but was:<10043> junit.framework.AssertionFailedError: expected:<9398> but was:<10043> at org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest.multiThreadFailover(MultiThreadFailoverTest.java:430) at org.jboss.test.messaging.jms.clustering.MultiThreadFailoverTest.testMultiThreadFailoverSeveralThreadsTransacted(MultiThreadFailoverTest.java:272) UNCOMMENT THESE TESTS UPON DUPLICATE MESSAGE DETECTION IMPLEMENTATION AND MAKE SURE THEY PASS! Do a search for "JBMESSAGING-815" to make sure you uncomment all related tests. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=comments#action_12... ] Clebert Suconic commented on JBMESSAGING-815: --------------------------------------------- I have commented an assertion on MultiThreadFailoverTest::multiThreadFailover and re-enabled testMultiThreadFailoverSeveralThreads... This test can run.. but we should ignore the assertion. I would prefer to keep the test as it would catch possible problems besides the counters. -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ] Tim Fox updated JBMESSAGING-815: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-815: ------------------------------------- To explain this issue in more detail: If message or ack is sent and hits the server and is processed correctly, then the server fails before the response is written back to the client, the client will get an exception and failover will start. When the client has failed over it will retry sending the message or ack. For the ack this is harmless since we can just ignore acks received if we can't find the message - the assumption here is it is already acked. For sends this is more serious. The message might have been previously sent and acked, so we might not find it in the queue. To solve this properly we need duplicate message detection on the server. Duplicate message detection is currently scheduled for 2.0 -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ] Tim Fox updated JBMESSAGING-815: -------------------------------- Priority: Major (was: Critical) -- 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

[ http://jira.jboss.com/jira/browse/JBMESSAGING-815?page=all ] Tim Fox reopened 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