+++ 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
Looks like we have three reports for this issue: bug 1084427 was filed against Online, it was cloned as this bug for Enterprise, and then it was cloned a second time as bug 1131190, also for Enterprise. The defect was fixed in Enterprise, and consequently bug 1131190 was closed. As far as I can tell, this bug and bug 1131190 were tracking the same defect in the same version of the same product, and bug 1131190 was referenced in the advisory and marked closed, so I am marking this bug as a duplicate. *** This bug has been marked as a duplicate of bug 1131190 ***