[ http://jira.jboss.com/jira/browse
/JBMESSAGING-904?page=comments#action_12354575 ]
Tim Fox commented on JBMESSAGING-904:
-------------------------------------
This is failing because on failover of a session we
shutdownAfterProcessingCurrentTasks on the session's
executor, then replace the executor.
This means if an ack is retried after being put on hold
after failover and ackmode is auto ack then the ack can be
resumed, but before it completes and nulls the auto_ack info
in the session state another delivery can be excuted - but
on a different thread since we replaced the executor so it
smacks into the back of the first one throws an exception
and the message doesn't get delivered. The next message that
actually gets delivered is then the next one and the
assertion is thrown.
Solution is to subclass QueuedExecutor with a new class that
allows all excet currently executing task to be cleared
without shutting down the QueuedExecutor.
>
org.jboss.test.messaging.jms.clustering.MultipleFailoverTest
.testFailoverFloodTwoServers() fails on Linux
>
------------------------------------------------------------
---------------------------------------------
>
> Key: JBMESSAGING-904
> URL: htt
p://jira.jboss.com/jira/browse/JBMESSAGING-904
> Project: JBoss Messaging
> Issue Type: Bug
> Reporter: Ovidiu Feodorov
> Assigned To: Ovidiu Feodorov
> Priority: Blocker
> Fix For: 1.2.0.GA
>
>
> junit.framework.AssertionFailedError
> at
org.jboss.test.messaging.jms.clustering.MultipleFailoverTest
.testFailoverFloodTwoServers(MultipleFailoverTest.java:252)
--
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.atl
assian.com/software/jira
_______________________________________________
jboss-jira mailing list
jboss-jira lists.jboss.org
h
ttps://lists.jboss.org/mailman/listinfo/jboss-jira
|
