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

Details

    • 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

    Description

      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.

      Attachments

        Issue Links

          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20438 [GSS](7.3.z) Upgrade JBoss Remoting from 5.0.19.Final-redhat-00001 to 5.0.20.Final-redhat-00001

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-5218 Upgrade JBoss Remoting to 5.0.20.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5105 ProtocolConnectionUtils may leak connection objects whose future takes too long to complete

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: