Bug 978890
Summary: | Threaddump doesn't work well for scalable jboss and ruby application | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Gaoyun Pei <gpei> |
Component: | Containers | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED DEFERRED | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.2.0 | CC: | libra-onpremise-devel, lmeyer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
For a Ruby scaled application, the threaddump operation is not enabled. For a JBoss scaled application, the directions indicate only how to see the thread dump on the primary gear.
Consequence:
The user cannot (or cannot easily) retrieve thread dumps for all gears in a multi-gear application.
Fix:
Result:
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-08-15 14:25:36 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: | |
Embargoed: | |||
Bug Depends On: | 974933 | ||
Bug Blocks: |
Description
Gaoyun Pei
2013-06-27 09:27:51 UTC
Agree we'd like this to work better; not going to happen for the 1.2 release. We'll pick this up during the next rebase (provided it's fixed upstream). |