Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 959575

Summary:	log4j-jboss-logmanager LoggingEvent does not properly serialize ThrowableInformation and loses stack information.
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	csams
Component:	Logging	Assignee:	James Perkins <jperkins>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.1
Target Milestone:	---
Target Release:	TBD EAP 6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-03 20:42:10 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:
Bug Blocks:	958311, 958971

Description csams 2013-05-03 20:34:01 UTC

Description of problem:
The LoggingEvent class of log4j-jboss-logmanager does not properly serialize ThrowableInformation and loses stack information if handled by an appender like JMSAppender.


Version-Release number of selected component (if applicable):
JBoss Enterprise Application Platform (EAP) 6.0.1

How reproducible:
Always

Steps to Reproduce:
Use a JMSAppender to send LoggingEvent containing a Throwable to a remote destination.
  
Actual results:
The message is preserved, but any stack information in the original message is lost.

Expected results:
The stack information is preserved.

Additional info:

Comment 2 James Perkins 2013-05-03 20:42:10 UTC

Changes have been made to the upstream log4j-jboss-logmanager project.