Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 14 Apr 2011 11:33:05 +0000 (UTC)
From: "Teemu Torma (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1168691706.57453.1302780785686.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (AMQCPP-361) Destroying a consumer may cause a
 crash
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Destroying a consumer may cause a crash
---------------------------------------

                 Key: AMQCPP-361
                 URL: https://issues.apache.org/jira/browse/AMQCPP-361
             Project: ActiveMQ C++ Client
          Issue Type: Bug
          Components: CMS Impl
    Affects Versions: 3.2.5
         Environment: all
            Reporter: Teemu Torma
            Assignee: Timothy Bish


ActiveMQSessionExecutor::dispatch gets a consumer and calls consumer's dispatch method without holding any locks in between.  This leaves a window when a consumer can be no longer valid on a dispatch call causing a crash.

Since this is a timing issue it is hard to demonstrate as such.  If one adds let's say one second sleep in ActiveMQSessionExecutor::dispatch before the call to the consumer->dispatch, and destroys a consumer on a destination which has messages incoming will likely crash the application.

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