[jboss-remoting-issues] [JBoss JIRA] Commented: (JBREM-1283) CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Wed May 25 22:55:00 EDT 2011
[ https://issues.jboss.org/browse/JBREM-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604487#comment-12604487 ]
Ron Sigal commented on JBREM-1283:
----------------------------------
Hi Lami,
re: "Is this going to be included in EAP 5.1.1 ?"
Yes, it is fixed in Remoting release 2.5.4.SP2, which will ship with EAP 5.1.1. See JBPAPP-5985 "Upgrade to Remoting 2.5.4.SP2".
-Ron
> CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker
> --------------------------------------------------------------
>
> Key: JBREM-1283
> URL: https://issues.jboss.org/browse/JBREM-1283
> Project: JBoss Remoting
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 2.5.4.SP1
> Reporter: Justin Bertram
> Assignee: Ron Sigal
> Fix For: 2.5.4.SP2
>
>
> In Tomcat 5.5 org.apache.coyote.http11.Http11Protocol [1] inherited its getters and setters from org.apache.coyote.http11.Http11BaseProtocol [2] and one could set "minSpareThreads" and "maxSpareThreads" directly. However, in Tomcat 6.0 [3] there is a new setExecutor method which takes a java.util.concurrent.Executor (i.e. not a String or a primitive like the other setters). The org.jboss.remoting.transport.coyote.CoyoteInvoker.setProperty(..) method doesn't support this.
> [1] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyote/http11/Http11Protocol.html
> [2] http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/coyote/http11/Http11BaseProtocol.html
> [3] http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/coyote/http11/Http11Protocol.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-remoting-issues
mailing list