Bug 1005441

Summary: can't threaddump on an app after it's started from a stopped state.
Product: OpenShift Online Reporter: Peter Ruan <pruan>
Component: ContainersAssignee: Jhon Honce <jhonce>
Status: CLOSED NOTABUG QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: mfojtik, pruan, qiuzhang, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-09 20:58:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Peter Ruan 2013-09-06 23:56:27 UTC 
Description of problem:
  Broker reports that it can't detect applicationi PID, after the app is stopped and started back up and followed by a 'rhc threaddump' command.


Version-Release number of selected component (if applicable):
current

How reproducible:
always.

Steps to Reproduce:
1. create a ruby app
2. stop the app
3. start the app to bring it back online
4. do 'rhc threaddump <app_name>'


Actual results:
 Unable to detect application PID. Check the application's availability by accessing http://ngzozq-pppp.rhcloud.com


Expected results:
able to execute threaddump.

Additional info:
Comment 1 Qiushui Zhang 2013-09-09 07:20:04 UTC 
Hi Peter,

Did you visit the website of the app before you do the threaddump after app started?

You need to visit the app from website in browser or by curl command, before every threaddump. I did not see this step in your bug description.


Best Regards,
Walter
Comment 2 Michal Fojtik 2013-09-09 09:53:17 UTC 
IMHO the 'curl' is something which the 'rhc threadump' should do automatically.
Comment 3 Peter Ruan 2013-09-09 19:05:28 UTC 
Hi Walter,
  I didn't visit the app's page for ruby, but I didn't have to do that for jboss apps.

Jhon,
  I looked at the problem again and it looks like threaddump does not work after the app is created...stopping the app or not doens't seem to play a part in this problem.  When I looked at the development.log file, broker reports a 200 when the RHC command is run.

Thanks,
-peter