[ https://issues.jboss.org/browse/JBREM-1281?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1281: ---------------------------------- org.jboss.remoting.transport.coyote.CoyoteInvoker has been updated to be compatible with jbossweb, which is based on tomcat 6. CoyoteInvoker.setup() will, as always, scan the configuration map and call CoyoteInvoker.setProperty() for each entry to set the appropriate property on the ProtocolHandler. However, when it encounters a property named "executor", it will parse the String value, expecting a String of the form "name1=value1, ..., nameN=valueN", to create a property map. It will create a org.apache.catalina.core.StandardThreadExecutor, apply the properties in the new property map to the StandardThreadExecutor, and call setExecutor() on the ProtocolHandler with the StandardThreadExecutor. If the value of "executor" is to be set in a *-service.xml file, it would look like <attribute name="Configuration"> <config> <invoker transport="http"> ... <attribute name="executor">minSpareThreads=20,maxThreads=100</attribute> ... </invoker> ... </config> </attribute> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBREM-1281?page=com.atlassian.jira.plugin... ] Ron Sigal commented on JBREM-1281: ---------------------------------- Unit test: org.jboss.test.remoting.transport.coyote.SetAttributeTestCase. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira