Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of teemu@torma.org designates
 213.41.244.89 as permitted sender)
From: Teemu Torma <teemu@torma.org>
To: dev@activemq.apache.org
Subject: Re: [jira] Resolved: (AMQCPP-271) Connection shutdown crashes if the
 server went down
Date: Sun, 6 Dec 2009 18:07:27 +0100
User-Agent: KMail/1.12.2 (Linux/2.6.31-15-generic; KDE/4.3.2; x86_64; ; )
References: <504712989.1260046495959.JavaMail.jira@brutus>
 <200912061603.19599.teemu@torma.org> <1260117535.2877.3.camel@localhost>
In-Reply-To: <1260117535.2877.3.camel@localhost>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <200912061807.27303.teemu@torma.org>

On Sunday 06 December 2009 17:38:54 Timothy Bish wrote:
> The method Thread::currentThread won't work after a call to the shutdown
> method for the library, which is why its important to clean up your
> ActiveMQ-CPP resources for calling it.

I meant that in multi-threading application where a thread that is not 
controlled my activemq-cpp tries to close a session, the Thread::currentThread 
throws because the thread never had a currentThread in the first place.

I tried just to remove the throw and return null pointer and everything 
appears to work fine.  Why not check the thread ids instead of thread 
structures in shutdown?  

Teemu