The interrupted exception is how it stops the thread internally.
See ReadTask.stop() or WriteTask.stop()
You should not leave it to the garbage collector, that is a guaranteed mechanism
to leave sockets open and run out of client sockets to bind to.
The gc is only guaranteed to run when you are running out of memory, not
running out sockets.
Besides, jbossmq's Connection implementation has no
finalize()
{
this.close();
}
it wouldn't work because the connection is hard referenced by the ping clock
daemon (it would never get called).
Regards,
Adrian
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831989#3831989
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831989
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
