logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Baranski" <m...@secmgmt.com>
Subject RE: Strange error message
Date Fri, 18 Dec 2009 14:10:53 GMT
I will test again with the current version of log4j, thank you very much for
your response.

-------------------------------------------------------------
Mike Baranski
O: 919 788 9200
F: 919 510 0037
M: 919 395 0620

mike@secmgmt.com

CVI Authorized User Number: CVI-20080925-1020950
-------------------------------------------------------------

Warning: The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this message is
not the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify the original sender
immediately by replying to this message and then delete it from your
computer. All e-mail sent to this address will be received by the SMC
corporate e-mail system and are subject to archiving and review by someone
other than the recipient.


>-----Original Message-----
>From: Curt Arnold [mailto:curt.arnld@gmail.com] On Behalf Of Curt Arnold
>Sent: Friday, December 18, 2009 8:52 AM
>To: Log4J Users List
>Subject: Re: Strange error message
>
>The SVN HEAD implementation of QuietWriter currently has checks on the
>string parameter and exception catching that I believe have been added
>since the version that you are using.  Look at bugs 46144 and 46574 and
>see if they have any similarities to your situation.
>
>>>From the stack trace, it also looks like a JRE bug is a possibility.
>Could you check the Sun or other JRE vendors database to see if there is
>a reported issue.
>
>Please provide platform, JRE provider and version, or log4j version, all
>of those are very useful in tracking down issues.
>
>Could you test again with the current SVN HEAD and/or the latest
>available JRE>
>
>
>On Dec 17, 2009, at 9:07 AM, Mike Baranski wrote:
>
>> I'm got the following error message from an application that worked
>fine all
>> day yesterday, then stopped.  This particular debug statement was run
>a
>> number of times previously.
>>
>> The statement that's being run is:
>>
>> l.debug("Getting all roles for user");
>>
>> Any ideas?
>>
>> The error was:
>>
>> File:
>>
>> java/io/OutputStreamWriter.java
>>
>> Line number:
>>
>> 250
>>
>> ________________________________
>>
>> Stacktraces
>>
>> java.lang.ArrayIndexOutOfBoundsException
>>
>>    java.io.OutputStreamWriter.write(OutputStreamWriter.java:250)
>>
>>    java.io.Writer.write(Writer.java:152)
>>
>>    org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:47)
>>
>>    org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
>>
>>    org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
>>
>>
>org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:211)
>>
>>
>>
>org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(Ap
>pend
>> erAttachableImpl.java:65)
>>
>>    org.apache.log4j.Category.callAppenders(Category.java:203)
>>
>>    org.apache.log4j.Category.forcedLog(Category.java:388)
>>
>>    org.apache.log4j.Category.debug(Category.java:257)
>>
>>
>>
>com.secmgmt.beans.auth.jdbc.JDBCAuthProvider.getRolesForUser(JDBCAuthPro
>vide
>> r.java:67)
>>
>> -------------------------------------------------------------
>> Mike Baranski
>> O: 919 788 9200
>> F: 919 510 0037
>> M: 919 395 0620
>>
>> mike@secmgmt.com
>>
>> CVI Authorized User Number: CVI-20080925-1020950
>> -------------------------------------------------------------
>>
>> Warning: The information contained in this message may be privileged
>and
>> confidential and protected from disclosure. If the reader of this
>message is
>> not the intended recipient, you are hereby notified that any
>dissemination,
>> distribution or copying of this communication is strictly prohibited.
>If you
>> have received this communication in error, please notify the original
>sender
>> immediately by replying to this message and then delete it from your
>> computer. All e-mail sent to this address will be received by the SMC
>> corporate e-mail system and are subject to archiving and review by
>someone
>> other than the recipient.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org


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


Mime
View raw message