[jboss-jira] [JBoss JIRA] (AS7-2100) Add missing attribute to the JBoss Remoting XML Schema
[
https://issues.jboss.org/browse/AS7-2100?page=com.atlassian.jira.plugin.s...
]
David Lloyd reassigned AS7-2100:
--------------------------------
Assignee: Kabir Khan (was: David Lloyd)
Remoting now uses the standard XNIO worker configuration parameters, and thus it's all
done via OptionMap. Here are the thread-related tunables for Remoting:
org.xnio.Options#WORKER_READ_THREADS (normally 1 or maybe 2-3 for an exceptionally busy
server)
org.xnio.Options#WORKER_WRITE_THREADS (same)
org.xnio.Options#WORKER_ACCEPT_THREADS (we can just leave this at 1, it doesn't have
to be tunable for Remoting)
org.xnio.Options#WORKER_TASK_CORE_THREADS (core pool size)
org.xnio.Options#WORKER_TASK_MAX_THREADS (max pool size)
org.xnio.Options#WORKER_TASK_KEEPALIVE (keepalive time in milliseconds)
org.xnio.Options#WORKER_TASK_LIMIT (worker queue length)
Add missing attribute to the JBoss Remoting XML Schema
------------------------------------------------------
Key: AS7-2100
URL: https://issues.jboss.org/browse/AS7-2100
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Remoting
Reporter: Andrig Miller
Assignee: Kabir Khan
Fix For: 7.1.0.CR1
I have been reviewing all the XML schemas as part of my performance tuning work. In
looking at the Remoting schema, there doesn't appear to be any thread pool settings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira