[
https://issues.jboss.org/browse/AS7-3792?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3792:
-----------------------------------
The code to make sure that only the allowed number of channel messages are sent from the
EJB client, is in place. The reason for why this exception still occurred with this code
in place was investigated in
https://issues.jboss.org/browse/AS7-3796. I'm marking
this as duplicate because there wasn't anything done specific to this issue and
there's no more safeguard that can be added from a EJB client API implementation point
of view.
Remote EJB client still throws exception rather than blocking
-------------------------------------------------------------
Key: AS7-3792
URL:
https://issues.jboss.org/browse/AS7-3792
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
Lets reopen this topic, there seems to be flaw in implementation of EJBCLIENT-23, I am
really seeing this exception with 1.0.2.Final client and AS 7.1.0.Final.
The exception is thrown on invoking method on the remote SFSB.
{noformat}
2012/02/16 08:34:58:715 EST [ERROR][Runner - 36] HOST
perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response.
<java.lang.reflect.UndeclaredThrowableException>
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.getSerialAndIncrement(Unknown Source)
at
org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
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: 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}
--
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