Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1056525 - "thread dump file: info is missing in REST response to thread dump
Summary: "thread dump file: info is missing in REST response to thread dump
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Master
Version: 1.x
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Lili Nader
QA Contact: libra bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-22 11:31 UTC by Oleg Fayans
Modified: 2016-12-01 00:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-01-22 12:43:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Oleg Fayans 2014-01-22 11:31:23 UTC
Description of problem:

When we request a threaddump via REST request, the response should tell in which file to search for the dump. It does not now

Version-Release number of selected component (if applicable):
reproduced on current INT instance and on devenv with ami: ami-0b132e62

How reproducible:

Steps to Reproduce:
1. create a ruby-1.9 app with mysql cartridge
2. request a threaddumpwith a REST request:
curl -k -H "Accept: application/xml" --user "<username:password>" https://<broker>/broker/rest/domains/<domain_name>/applications/<app_name>/events -X POST -d event=thread-dump

Actual results:
broker response does not contain any hint where to search the dump file

Expected results:

Should be something like this: 
The thread dump file will be available via: rhc tail rb1 -f ruby-1.8/logs/error_log-20140121-* -o '-n 250'
Additional info:

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