[jboss-jira] [JBoss JIRA] Resolved: (JBAS-9254) Crashed/killed server not detected
Kabir Khan (JIRA)
jira-events at lists.jboss.org
Wed Apr 6 10:55:53 EDT 2011
[ https://issues.jboss.org/browse/JBAS-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kabir Khan resolved JBAS-9254.
------------------------------
Assignee: Kabir Khan
Resolution: Duplicate Issue
Handled by JBAS-8943. If that does not fix it once in master, please reopen the issue
> Crashed/killed server not detected
> -----------------------------------
>
> Key: JBAS-9254
> URL: https://issues.jboss.org/browse/JBAS-9254
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Heiko Rupp
> Assignee: Kabir Khan
>
> Start domain mode. This brings up server-one and -two and -three as disabled.
> Kill from the shell server-two
> hrupp 56191 0,1 1,0 1058416 81580 s003 S+ 11:50am 0:54.69 /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java -Xms64m -Xmx256m -Dorg.jboss.boot.log.file=domain/servers/server-two/log/boot.log -Dlogging.configuration=file:/devel/jbas7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/domain/configuration/logging.properties -jar jboss-modules.jar -mp modules -logmodule org.jboss.logmanager -jaxpmodule javax.xml.jaxp-provider org.jboss.as.server
> snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$ kill 56191
> snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$ ps auxw|grep server-two
> snert:/im/rhq/modules/plugins/jboss-as-7 hrupp$
> Hostcontroller log shows:
> [Server:server-two] 16:39:29,310 INFO [org.jboss.as.logging] (MSC service thread 1-1) Restored bootstrap log handlers
> [Server:server-two] 16:39:29,314 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Removed JDBC Data-source [java:/H2DS]
> [Server:server-two] 16:39:29,315 ERROR [org.jboss.as.management] (Read thread for /0.0.0.0:9999) java.net.SocketException: Socket closed
> [Server:server-two] 16:39:29,317 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA-32018 Destroying TransactionManagerService
> [Server:server-two] 16:39:29,317 INFO [com.arjuna.ats.jbossatx] (MSC service thread 1-2) ARJUNA-32014 Stopping transaction recovery manager
> [Server:server-two] 16:39:29,317 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-4) JMX remote connector stopped
> [Server:server-two] 16:39:29,326 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-3) HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped
> [Server:server-two] 16:39:29,328 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3-SNAPSHOT "TBD" stopped in 30ms
> 16:39:29,661 INFO [org.jboss.as.process.Server:server-two.status] (reaper for Server:server-two) Process 'Server:server-two' finished with an exit status of 143
> Now go to e.g. the CLI
> [localhost:9999 /] cd /host=local/server-config=server-two
> [localhost:9999 server-two] :read-attribute(name=status)
> {
> "outcome" => "success",
> "result" => "STARTED",
> "compensating-operation" => undefined
> }
> Note that the server is still considered as running.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list