activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <>
Subject [jira] [Commented] (AMQ-5966) ActiveMQ client hangs after rollback of a transacted JMS session
Date Tue, 22 Sep 2015 16:17:04 GMT


Christopher L. Shannon commented on AMQ-5966:

I think the test case code throws that exception just to demonstrate that the same listener
was called twice.  I was able to show the RuntimeException when running the code which is
how I found the commit where the behavior changed.  That being said, I haven't looked into
it enough yet to figure out if there is an actual issue with the same listener being called
again or if a new one is necessary.

> ActiveMQ client hangs after rollback of a transacted JMS session
> ----------------------------------------------------------------
>                 Key: AMQ-5966
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.12.0
>         Environment: Reproduced standalone under Linux, but any environment should be
>            Reporter: Andreas Mattes
>         Attachments:
> The ActiveMQ JMS client is accessed through the ConnectionConsumer protocol. A ServerSessionPool
is provided which creates ServerSessions with transacted JMS sessions. Up to ActiveMQ 5.11.2,
everything has worked fine, but with ActiveMQ 5.12.0, after rollback of a sesseion, the application
hangs until JMS re-connect happens. Further investigation reveals that with ActiveMQ 5.11.2
and earlier, after rollback a new ServerSession is taken from the pool and loaded with the
message of the rolled back session. With ActiveMQ 5.12.0, however, the MessageListener of
the same session is called again. This is a problem with the ConnectionConsumer protocol,
because the may have claimed the session for recycling.
> The attached piece of test code ( demonstrates the issue. It runs
fine with ActiveMQ 5.11.2 and hangs with ActiveMQ 5.12.0. It demonstrates the issue for QueueSessions,
but TopicSessions are affected equally.

This message was sent by Atlassian JIRA

View raw message