Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-13886

Remoting outbound channels are not closed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 18.0.1.Final, 20.0.1.Final
    • Remoting
    • Hide

      we have a clustered environment (2 nodes i.e master and slave) where we have multiple EJBs deployed between multiple jvms(appservers). when we are running test (~1200 to 1500 TPS) , we are observing open connections gets exhausted and EJB lookup starts failing with above mentioned error/exception.

      Show
      we have a clustered environment (2 nodes i.e master and slave) where we have multiple EJBs deployed between multiple jvms(appservers). when we are running test (~1200 to 1500 TPS) , we are observing open connections gets exhausted and EJB lookup starts failing with above mentioned error/exception.
    • Migration
    • Undefined
    • ---
    • ---

      We are seeing below issue in Wildfly 18 and 20 which is blocking our migration from wildfly10 but not seeing same issue in wildfly10.

      It seems similar issue has been opened in JBEAP, https://issues.redhat.com/browse/JBEAP-18322 

       

      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)

       

       

              flaviarnn Flavia Rainone
              pn556p Pankaj Narkhede (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: