Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13547

"Exception accepting request, closing server channel TCP server (NIO) <3a913c2>: java.nio.channels.ClosedChannelException" occurs during server termination on Solaris intermittently

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.CR4
    • None
    • Server
    • None

    Description

      This is a new issue in EAP 7.1.0.CR3 build. It has happened intermittently only on Solaris so far for both standalone as well as domain mode.
      There is following ERROR in server.log or host-controller.log when stopping server or host controller:

      ERROR [org.xnio.nio.tcp.server] (management Accept) Exception accepting request, closing server channel TCP server (NIO) <3a913c2>: java.nio.channels.ClosedChannelException
	at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:235)
	at org.xnio.nio.QueuedNioTcpServer.handleReady(QueuedNioTcpServer.java:477)
	at org.xnio.nio.QueuedNioTcpServerHandle.handleReady(QueuedNioTcpServerHandle.java:38)
	at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)

      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-13551 Upgrade XNIO to 3.5.4.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. XNIO-309 Socket accept errors should log at DEBUG, not ERROR

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

              dlloyd@redhat.com David Lloyd
              pjelinek@redhat.com Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: