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

Managed server shutdown unexpectedly when timeout during connection request to HC

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 9.0.0.Alpha1
    • 8.1.0.Final
    • Management
    • None

      Sometimes managed server shutdown unexpectedly when managed server tries to connect to the HC and got lengthly Full GC.

      java.io.IOException: JBAS012175: Channel closed
      at org.jboss.as.server.mgmt.domain.HostControllerConnection.getChannel(HostControllerConnection.java:101)
      at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
      at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:100)
      at org.jboss.as.server.mgmt.domain.HostControllerConnection.reConnect(HostControllerConnection.java:171)
      at org.jboss.as.server.mgmt.domain.HostControllerClient.reconnect(HostControllerClient.java:98)
      at org.jboss.as.server.DomainServerMain.main(DomainServerMain.java:138)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at org.jboss.modules.Module.run(Module.java:292)
      at org.jboss.modules.Main.main(Main.java:455)

      The current DomainServerMain exits on the connetion error.

      The scenario is:

      1. server tries to connect to the HC
      2. server Full GC
      3. HC is waiting a request from server, read timeout, closes the sock
      4. server resumed from GC, failed to send the req to the HC and exit

              emuckenhuber_jira Emanuel Muckenhuber (Inactive)
              rhn-support-tkimura Takayoshi Kimura
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: