Topic-Messages not redelivered after rollback and reconnect.

[rosenfelder]

I'm using apache-activemq-5.4.2-fuse-01-00

There is a durable subscription on a topic with some messages waiting to be consumed.

The following steps reproduce my problem:

1. Open a transacted, durable subscriber

2. consume messages

3. rollback

4. closse the session

5. reconnect

6. consume messages

I expect to receive the same messages in step 2 and 6, but I never get any message a soon as I close the session (i.e. in step 6).

Is this the supposed behaviour of a JMS Provider to implicitly acknowledge all messages when a session is closed, even if I call rollback?

Following the relevant code-snippet, where in the second receive, I don't receive the rolled-back messages:

            TopicConnection conn = factory.createTopicConnection();

            conn.setClientID(clientId);

            TopicSession session = conn.createTopicSession(true, Session.SESSION_TRANSACTED);

            TopicSubscriber subscriber = session.createDurableSubscriber(myTestTopic, subscriptionName);

            conn.start();

            Message message = subscriber.receive();

            while (null != message) {

                System.out.println("Message received: " + ((TextMessage)message).getText());

                message = subscriber.receive();

            }

            session.rollback();

            subscriber.close();

            session.close();

            conn.close();

            conn = factory.createTopicConnection();

            conn.setClientID(clientId);

            session = conn.createTopicSession(true, Session.SESSION_TRANSACTED);

            subscriber = session.createDurableSubscriber(myTestTopic, subscriptionName);

            conn.start();

            message = subscriber.receive();

            while (null != message) {

                System.out.println("Message received: " + ((TextMessage)message).getText());

                message = subscriber.receive();

            }

[garytully]

add a timeout to the call to receive.

message = subscriber.receive(4000);

There is a race between a consumer checking for a message and the broker doing a first async dispatch, often the client wins and does not find a message if there is no wait timeout specified.

[rosenfelder]

The example is simplified for readability. I actually did use some timeout, I even tried with message consumers. There is also no redelivery delay nor exponential backup configured.

When I change the persistence adapter to JDBC, I see the message in the database after sending, but as soon as the persistent subscriber receives the message (in a not-yet commited transaction), it gets removed from the database. So even if I call rollback() afterwards, the message cannot be redelivered again, as it doesn't seem to exist in the message store anymore.

When I switch to message queues, the messages get redelivered, which lets me think that this is a bug in the implementation of topics.

[garytully]

This is a bug. I have raised and resolved AMQ-3238 such that this will be fixed in the ActiveMQ 5.5.

Thanks for the simple test code that demonstrated the problem.

Edited by: gtully on Mar 23, 2011 11:32 AM

Edited by: gtully on Mar 23, 2011 11:35 AM

[rosenfelder]

I was just about to raise a bug in JIRA and now have seen that you already fixed this issue. Thanks a lot for the quick reaction!