[esb-java-dev] [jira] Resolved: (ESBJAVA-313) The fully qualified class name of the caller issuing the logging event printed as a question mark(?) in the Trace Logs

[indika kumara (JIRA)]

     [ http://www.wso2.org/jira/browse/ESBJAVA-313?page=all ]

indika kumara resolved ESBJAVA-313.
-----------------------------------

    Fix Version/s: 1.5-beta-1
       Resolution: Fixed

changed the conversion pattern . Trace Logger isn't for per and each class .

> The fully qualified class name of the caller issuing the logging event printed as a question mark(?) in the Trace Logs
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ESBJAVA-313
>                 URL: http://www.wso2.org/jira/browse/ESBJAVA-313
>             Project: WSO2 ESB
>          Issue Type: Bug
>          Components: Logging and Tracing
>    Affects Versions: 1.5-QA-b1
>         Environment: Ubuntu7.04, JDK1.5.0_12, Firefox 2.0.0.9
>            Reporter: Evanthika Amarasiri
>         Assigned To: indika kumara
>            Priority: Minor
>             Fix For: 1.5-beta-1
>
>
> Following is the pattern for the memory appender for trace logger
> ************************************************************************************************
> log4j.appender.TRACE_MEMORYAPPENDER.layout.ConversionPattern=[%X{host}] [%t] %-5p [%d{HH:mm:ss,SSS}] %C{1} - %m%n
> ************************************************************************************************
> When the trace logs are printed, the fully qualified class name is printed as a question mark [?]
> [testc-ubuntu] [HttpServerWorker-5] INFO [09:05:21,052] ? - Synapse received a new message for message mediation...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira