Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-371

Channel is not closed when one of the peers cancels the connection

XMLWordPrintable

    • Hide

      -Start a domain master
      -Connect a domain slave
      -Use the following to induce a pause in the domain master:

      kill -STOP $DOMAIN_MASTER_PID

      -Note repeating retries on the slave:

      INFO  [org.jboss.as.host.controller] (Host Controller Service Threads - 464) WFLYHC0150: Trying to reconnect to master host controller.

      -After some time capture a heap dump, and check connection accumulation. With an OQL in MAT, these can be pulled easily like so:

      SELECT socketChannel.localAddress.holder.addr.holder.address, socketChannel.localAddress.holder.port, socketChannel.remoteAddress.holder.addr.holder.address, socketChannel.remoteAddress.holder.port FROM org.xnio.nio.NioSocketConduit
      Show
      -Start a domain master -Connect a domain slave -Use the following to induce a pause in the domain master: kill -STOP $DOMAIN_MASTER_PID -Note repeating retries on the slave: INFO [org.jboss.as.host.controller] (Host Controller Service Threads - 464) WFLYHC0150: Trying to reconnect to master host controller. -After some time capture a heap dump, and check connection accumulation. With an OQL in MAT, these can be pulled easily like so: SELECT socketChannel.localAddress.holder.addr.holder.address, socketChannel.localAddress.holder.port, socketChannel.remoteAddress.holder.addr.holder.address, socketChannel.remoteAddress.holder.port FROM org.xnio.nio.NioSocketConduit
    • Undefined

      This issue follows up on WFCORE-5105.

      When one of the peers cancels the connection, the underlying channel is not closed. This only happens when the provider involves the HTTP upgrade facility.

              yborgess1@redhat.com Yeray Borges Santana
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: