-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
7.2.3.GA
Closing remote outbound channels takes only a partial effect. As shutdownWrite is invoked, the channels is partially closed. The close() message we see being called in the sequence does not result in a protocol message sent to the other end.
This can result in the Too many outbound channels open error:
Suppressed: org.jboss.remoting3.ProtocolException: Too many channels open at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:194) at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335) at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109) at org.jboss.remoting3.ClientServiceHandle.getClientService(ClientServiceHandle.java:80)
- clones
-
REM3-346 Remote channels config for max outbound and inbound channels must be equal to min value of both ends
- Resolved
-
JBEAP-18322 [GSS](7.3.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed
- Closed
-
EJBCLIENT-348 Add trace logging for EJBClientContext creation and channel opening
- Resolved
-
REM3-345 Add trace logging for ClientServiceHandle opening and closing channels
- Resolved
- is incorporated by
-
JBEAP-17683 [GSS](7.2.z) Upgrade JBoss Remoting from 5.0.16.Final-redhat-00001 to 5.0.17.Final-redhat-00001
- Closed
-
JBEAP-18318 [GSS](7.2.z) Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final
- Closed
- relates to
-
EJBCLIENT-347 EJBClientContexts create oubound channels that are never closed
- Resolved