Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 989484 - Add jboss stack trace to log collector
Add jboss stack trace to log collector
Status: CLOSED UPSTREAM
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-log-collector (Show other bugs)
3.3.0
All Linux
medium Severity low
: ---
: 3.3.0
Assigned To: Sandro Bonazzola
Tareq Alayan
integration
: Triaged
Depends On: 916928
Blocks: 1019461
  Show dependency tree / graph
 
Reported: 2013-07-29 07:01 EDT by Roy Golan
Modified: 2015-09-22 09 EDT (History)
12 users (show)

See Also:
Fixed In Version: rhevm-log-collector-3.3.1-1.el6ev
Doc Type: Bug Fix
Doc Text:
This update adds JBoss stack trace support to the rhevm-log-collector. The "jbosstrace" option sends a SIGQUIT signal to the JBoss process launched by ovirt-engine, causing a dump of the stack trace to /var/log/ovirt-engine/console.log. Other JBoss instances will not receive that signal.
Story Points: ---
Clone Of: 916928
Environment:
Last Closed: 2013-10-01 02:19:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 19365 None None None Never
oVirt gerrit 19602 None None None Never
Red Hat Product Errata RHBA-2014:0039 normal SHIPPED_LIVE rhevm-log-collector bug fix and enhancement update 2014-01-21 16:52:46 EST

  None (edit)
Description Roy Golan 2013-07-29 07:01:14 EDT 
complex scenario bugs, which are hard to reproduce will find this really helpful. A java stack trace will show us running threads and they're state and will reveal deadlock if exist.

how to create a stack trace? 
if jboss is the application server then its usually enough to

kill -3 `pgrep -f jboss`

and the trace will go into /var/log/ovirt-engine/console.log
Comment 1 Sandro Bonazzola 2013-09-18 08:50:24 EDT 
patch pushed upstream master.

added jbosstrace option, enabled by default, to engine
sos plugin.
The new option send a SIGQUIT signal to the JBoss
process launched by ovirt-engine, causing a dump of
the stack trace to /var/log/ovirt-engine/console.log.

Other JBoss instances will not receive that signal.
Comment 2 Sandro Bonazzola 2013-09-27 02:33:06 EDT 
Merged on upstream master and 3.3 branch.
Comment 4 Charlie 2013-11-27 20:15:58 EST 
This bug is currently attached to errata RHBA-2013:15255. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.