[
http://jira.jboss.com/jira/browse/JGRP-737?page=all ]
Bela Ban resolved JGRP-737.
---------------------------
Resolution: Done
- Moved the timer from ProtocolStack to TP
- Moved all thread factories to TP as well
- Added ability for each protocol to have its own thread factory, overriding the one in
TP
Fixed in 2.6 (2.6.3) and 2.7 (CVS head)
Shared transport protocols use stack field from first channel
created
---------------------------------------------------------------------
Key: JGRP-737
URL:
http://jira.jboss.com/jira/browse/JGRP-737
Project: JGroups
Issue Type: Bug
Affects Versions: 2.6.2
Reporter: Brian Stansberry
Assigned To: Bela Ban
Priority: Critical
Fix For: 2.6.3, 2.7
For example, TP.timer is set to TP.stack.timer. TP.stack belongs to an individual
channel, not to the set of channels associated with a shared transport.
Disconnect the first channel and the others go boom.
Did a quick scan of usage of the 'stack' field or the
'getProtocolStack()' method in TP and its subclasses. This usage for the timer is
one. Others are:
1) TCP.getConnectionTable calls
cTable.setThreadFactory(getProtocolStack().getThreadFactory());
2) handleDiagnosticProbe uses stack.getChannel()
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira