[jboss-jira] [JBoss JIRA] (AS7-4372) EJB remoting server side doesn't honour the max outbound messages configured on a channel

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated AS7-4372:
----------------------------------

       Fix Version/s: 7.1.2.Final-redhat1
    Git Pull Request: https://github.com/jbossas/jboss-as/pull/1962  (was: https://github.com/jbossas/jboss-as/pull/1962)


Scheduling for 7.1.2 since this is a "Blocker". An AS7 project Blocker means a release or tag should not happen until the issue is fixed, so a Blocker must have a Fix Version assigned.
                
> EJB remoting server side doesn't honour the max outbound messages configured on a channel
> -----------------------------------------------------------------------------------------
>
>                 Key: AS7-4372
>                 URL: https://issues.jboss.org/browse/AS7-4372
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.1.Final
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>            Priority: Blocker
>             Fix For: 7.1.2.Final-redhat1
>
>
> While sending out messages/responses on the EJB remote channel, the server side doesn't take into account the configured max outbound messages on the channel. This can lead to the following exception on the server side:
> {code}
>  org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
>         at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA]
>         at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA]
>         at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.writeMethodInvocationResponse(MethodInvocationMessageHandler.java:330)
>         at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$500(MethodInvocationMessageHandler.java:64)
>         at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:226)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_b147-icedtea]
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_b147-icedtea]
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_b147-icedtea]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_b147-icedtea]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_b147-icedtea]
>         at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_b147-icedtea]
>         at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]
> {code}

--
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