[ https://issues.jboss.org/browse/TEIID-2402?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2402. ----------------------------------- Resolution: Done Marking the session object available to all log messages doesn't seem necessary. Also jboss views the use of the mdc for potentially mutable objects as an anti-pattern and forces the values to string. Any other approach such as the manipulation of the log record parameters seems like a just a hack, so the approach here is to just put the session in and vdb name/version strings in the mdc. The docs have been updated to describe the mdc properties and the standalone.xml was updated to include the session in all of the messages (although this is redundant in some messages). The customized logger may use the admin api if needed to get the session based upon the session id. Beyond this if someone absolutely needs additional context information in the logging layer from the same thread as the caller, then the approach should be to reference the DQPWorkContext - but that should be considered an unsupported use of an internal api. -- 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