My experience with file locks on NFS is "use at your own risk". Some NFS implementations are better than others. If you must log to a single file I would recommend writing to a socket and then have a single process write to the file. Although many people here seem to have no problems, in the data center I work on we ran into this years ago and don't allow it anymore. Ralph On Dec 28, 2011, at 1:19 PM, <ThomasSchuessler2@Eaton.com> <ThomasSchuessler2@Eaton.com> wrote:
We are getting stuck threads, any advice?
####<Dec 28, 2011 9:29:30 AM EST> <Error> <WebLogicServer> <[obfuscated]> <soa_server1> <[STANDBY] ExecuteThread: '395' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8f08ad23754ca371:-6015b447:13484e5a335:-7ffe-0000000000005269> <1325082570435> <BEA-000337> <[STUCK] ExecuteThread: '261' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "707" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@429fb0e6[ POST /Custom[obfuscated]Service/Custom[obfuscated]Port HTTP/1.1 TE: trailers, deflate, gzip, compress User-Agent: Oracle HTTPClient Version 10h SOAPAction: "null" Authorization: [obfuscated] Accept-Encoding: gzip, x-gzip, compress, x-compress ECID-Context: 1.a161c6d66e04e744:-2716b1b5:1346c7f4437:-7ffe-00000000000a19aa;kXhDsLK[ obfuscated]KIVPToLQSJLQSqPRO_GNRmKS Content-type: text/xml; charset=UTF-8 Content-Length: 3607 Connection: Keep-Alive Proxy-Client-IP: [obfuscated] X-Forwarded-For: [obfuscated] X-WebLogic-KeepAliveSecs: 30 X-WebLogic-Force-JVMID: unset X-WebLogic-Request-ClusterInfo: true
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: Thread-1020 "[STUCK] ExecuteThread: '261' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, blocked, priority=1, DAEMON> { -- Blocked trying to get lock: java.lang.Object@489d327d[fat lock]
ch.qos.logback.core.OutputStreamAppender.subAppend(OutputStreamAppender. java:205)
ch.qos.logback.core.rolling.RollingFileAppender.subAppend(RollingFileApp ender.java:149)
ch.qos.logback.core.OutputStreamAppender.append(OutputStreamAppender.jav a:104)
ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAp penderBase.java:67)
ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(App enderAttachableImpl.java:51) ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:281) ch.qos.logback.classic.Logger.callAppenders(Logger.java:267)
ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:468 ) ch.qos.logback.classic.Logger.filterAndLog_2(Logger.java:450) ch.qos.logback.classic.Logger.debug(Logger.java:559)
-----Original Message----- From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of ceki Sent: Mittwoch, 21. Dezember 2011 18:55 To: logback users list Subject: Re: [logback-user] Prudent [sic!] mode logging to NFS-mounted file
Logback should have complained about the unknown property. Anyway, let us know if prudent mode work with NFS. (Prudent mode under NFS was tested a long time ago and if I remember correctly it worked fine.) -- Ceki http://twitter.com/#!/ceki
On 21.12.2011 18:40, ThomasSchuessler2@Eaton.com wrote:
Thank you very much for the fast answer. I feel so stupid.
-----Original Message----- From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of ceki Sent: Mittwoch, 21. Dezember 2011 17:49 To: logback users list Subject: Re: [logback-user] Prudent mode logging to NFS-mounted file
Check spelling of prudent (not prudend).
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
-------------------------------------------------------------------------- _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user