[
https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098940#comment-13098940
]
Timothy Bish commented on AMQ-3485:
-----------------------------------
I'd recommend creating a JUnit test case that reproduces your issue and
attaching it here.
> 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
>
> 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
