[ http://jira.jboss.com/jira/browse/JGRP-49?page=history ] Bela Ban resolved JGRP-49: --------------------------
Resolution: Done Fixed. Although this didn't cause multiple outgoing packet threads to be created b/c OutgoingPacketHandler.start() would not start a new thread if the old thread was still running. However, the current solution is cleaner. Thanks for detecting this ! > org.jgroups.protocols.UDP.stopThreads() doesn't stop outgoing_packet_handler > ---------------------------------------------------------------------------- > > Key: JGRP-49 > URL: http://jira.jboss.com/jira/browse/JGRP-49 > Project: JGroups > Type: Bug > Environment: version 2.2.7 all platforms > Reporter: Steve Nicolai > Assignee: Bela Ban > Fix For: 2.2.8 > > > When a channel is disconnected, stop() is called for all items in the > protocol stack. UDP.stop() calls stopThreads() which does not stop the > outgoing_packet_handler. > This causes multiple of these threads to be created if a channel is started > and stopped in an application. > Proposed fix, at the bottom of org.jgroups.protocols.UDP.stopThreads() add > the following: > // 4. if (outgoing_packet_handler != null) > outgoing_packet_handler.stop(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development