[JBoss JIRA] Created: (JBMESSAGING-899) QueueTest::testClosedConsumerBeforeStart fails because a possible anti-pattern
2:58 a.m.
QueueTest::testClosedConsumerBeforeStart 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
7:04 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-899) QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Clebert Suconic updated JBMESSAGING-899:
----------------------------------------
Summary: QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
(was: QueueTest::testClosedConsumerBeforeStart fails because a possible anti-pattern)
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
7:06 a.m.
New subject: [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
10:58 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-899) QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Ovidiu Feodorov closed JBMESSAGING-899.
---------------------------------------
Resolution: Rejected
Invalid test.
You created a transacted session s2, but did not commit any transaction to acknowledge
deliveries.
In order to have the test passing, you need to either use a non-transacted session with
AUTO_ACKNOWLEDGE, or commit the transaction after receiving batches of 20 messages.
In both cases, I've checked and the test passes indeed.
// JMS 1.1 Specifications, Section 4.3.5:
// "Closing a connection must roll back the transactions in progress on
its
// transacted sessions*.
// *) The term 'transacted session' refers to the case where a
session's commit and
// rollback methods are used to demarcate a transaction local to the session.
In the
// case where a session's work is coordinated by an external transaction
manager, a
// session's commit and rollback methods are not used and the result of a
closed
// session's work is determined later by the transaction manager.
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
5:42 p.m.
New subject: [JBoss JIRA] Reopened: (JBMESSAGING-899) QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Clebert Suconic reopened JBMESSAGING-899:
-----------------------------------------
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
5:42 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-899) QueueTest::testClosedConsumerAfterStart fails because a possible anti-pattern
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Clebert Suconic updated JBMESSAGING-899:
----------------------------------------
Assignee: Tim Fox (was: Clebert Suconic)
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: Tim Fox
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
5:44 p.m.
New subject: [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 session.commit was an accident, but the test still fail time to time.. when a message
is delivered to a closed MessageCallbackHandler..And it was failing with this condition
when I committed before.
i.e, this test will fail when these messages are happening.
10:35:09,845 DEBUG @WorkerThread#0[127.0.0.1:2793] [ServerInvoker] Thread pool class
supplied is not an object name.
10:35:09,848 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,848 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,848 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,848 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,849 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,849 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,849 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,849 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,849 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,850 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,850 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,851 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
10:35:09,852 TRACE @WorkerThread#0[127.0.0.1:2793] [CallbackManager]
CallbackManager[257f1b] callback handler not found, message arrived after consumer is
closed
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: Tim Fox
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
5:46 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-899) Messages are temporarily lost if message arrives on a closed MessageCallbackHandler
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Clebert Suconic updated JBMESSAGING-899:
----------------------------------------
Summary: Messages are temporarily lost if message arrives on a closed
MessageCallbackHandler (was: QueueTest::testClosedConsumerAfterStart fails because a
possible anti-pattern)
Description:
If this pattern is being used:
MessageConsumer c2 = s2.createConsumer(queue);
conn2.start();
c2.close();
c2 = s2.createConsumer(queue);
We might loose messages until we close the session
QueueTest::testClosedConsumerAfterStart validate this bug. It fails occasionally
(on my computer in happened 1 in 6)
was:
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.
Messages are temporarily lost if message arrives on a closed
MessageCallbackHandler
-----------------------------------------------------------------------------------
Key: JBMESSAGING-899
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-899
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assigned To: Tim Fox
Priority: Blocker
Fix For: 1.2.0.GA
If this pattern is being used:
MessageConsumer c2 = s2.createConsumer(queue);
conn2.start();
c2.close();
c2 = s2.createConsumer(queue);
We might loose messages until we close the session
QueueTest::testClosedConsumerAfterStart validate this bug. It fails occasionally
(on my computer in happened 1 in 6)
--
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
1:41 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-899) Messages are temporarily lost if message arrives on a closed MessageCallbackHandler
[ http://jira.jboss.com/jira/browse/JBMESSAGING-899?page=all ]
Ovidiu Feodorov closed JBMESSAGING-899.
---------------------------------------
Resolution: Done
Messages are temporarily lost if message arrives on a closed
MessageCallbackHandler
-----------------------------------------------------------------------------------
Key: JBMESSAGING-899
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-899
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assigned To: Tim Fox
Priority: Blocker
Fix For: 1.2.0.GA
If this pattern is being used:
MessageConsumer c2 = s2.createConsumer(queue);
conn2.start();
c2.close();
c2 = s2.createConsumer(queue);
We might loose messages until we close the session
QueueTest::testClosedConsumerAfterStart validate this bug. It fails occasionally
(on my computer in happened 1 in 6)
--
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
6266
days inactive
6267
days old
8 comments
2 participants
participants (2)
-
Clebert Suconic (JIRA) -
Ovidiu Feodorov (JIRA)