activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Leung (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQCPP-556) Stop ActiveMQSessionKernel should also stop the ActiveMQConsumerKernel
Date Mon, 01 Dec 2014 06:19:13 GMT

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

Jeremy Leung updated AMQCPP-556:
--------------------------------
    Description: 
When we create a new *MessageConsumer* with a *MessageListener* from a session, the session
will be stopped before the updates of the message listener and restarted afterward if the
session already started.
However, if there have more than one consumers already started; calling *ActiveMQSessionKernel::stop()*
may goes into a deadlock if there have many messages coming in.

> Stop ActiveMQSessionKernel should also stop the ActiveMQConsumerKernel
> ----------------------------------------------------------------------
>
>                 Key: AMQCPP-556
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-556
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.8.3
>            Reporter: Jeremy Leung
>            Assignee: Timothy Bish
>         Attachments: AMQCPP-556.patch
>
>
> When we create a new *MessageConsumer* with a *MessageListener* from a session, the session
will be stopped before the updates of the message listener and restarted afterward if the
session already started.
> However, if there have more than one consumers already started; calling *ActiveMQSessionKernel::stop()*
may goes into a deadlock if there have many messages coming in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message