Just a heads up: we had a similar usecase at a client, but unfortunatly they were using a windows cluster where one node owned the shared drive where the logs had to be written to. The problem was that when you switched ownership of the drive while the application was logging in prudent mode, the file lock could not always be released. This means the next time you tried to log, the blocking lock() call would hang infinitely. After this happened a few times (caught it before production luckily), we wrote custom appenders with non-blocking locking and now we usually log asynchronously which avoids the problem alltogether (no prudent mode needed).<br>
<br><div class="gmail_quote">On 7 April 2011 18:44, Ceki Gulcu <span dir="ltr"><<a href="mailto:ceki@qos.ch">ceki@qos.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
As David mentioned prudent mode caters for this use case. It should should work nicely.<br>
<br>
BTW, I did not see get the original message from "LogbackUser" apparently posted from nabble.<br><font color="#888888">
<br>
-- <br>
Ceki<br>
<br>
QOS.ch, main sponsor of cal10n, logback and slf4j open source projects, is looking to hire talented software engineers. For further details, see <a href="http://logback.qos.ch/job.html" target="_blank">http://logback.qos.ch/job.html</a></font><div class="im">
<br>
<br>
<br>
On 07.04.2011 17:56, David Roussel wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Use prudent mode - <a href="http://logback.qos.ch/manual/appenders.html#FileAppender" target="_blank">http://logback.qos.ch/manual/appenders.html#FileAppender</a><br>
<br>
<br>
<br>
LogbackUser wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Are there any configuration properties through which multiple<br>
web-applications using logback could be configured to log to the same log<br>
file? This is taking into consideration that the messages would be logged<br>
concurrently without losing any messages.<br>
<br>
The reason I ask this question is that - we have a clustered environment<br>
of glassfish server instances where the same web application is installed<br>
on all the server instances in the cluster.<br>
<br>
</blockquote>
<br>
</blockquote>
<br></div><div><div></div><div class="h5">
_______________________________________________<br>
Logback-user mailing list<br>
<a href="mailto:Logback-user@qos.ch" target="_blank">Logback-user@qos.ch</a><br>
<a href="http://qos.ch/mailman/listinfo/logback-user" target="_blank">http://qos.ch/mailman/listinfo/logback-user</a><br>
</div></div></blockquote></div><br>