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: <11228145.post@talk.nabble.com>
Date: Thu, 21 Jun 2007 00:36:21 -0700 (PDT)
From: Jim_Cross <jimcross1981@googlemail.com>
To: users@activemq.apache.org
Subject: Re: Orphan connections from .NET clients
In-Reply-To: <46681E6D.1050405@blackspark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <4666F712.6000201@blackspark.com>
 <af2843cd0706062128s5e6db8d3s253c6b75b5f4d4f6@mail.gmail.com>
 <46681E6D.1050405@blackspark.com>


Gaurav,

Did you ever find a workaround for this? I've hit the same problem with NMS
and ActiveMQ 4.1.1 (also seems to affect 4.1.0 but not 4.0.2), and it looks
like it could be a show stopper for us.

Cheers,

Jim


Gaurav Hariani-2 wrote:
> 
> yes
> 
> Hiram Chirino wrote:
>> Odd. look like a bug.  You using 4.1.1?
>>
>>
>> On 6/6/07, Gaurav Hariani <gaurav@blackspark.com> wrote:
>>> Since James and Hiram are back on the list ... I thought I'd repost 
>>> this-
>>>
>>> We are facing a problem of orphan connections to ActiveMQ. A simple .NET
>>> client that only creates a connection/session and then closes and exits,
>>> still shows up in jconsole.
>>> It is possible to stop it manually in jconsole.
>>>
>>> Below is an example to reproduce the problem:
>>>
>>>
>>> The following code creates a connection to an OpenWire transport
>>> connector, waits for 1 second and then closes the session/connection.
>>> Looking at JConsole ... ActiveMQ reports the connection as open. Too
>>> many open connections and ActiveMQ stops processing messages.
>>>
>>> However if the connection is not closed by the application and the
>>> application is killed using Ctrl-C ... then ActiveMQ closes the
>>> connections.
>>>
>>> Is there something obvious that I'm doing wrong or is this a bug in the
>>> TcpTransport code?
>>>
>>>
>>>
>>> using System;
>>> using System.Threading;
>>> using NMS;
>>>
>>> namespace ActiveMQ {
>>>    class TestMain {
>>>
>>>        static void Main(string[] args) {
>>>
>>>            Uri uri = new Uri("tcp://activemqserver:61616");
>>>
>>>            ConnectionFactory factory = new ConnectionFactory(uri);
>>>            IConnection connection = null;
>>>            ISession session = null;
>>>
>>>            try {
>>>                connection = factory.CreateConnection();
>>>                Console.WriteLine("Connection Created");
>>>
>>>                connection.ClientId = "[test1] " + connection.ClientId;
>>>
>>>                session = connection.CreateSession();
>>>                Console.WriteLine("Session Created");
>>>
>>>                Thread.Sleep(1000);
>>>
>>>            } finally {
>>>                session.Close();
>>>                connection.Close();
>>>                Console.WriteLine("Connection Closed");
>>>            }
>>>        }
>>>    }
>>> }
>>>
>>
>>
> 
> 

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