activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pablo La Greca (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3485) Transacted Session returns invalid MessageConsumer after the first MessageConsumer for the same destiantion. Bug introduced in 5.5.0 - working ok in 4.1.2
Date Tue, 20 Sep 2011 16:30:08 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108811#comment-13108811
] 

Pablo La Greca commented on AMQ-3485:
-------------------------------------

I'm don't want that. What I want is that if I have a queue QUEUEA with 2 messages, and I have
a session SESSIONA, I should be able to create one consumer with SESSIONA and consume the
first message, close that consumer, and then create another consumer with SESSIONA and consume
the second message. Once more, as I was able to do in previous versions of ActiveMQ.

If after that I commit SESSIONA both message will be removed.

> Transacted Session returns invalid MessageConsumer after the first MessageConsumer for
the same destiantion. Bug introduced in 5.5.0 - working ok in 4.1.2
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3485
>                 URL: https://issues.apache.org/jira/browse/AMQ-3485
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.5.0
>            Reporter: Pablo La Greca
>         Attachments: activemq-issue-test-case.zip
>
>
> When I have a transacted Session, as it is single threaded I can't create two MessageConsumer
to the same Destination. But if I create a MessageConsumer to a Destination and then I close
it, then I should be able to create a new MessageConsumer to the same Destination. This is
working fine in active mq 4.1.2 but it doesn't work in 5.5.0. It allows to create a second
MessageConsumer but that seconde MessageConsumer always returns null when the queue has messages.
> i.e:
> Session session = .... //transacted session
> Destination dest = .... 
> MessageConsumer mc = session.createMessageConsumer(dest);
> Message message = mc.receive(); // message received ok
> mc.close();
> mc = session.createMessageConsumer(dest);
> Message message = mc.receive(); // message is null
> Thanks, Pablo.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message