Bug 798553 - Couldn't find thread dump log file for jboss app
Summary: Couldn't find thread dump log file for jboss app
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 09:00 UTC by bzhao
Modified: 2015-05-14 22:52 UTC (History)
1 user (show)

Fixed In Version: devenv_1650
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-02 21:56:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description bzhao 2012-02-29 09:00:05 UTC
Description of problem:
Couldn't generate thread dump log for jboss app after executing "rhc-ctl-app -a jbosstest2 -c threaddump", this file $appname/jbossas-7/stdout.log  does not exist 

Version-Release number of selected component (if applicable):
rhc-0.87.6-1.el6_2.noarch
rhc-cartridge-jbossas-7-0.87.11-1.el6_2.noarch

How reproducible:
Always

Steps to Reproduce:
1.Create an jbossas app.
# rhc-create-app -t jbossas-7 -predhat -a jbosstest2 -p xxx

2.execute  rhc-ctl-app, the thread dump will go to a new log file (stdout.log)
rhc-ctl-app -a jbosstest2 -p xxx -c threaddump

3.Access this file via rhc app tail
# rhc app tail -a jbosstest2 -f jbosstest2/jbossas-7/stdout.log
  
Actual results:
It'll output error messages said that "Could not find any files matching glob"

Expected results:
Can generate thread dump for jboss app and can access stdout.log vis rhc app tail

Additional info:
$appname/jbossas-7/stdout.log even does not exists for jbossas-7 app,but it existed before for jbossas-7.0 even if without thread dump.
 
# rhc app tail -a jbosstest2 -f jbosstest2/jbossas-7/stdout.log
Password: 
Attempting to tail files: jbosstest2/jbossas-7/stdout.log
Use ctl + c to stop

Could not find any files matching glob

Comment 1 bzhao 2012-03-01 07:11:00 UTC
Passed verification against rhc-0.87.7-1.el6_2.noarch


Note You need to log in before you can comment on or make changes to this bug.