activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim_Cross <jimcross1...@googlemail.com>
Subject Re: Orphan connections from .NET clients
Date Mon, 25 Jun 2007 12:01:05 GMT

Hmm, very odd - taking out connection.Stop() and connection.Close() still
doesn't fix it for me.
Also connection.Dispose() just calls Close() anyway, so I'm not sure why
that fixed it for you either...


Dris wrote:
> 
> Not really. Actually on looking at it I am closing and disposing of
> sessions and consumers, and just disposing of producers and connections so
> I don't have your connection.Stop and connection.Close in mine. I would be
> surprised if that made a diff though. I had the issue until I added the
> connection.Dispose() and then it went away. I think I assumed that
> disposing of the session would stop and close it, though I have never
> checked the source for this. I was just being lazy.
> 

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


Mime
View raw message