[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-899) QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-899:
---------------------------------------------
The point of adding this test was an investigation of MergeQueue::testMergeQueue2...
At the end the problem wasn't the queue itself, but this anti pattern was being used
by "accident", as the failover was starting the connection, and right after
failover and closing it immediatly.
On the failover side, maybe we should just not resume invocations on close?
QueueTest::testClosedConsumerAfterStart fails because a possible
anti-pattern
-----------------------------------------------------------------------------
Key: JBMESSAGING-899
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-899
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.2.0.GA
If this anti-pattern is being used:
MessageConsumer c2 = s2.createConsumer(queue);
conn2.start();
c2.close();
c2 = s2.createConsumer(queue);
We might loose messages until we restart the server.
--
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