+++ This bug was initially created as a clone of Bug #1084427 +++ Description of problem: Create one jbossew/jbosseap app(e.g., myjbossew10), tailf app-root/logs/$cartridge.log in gear and stop app, found no stop related info shows in $cartridge.log file. Version-Release number of selected component (if applicable): devenv_4624 How reproducible: always Steps to Reproduce: 1.Create one jboss app #rhc app create myjbossews10 jbossews-1.0 2.Open Terminal:1 and tailf app-root/logs/$cartridge.log in gear # 3.Open Terminal:2 and stop app #rhc app stop myjbossew10 4.Check app-root/logs/$cartridge.log in Terminal:1 Actual results: No stop related info shows in $cartridge.log when stop app Expected results: Should have stop info when stop app in log Additional info: ===========This is previous log======================= [33m2014/03/04 05:38:36,343 INFO [org.hornetq.ra] (ServerService Thread Pool -- 71) HQ151003: HornetQ resource adaptor stopped [0m [33m2014/03/04 05:38:36,716 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment ROOT.war (runtime-name: ROOT.war) in 588ms [0m [33m2014/03/04 05:38:36,871 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 74) HQ221002: HornetQ Server version 2.3.13.Final (2.3.123, 123) [d0c9e9ba-a388-11e3-8827-f96303d1f615] stopped [0m [33m2014/03/04 05:38:36,880 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.1.GA (AS 7.3.1.Final-redhat-3) stopped in 738ms --- Additional comment from Balazs Varga on 2014-08-18 09:07:38 EDT --- The problem is that we send SIGKILL instead of SIGTERM to the processes, see: https://github.com/openshift/origin-server/blob/a9c5419101392a72f0429da3c66db55c1b71e5be/cartridges/openshift-origin-cartridge-jbossews/bin/control#L103 I'm going to talk about this with Dan Mace why was this necessary.
http://etherpad.corp.redhat.com/puddle-2-2-2014-10-07
Verify this bug with openshift-origin-cartridge-jbossews-1.29.1-1.git.149.c7fbca5.el6op.noarch, openshift-origin-cartridge-jbosseap-2.21.1-1.git.149.ef6cd67.el6op.noarch After creating a jbossews app, stop the app using "rhc app stop $app_name", monitor app-root/logs/$cartridge.log: ... Oct 08, 2014 4:27:57 PM org.apache.coyote.http11.Http11Protocol pause INFO: Pausing Coyote HTTP/1.1 on http-127.2.154.1-8080 Oct 08, 2014 4:27:58 PM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina Oct 08, 2014 4:27:58 PM org.apache.coyote.http11.Http11Protocol destroy INFO: Stopping Coyote HTTP/1.1 on http-127.2.154.1-8080 For jbosseap app, logs below could be seen in app-root/logs/$cartridge.log when stopping it: ... 2014/10/08 17:08:41,425 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] 2014/10/08 17:08:41,422 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003075: Coyote HTTP/1.1 pausing on: http-127.10.87.1/127.10.87.1:8080 2014/10/08 17:08:41,426 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] 2014/10/08 17:08:41,426 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003077: Coyote HTTP/1.1 stopping on : http-127.10.87.1/127.10.87.1:8080 2014/10/08 17:08:41,426 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) JBWEB003077: Coyote HTTP/1.1 stopping on : http-127.10.87.1/127.10.87.1:8080 2014/10/08 17:08:41,431 INFO [org.jboss.jaxr] (MSC service thread 1-4) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory 2014/10/08 17:08:41,434 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 68) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 2014/10/08 17:08:41,440 INFO [org.jboss.web] (ServerService Thread Pool -- 70) JBAS018224: Unregister web context: 2014/10/08 17:08:41,495 INFO [org.hornetq.ra] (ServerService Thread Pool -- 68) HQ151003: HornetQ resource adaptor stopped 2014/10/08 17:08:41,571 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 68) HQ221002: HornetQ Server version 2.3.21.Final (2.3.21, 123) [7e086a9e-4ec2-11e4-9923-d753ba1543a6] stopped 2014/10/08 17:08:41,640 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment ROOT.war (runtime-name: ROOT.war) in 266ms 2014/10/08 17:08:41,650 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: JBoss EAP 6.3.1.GA (AS 7.4.1.Final-redhat-3) stopped in 276ms
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2014-1796.html
*** Bug 1108058 has been marked as a duplicate of this bug. ***