In addition, is it sufficient to simply close the connection, or should we
be closing each Consumer, then each Session, then each connection?  In other
words, do calls to Conection.close() automatically call Session.close()
which then call Producer/Consumer.close()?

Thanks,

Nathan

-----Original Message-----
From: Abe Mirrashidi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 12:33 PM
To: [EMAIL PROTECTED]
Subject: [developers] Leaking sessions.


> >I have a single TopicConnection which creates TopicSessions and then
> >closes them when they are no longer needed.

> First you should try this with SwiftMQ 2.1.0 version. If the problem
> resides you can fill a bug report at [EMAIL PROTECTED] .

The problem still occurs with 2.1.0.

Besides close(), is there anything else that needs to be done for a
session to be GC'd?

Cheers,
Abe



------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to 
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/


------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to 
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/




Reply via email to