[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] Ravi Luthra commented on AS7-4925: ---------------------------------- One curiosity of mine is translation - If an application logs with Log4J, is there any translation between that log event and the log4j appender in JBoss (as managed by the log manager after this bug is fixed)? I can understand a translation occurring if the log even comes from JUL, Commons, or SLF - but if Log4J is the logging API and the Handling API - I'm hoping we can get the original event object. Reason I ask is we have a couple of APIs that would like to use Log4J's Object parameter to pump in special objects - and Log4J retains these objects in the LoggingEvent that gets sent to the Appender. However if this is not possible and the message gets converted to a String - we'll understand this as one of the unfortunate side effects of the logmanager subsystem. Our work-around would be to include a special appender in log4J's root logger that would hopefully not get closed or otherwise managed by JBoss - and from that appender we can perform our special logging. Overall this is probably the only EAP 5 to 6 transitional item we had a gap on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] Ravi Luthra edited comment on AS7-4925 at 7/10/12 6:07 PM: ----------------------------------------------------------- One curiosity of mine is translation - If an application logs with Log4J, is there any translation between that log event and the log4j appender in JBoss (as managed by the log manager after this bug is fixed)? I can understand a translation occurring if the log event comes from JUL, Commons, or SLF - but if Log4J is the logging API and the Handling API - I'm hoping we can get the original event object. Reason I ask is we have a couple of APIs that would like to use Log4J's Object parameter to pump in special objects - and Log4J retains these objects in the LoggingEvent that gets sent to the Appender. However if this is not possible and the message gets converted to a String - we'll understand this as one of the unfortunate side effects of the logmanager subsystem. Our work-around would be to include a special appender in log4J's root logger that would hopefully not get closed or otherwise managed by JBoss - and from that appender we can perform our special logging. Overall this is probably the only EAP 5 to 6 transitional item we have a no-alternative for. was (Author: homer400): One curiosity of mine is translation - If an application logs with Log4J, is there any translation between that log event and the log4j appender in JBoss (as managed by the log manager after this bug is fixed)? I can understand a translation occurring if the log event comes from JUL, Commons, or SLF - but if Log4J is the logging API and the Handling API - I'm hoping we can get the original event object. Reason I ask is we have a couple of APIs that would like to use Log4J's Object parameter to pump in special objects - and Log4J retains these objects in the LoggingEvent that gets sent to the Appender. However if this is not possible and the message gets converted to a String - we'll understand this as one of the unfortunate side effects of the logmanager subsystem. Our work-around would be to include a special appender in log4J's root logger that would hopefully not get closed or otherwise managed by JBoss - and from that appender we can perform our special logging. Overall this is probably the only EAP 5 to 6 transitional item we had a gap on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4925: --------------------------------------- James, can this be resolved? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-4925: --------------------------------------- Ah, I forgot I hadn't merged that one yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-4925: ------------------------------- Forum Reference: https://community.jboss.org/message/738947 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-4925: ------------------------------- Fix Version/s: (was: 7.1.3.Final (EAP)) Forum Reference: https://community.jboss.org/message/738947 (was: https://community.jboss.org/message/738947) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-4925?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-4925: ------------------------------- Fix Version/s: 7.1.4.Final (EAP) Git Pull Request: https://github.com/jbossas/jboss-as/pull/2984 (was: https://github.com/jbossas/jboss-as/pull/2984) Forum Reference: https://community.jboss.org/message/738947 (was: https://community.jboss.org/message/738947) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira