[teiid-issues] [JBoss JIRA] (TEIID-2267) Verify Custom Appenders (command, audit) work in AS7

[Siva Chemudupaty (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728441#comment-12728441 ] 

Siva Chemudupaty commented on TEIID-2267:
-----------------------------------------

Ramesh,

Thanks for the prompt reply. As I mentioned in my email earlier, at runtime the object that I get is ExtLogRecord. Is it possible to copy the contextInformation to the MDC /NDC for the ExtLogRecord ? Any high level suggestions that you can think of for the second alternative that you mentioned above ?

Thanks
Siva
                
> Verify Custom Appenders (command, audit) work in AS7
> ----------------------------------------------------
>
>                 Key: TEIID-2267
>                 URL: https://issues.jboss.org/browse/TEIID-2267
>             Project: Teiid
>          Issue Type: Task
>          Components: Common
>    Affects Versions: 8.0
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>             Fix For: 8.2
>
>
> AS7 has different logging configuration than the AS 5.1. The appenders do work as is, and configuration may be different. However based on this AS7-4925 it looks like Log4J appender can be supported in AS 7.2. This information needs to be verified and update Teiid documentation at 
> https://docs.jboss.org/author/display/teiid/Custom+Logging
> https://docs.jboss.org/author/display/teiid/Logging
> Since 7.2, is not available yet if we want to fix this change the document to use java.util.logging.Handler interface to extend and add configuration like below in the logging subsystem in standalone-teiid.xml file
> {code}
> <custom-handler name="COMMAND" module="" class="org.something.CustomAppender">
> </custom-handler>
>   <logger category="org.teiid.COMMAND_LOG">
>       <level name="INFO"/>
>       <handler name="COMMAND"/>
>   </logger>
> {code}

--
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