Recently I ran across a problem in which the Location Info (Class Name,
Method Name, etc.) was not generated appropriately in a Websphere 3.5 VM.
The root problem was the Stack Trace format generated by the VM. Inside
optimized code the trace might look like:
java.lang.Exception
at testlog4j.Test.main(Test.java(Compiled Code))
Because the LocationInfo Class uses the LAST index of '(' as it's starting
point for discovering the File, Method, and Class names, this Location Info
is invalid. I fixed LocationInfo locally to handle Websphere's bizarre
traces. It would be beneficial to propagate this fix into upcoming releases
of Log4j. I was unable to contact the author of this class (Mathias
Rupprecht). Please advise.
Regards,
Andy Day
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
