-
Bug
-
Resolution: Done
-
Major
-
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
-
EJBCLIENT-347 EJBClientContexts create oubound channels that are never closed
- Resolved
-
JBEAP-21285 [GSS](7.4.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed
- Closed
- is blocked by
-
JBEAP-21581 (7.3.z) REM3-377 - Use safeClose() in ClientServiceHandle.close()
- Closed
- is cloned by
-
JBEAP-17475 [GSS](7.2.z) EJBCLIENT-347 / REM3-350 - Remoting outbound channels are not closed
- Closed
- is related to
-
WFLY-13886 Remoting outbound channels are not closed
- Open
-
WFLY-14564 Close EJBClientContext when related service is closed
- Closed
- relates to
-
JBEAP-22021 [GSS](7.3.z) max-outbound-channels setting in remoting subsystem is not honored
- Closed