Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <11284483.post@talk.nabble.com>
Date: Mon, 25 Jun 2007 03:57:46 -0700 (PDT)
From: Jim_Cross <jimcross1981@googlemail.com>
To: users@activemq.apache.org
Subject: Re: Orphan connections from .NET clients
In-Reply-To: <11269315.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <4666F712.6000201@blackspark.com> <11269315.post@talk.nabble.com>


Hi Chris,

My shutdown code looks like this, but I still get the problem:

                if (consumer != null)
                {
                    consumer.Close();
                    consumer.Dispose();
                }
                
                if (session != null)
                {
                    session.Close();
                    session.Dispose();
                }
                
                if(connection != null)
                {
                    connection.Stop();
                    connection.Close();
                    connection.Dispose();
                }


Are you doing anything different to that?


Dris wrote:
> 
> Have you tried explicitly calling connection.Dispose() before exiting your
> program? To get round this problem I just called Close() and Dispose() on
> every NMS object that exposed either or both those methods and it seemed
> to work for me. I suspect that just disposing of the connection may be
> enough to do the job though. I would be interested to know what happens
> for you. 
> 
> Chris
> 
> 

-- 
View this message in context: http://www.nabble.com/Orphan-connections-from-.NET-clients-tf3879502s2354.html#a11284483
Sent from the ActiveMQ - User mailing list archive at Nabble.com.