Hmm. I've been happily using log4j 1.1.3 on Solaris 8, Sun JVM
1.3.1-b24 (-server), and everything's been hunky-dory. However, now I'm
more out of raw development and focusing on performance, so I went to
modify my log4j configuration. I had been using a PatternLayout of:
log4j.appender.file.layout.ConversionPattern=%d{ISO8601} [%t] %p
(%C{1}.%M) - %m%n
which contains several items known to be slow, so I modified it to:
log4j.appender.file.layout.ConversionPattern=%d{ISO8601} [%t] %p - %m%n
and after several events through my application, JVM crashes, with
something like:
Unexpected Signal : 11 occurred at PC=0xfe0b5cf0
Function name=JVM_CurrentTimeMillis
Library=/usr/j2se/jre/lib/sparc/server/libjvm.so
I strongly suspect log4j, since when I switch back to my original
ConversionPattern, the crash doesn't happen. I'll do some more testing
with it, but does this ring any bells with anyone?
Thanks,
dwh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
