[jboss-jira] [JBoss JIRA] (WFCORE-1238) Domain Controller hung when deployment from CLI is interrupted.

Brian Stansberry (JIRA) issues at jboss.org
Wed Mar 2 15:26:00 EST 2016


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

Brian Stansberry commented on WFCORE-1238:
------------------------------------------

Is this still an issue with WildFly 10.0.0.Final? There have been quite a lot of changes in this general area in 9 and 10.

> Domain Controller hung when deployment from CLI is interrupted.
> ---------------------------------------------------------------
>
>                 Key: WFCORE-1238
>                 URL: https://issues.jboss.org/browse/WFCORE-1238
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>         Environment: Wildfly version 8.2.0
>            Reporter: Rahul Jain
>            Assignee: Brian Stansberry
>
> We are running the widlfly in Domain mode with the following configuration:
> 1) Host A running the domain controller
> 2) Host B running Host controller with one app server
> 3) Host C running Host controller with one app server
> When we deloy war using jboss-cli and due to some unforscene issue the jboss-cli client dies before the deployment is completed. But after this the Domain Controller didn't respond to any communication either via cli or console. We need to restart the domain controller to get it working.
> -----------------------------------------------------------------------------------------------------
> LOGS from Wildfly server (DC)
> This node IS Domain Controller.
> =========================================================================
>   JBoss Bootstrap Environment
>   JBOSS_HOME: /opt/wildfly
>   JAVA: /usr/java/default/bin/java
>   JAVA_OPTS: -Xms64m -Xmx512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 18:33:57,144 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
> 18:33:57,298 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 18:33:57,917 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
> [Host Controller] 18:33:58,120 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
> [Host Controller] 18:33:58,187 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
> [Host Controller] 18:33:58,975 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final
> [Host Controller] 18:33:59,003 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 18:33:59,015 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final
> [Host Controller] 18:33:59,123 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.6.Final
> [Host Controller] 18:33:59,162 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 192.168.1.203:9999
> [Host Controller] 18:34:01,237 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.1.203:9990/management
> [Host Controller] 18:34:01,237 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.1.203:9990
> [Host Controller] 18:34:01,238 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" (Host Controller) started in 3853ms - Started 44 of 46 services (13 services are lazy, passive or on-demand)
> [Host Controller] 18:34:09,845 INFO  [org.jboss.as.domain] (Host Controller Service Threads - 25) JBAS010918: Registered remote slave host "192.168.1.200", WildFly 8.2.0.Final "Tweek"
> [Host Controller] 18:34:26,326 WARN  [org.jboss.as.domain] (Remoting "cloudify-a2:MANAGEMENT" I/O-1) JBAS010929: Connection to remote host "192.168.1.200" closed unexpectedly
> [Host Controller] 18:34:26,328 INFO  [org.jboss.as.domain] (Remoting "cloudify-a2:MANAGEMENT" I/O-1) JBAS010925: Unregistered remote slave host "192.168.1.200"
> [Host Controller] 18:34:55,859 INFO  [org.jboss.as.domain] (Host Controller Service Threads - 26) JBAS010918: Registered remote slave host "192.168.1.200", WildFly 8.2.0.Final "Tweek"
> [Host Controller] 18:35:30,297 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /opt/wildfly/domain/data/content/cf/6a68fb1bc9d5f1a1a00228243ef94f23d5a370/content
> [Host Controller] 18:35:47,437 INFO  [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /opt/wildfly/domain/data/content/43/8ab1e9f1b69ad7bce0628b3d771eadffa09703/content
> [Host Controller] 18:35:55,915 ERROR [org.jboss.as.domain.deployment] (management-handler-thread - 1) JBAS010809: ConcurrentUpdateTask caught InterruptedException waiting for task ConcurrentServerGroupUpdateTask{server-group=A}; returning
> [Host Controller] 18:35:55,924 WARN  [org.jboss.as.host.controller] (management-handler-thread - 1) JBAS010802: Interrupted awaiting final response from server 192.168.1.200-0 on host 192.168.1.200
> [Host Controller] 18:35:55,942 WARN  [org.jboss.as.domain] (Remoting "cloudify-a2:MANAGEMENT" task-2) JBAS010929: Connection to remote host "192.168.1.200" closed unexpectedly
> [Host Controller] 18:35:55,942 INFO  [org.jboss.as.domain] (Remoting "cloudify-a2:MANAGEMENT" task-2) JBAS010925: Unregistered remote slave host "192.168.1.200"
> ----------------------------------------------------------------------------------------
> If you need anyother information, please let us know.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list