logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30588] - log4j cannot parse stacktraces from JRockit
Date Fri, 27 Apr 2007 21:12:15 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30588>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30588


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Additional Comments From carnold@apache.org  2007-04-27 14:12 -------
I've tested with JRockit R27.2.0 both 1.4.2 and 1.6 and on both Windows and Linux and it appears
that the 
stack traces in JRockit look just like Sun stack traces.  I'm assuming that the behavior has
changes since 
this bug was filed.  The change seems innocuous, but it would be nice to know that we are
doing some 
good on a change.  I have fixed the unit tests so they pass on JRockit by explicitly setting
the thread 
names in the test.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message