Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 22 Oct 2012 13:24:12 +0000 (UTC)
From: "Pablo La Greca (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <275397688.9586.1350912252489.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <931206033.23261.1315363149939.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (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
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pablo La Greca updated AMQ-3485:
--------------------------------

    Comment: was deleted

(was: Dejan thanks!. Somebody with common sense finally.)
    
> 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
>            Assignee: Dejan Bosanac
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira