[
https://issues.jboss.org/browse/JBREM-1277?page=com.atlassian.jira.plugin...
]
Ron Sigal commented on JBREM-1277:
----------------------------------
SocketServerInvoker (and therefore SSLSocketServerInvoker, BisocketServerInvoker, and
SSLBisocketServerInvoker) can now be configured with the
"acceptThreadPriorityIncrement" parameter, by which the priority of the accept
thread(s) is increased. If the resulting priority is out of the acceptible range
(java.lang.Thread.MIN_PRIORITY to java.lang.thread.MAX_PRIORITY), a warning is issued and
the priority is not changed.
In the bisocket transport, the value of "acceptThreadPriorityIncrement" is used
to increase the priority of the SecondaryServerSocketThread, which manages the secondary
ServerSocket.
These changes have been applied to branches 2.2 and 2.x
Testing:
*
org.jboss.test.remoting.transport.bisocket.accept.SecondaryAcceptThreadPriorityTestCase
* org.jboss.test.remoting.transport.socket.accept.AcceptThreadPriorityTestCase
Waiting for results in hudson.
Need to update Remoting Guide and Users Guide.
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