[jboss-jira] [JBoss JIRA] (WFLY-3468) Managed server shutdown unexpectedly when timeout during connection request to HC

James Livingston (JIRA) issues at jboss.org
Thu Aug 14 19:50:29 EDT 2014


    [ https://issues.jboss.org/browse/WFLY-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993109#comment-12993109 ] 

James Livingston commented on WFLY-3468:
----------------------------------------

To reproduce:
1) Uncomment the debugging example for server-one in domain/configuration/host.xml
2) Run domain.sh, and connect your debugger (port 8787 out of box)
3) Either suspect the "main" thread and use Step Out, or put a breakpoint on the line after StreamUtils.readUTFZBytes()
4) Run "kill -STOP $SERVER_ONE_PID" to suspend the process
5) Wait until the HC reports ReadTimeoutException
6) Use "kill -CONT $SERVER_ONE_PID", and it will drop into the debugger
7) Suspend the HC process as above
8) Step over the calls until it enters client.reconnect()
9) After it times out contacting the HC, it will catch an IOException (ConnectException if you reproduce this way, but others can occur)
10) Resume the HC process and do whatever debugging you want

> Managed server shutdown unexpectedly when timeout during connection request to HC
> ---------------------------------------------------------------------------------
>
>                 Key: WFLY-3468
>                 URL: https://issues.jboss.org/browse/WFLY-3468
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>    Affects Versions: 8.1.0.Final
>            Reporter: Takayoshi Kimura
>            Assignee: Emanuel Muckenhuber
>            Priority: Minor
>
> Sometimes managed server shutdown unexpectedly when managed server tries to connect to the HC and got lengthly Full GC.
> {quote}
> 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)
> {quote}
> The current DomainServerMain exits on the connetion error.
> The scenario is:
> # server tries to connect to the HC
> # server Full GC
> # HC is waiting a request from server, read timeout, closes the sock
> # server resumed from GC, failed to send the req to the HC and exit



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jboss-jira mailing list