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:
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
IMHO the 'curl' is something which the 'rhc threadump' should do automatically.
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