Bug 789831 - threaddump for ruby app won't work after app restarted
Summary: threaddump for ruby app won't work after app restarted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Containers
Version: 1.x
Hardware: All
OS: All
medium
low
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-13 05:41 UTC by Linqing Lu
Modified: 2013-04-30 22:46 UTC (History)
2 users (show)

Fixed In Version: devenv_1607
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 02:06:52 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Linqing Lu 2012-02-13 05:41:09 UTC
Description of problem:
`rhc app threaddump` with a restarted ruby app always hits "Application is stopped"

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

How reproducible:


Steps to Reproduce:
1. create a ruby app
2. restart this app (rhc-ctl-app or rhc-admin-ctl-app in devenv)
3. `rhc app threaddump`
  
Actual results:
Warned "Application is stopped. Ruby/Rack applications must be started by accessing the URL for a thread dump"

Expected results:
threaddump can be executed as expected

Additional info:
---------------------------
[root@intel-q8200novt-8-6 test]# rhc app restart -a ruby2
Password: 

RESULT:
Success

[root@intel-q8200novt-8-6 test]# rhc app status -a ruby2
Password: 

RESULT:
Total Accesses: 1
Total kBytes: 0
Uptime: 471
ReqPerSec: .00212314
BytesPerSec: 0
BytesPerReq: 0
BusyWorkers: 1
IdleWorkers: 0
Scoreboard: W....

[root@intel-q8200novt-8-6 test]# rhc app threaddump -a ruby2
Password: 

RESULT:
 Application is stopped. Ruby/Rack applications must be started by accessing the URL for a thread dump

Comment 1 Linqing Lu 2012-02-13 07:51:44 UTC
Tried to access the url and threaddump it again. It worked.
But i don't think this situation should happened after restart.
At least the error message was not accurate about "stopped". A little bit confusing.

Comment 2 Xiaoli Tian 2012-02-14 06:00:27 UTC
Verify this bug on devenv_1608,it still can not thread dump after restart for there's no access to the app, but the reminding message is changed as following:
 Application is inactive. Ruby/Rack applications must be accessed by their URL (http://appruby0-domx2.dev.rhcloud.com) before you can take a thread dump.

This sounds more reasonable.


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