[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1277) Allow configuration of socket and bisocket accept thread priority
[
https://issues.jboss.org/browse/JBREM-1277?page=com.atlassian.jira.plugin...
]
Ron Sigal commented on JBREM-1277:
----------------------------------
As Doug pointed out, the worker threads are created by the accept threads and inherit the
priority thread, so the worker thread priority should be set to Thread.NORM_PRIORITY.
Fixed on both branches, and unit tests updated to test for worker thread priority.
Waiting for results in hudson.
Allow configuration of socket and bisocket accept thread priority
-----------------------------------------------------------------
Key: JBREM-1277
URL: https://issues.jboss.org/browse/JBREM-1277
Project: JBoss Remoting
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Affects Versions: 2.2.3.SP3, 2.5.4.SP1
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.3.SP4, 2.5.4.SP2
It is possible that under heavy load, the
org.jboss.remoting.transport.socket.SocketServerInvoker accept thread and the
org.jboss.remoting.transport.bisocket.BisocketServerInvoker secondary accept threads,
which manage ServerSockets, can get starved by the worker threads. It would be useful to
be able increase the priority of these threads.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira