[jboss-jira] [JBoss JIRA] (AS7-3796) Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)

jaikiran pai (JIRA) jira-events at lists.jboss.org
Thu Feb 16 10:12:36 EST 2012


    [ https://issues.jboss.org/browse/AS7-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667120#comment-12667120 ] 

jaikiran pai commented on AS7-3796:
-----------------------------------

I have a test which tries to do something similar in AS7. I had run that while implementing this solution. I'll rerun it again and send a pull request for upstream so that we have this thoroughly tested. In the meantime, I'll see if we are missing some path which might not be using the semaphore before writing out to the channel(I don't think we have missed any, but will check again).

                
> Remote EJB client seems to be leaking messages MAX_OUTBOUND_MESSAGES (ChannelBusyException: Too many open outbound writes)
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-3796
>                 URL: https://issues.jboss.org/browse/AS7-3796
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Clustering, EJB, Remoting
>    Affects Versions: 7.1.0.Final
>            Reporter: Radoslav Husar
>            Assignee: David Lloyd
>            Priority: Critical
>             Fix For: 7.1.1.Final
>
>
> David and Jaikiran,
> lets revisit this topic. I still think were are leaking messages in remoting3. Badly. Even though I set MAX_O_Ms to 100K it still results in:
> {noformat}
> 2012/02/16 08:34:48:728 EST [WARN ][Runner - 227] SFCORE_LOG - Error sampling data:  <org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.>
>         org.jboss.smartfrog.loaddriver.RequestProcessingException: Could not get valid response. Runner: 227.
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:79)
> 	at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
> 	at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
> 	at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.reflect.UndeclaredThrowableException
> 	at $Proxy0.getSerialAndIncrement(Unknown Source)
> 	at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
> 	... 3 more
> Caused by: org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111)
> 	at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
> 	at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:235)
> 	at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:193)
> 	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
> 	at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
> 	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
> 	at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
> 	at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
> 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
> 	at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
> 	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
> 	... 5 more
> {noformat}
> Here is a snip from the client properties:
> {noformat}
> remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
> remote.connections=perf18,perf19,perf20,perf21
> remote.connection.perf18.host=perf18
> remote.connection.perf18.port=4447
> remote.connection.perf18.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
> remote.connection.perf18.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=100000
> {noformat}

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

        


More information about the jboss-jira mailing list