[jboss-jira] [JBoss JIRA] Closed: (JBREM-667) Worker thread names are confusing
[ http://jira.jboss.com/jira/browse/JBREM-667?page=all ]
Ovidiu Feodorov closed JBREM-667.
---------------------------------
Resolution: Done
Assignee: Ovidiu Feodorov (was: Tom Elrod)
Renamed them AcceptorThread#<counter>-port and
WorkerThread#<counter>[current-socket-IP:current-socket-port]
Worker thread names are confusing
---------------------------------
Key: JBREM-667
URL: http://jira.jboss.com/jira/browse/JBREM-667
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Alpha3 (Bluto), 2.2.0.Alpha4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Minor
Fix For: 2.2.0.Alpha5
The worker thread names are confusing.
Example: "SocketServerInvokerThread-10.1.122.40-0",
"SocketServerInvokerThread-10.1.122.42-8"
They contain the IP address of the client that originally caused the worker thread to be
created, but then the worker threads are recycled via the thread pool, ending in handling
invocations from clients created from completely different IP addresses.
I propose calling them "RemotingWorkerThread-<counter>"
--
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