On Fri, 2011-09-09 at 12:44 -0700, Shine wrote:
> hi,
>
> if you connect to the message broker and close/dispose everything, few
> handles still alive.
>
> expample:
>
> Apache.NMS.IConnectionFactory factory = new
> Apache.NMS.NMSConnectionFactory(@"tcp://messagebroker.xabcd.org:61616?wireFormat.maxInactivityDuration=0");
>
> using (Apache.NMS.IConnection connection =
> factory.CreateConnection("NotForYourEyes", "NotForYourEyes"))
> {
> using (Apache.NMS.ISession session = connection.CreateSession())
> {
>
> Apache.NMS.IDestination destination = new
> Apache.NMS.ActiveMQ.Commands.ActiveMQTopic("{12345678-288C-4787-A9C9-123456789012}/11023");
> using (Apache.NMS.IMessageConsumer consumer =
> session.CreateConsumer(destination))
> {
> connection.Start();
> }
> }
> }
>
> About 35 handles will not be cleaned up. If you do some reconnects you get
> an "OutOfMemory" Exception after a while.
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/C-NMS-After-close-a-connection-a-couple-of-handles-will-not-be-cleaned-up-tp3802609p3802609.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Usually helpful to let us know what version you are using, there were
some things like this fixed in past releases, if not on v1.5.1 then I'd
suggest giving that a try.
Regards
--
Tim Bish
------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/
