Bug 973856 - Add custom logging handler to route log messages to files based on deployment currently executing
Summary: Add custom logging handler to route log messages to files based on deployment...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: TBD EAP 6
Assignee: Kyle Lape
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-13 02:05 UTC by Kyle Lape
Modified: 2018-12-02 17:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-16 16:05:01 UTC
Type: Feature Request
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker PRODMGT-438 0 Major Resolved New logging handler that emulates Log4J's TCLMFilter 2016-06-23 04:15:29 UTC

Description Kyle Lape 2013-06-13 02:05:49 UTC
Comment 3 James Perkins 2014-09-16 16:05:01 UTC 
According the issues linked the issue was resolved and the latest versions of the logmanager and log4j-jboss-logmanager should be in the current release.
Comment 4 Kyle Lape 2014-09-18 21:59:19 UTC 
Changing to WONTFIX because this is not actually in EAP 6.  

Honestly I probably shouldn't have opened this BZ to begin with because it should be an internal PRODMGT Jira until it's been approved for implementation by PM.  If it does get worked on in the future, we can open a new BZ at that time (I guess).
Note You need to log in before you can comment on or make changes to this bug.