James-
Thanks for the response.
For option 3 (the fastest solutions seems to always be preferred) is
there a way to insert the server name into the logfile name or path as a
parameter - so that the environment people don't have to change their
deployment procedures? (something like /logs/{$server.name}_System.out)
Thanks again!
Dave
-----Original Message-----
From: James Stauffer [mailto:[EMAIL PROTECTED]
Sent: Monday, September 11, 2006 12:15 PM
To: Log4J Users List
Subject: Re: log4j dailyrollingfileappender in managed server
environment
Two JVMs should be writting to the same file. Consider these options:
1. Write to a database.
2. Write a Socket and have a listener collect and write to a file.
3. Write to distinct files.
On 9/11/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> All-
>
>
>
> I am encountering a problem using the dailyrollingfileappender in a
> managed server environment. Both virtual server nodes are set to
write
> to the same logfile. The dailyrollingfileappender is supposed to
> archive the logfile every day (and it does), but after the archive,
one
> of the nodes starts writing to the proper logfile again, while the
other
> continues writing to the previous, now archived, file.
>
>
>
> Could this be a problem with the classpath or the closing of the
> filestreams of the different nodes? If we bounce the servers they
start
> working normally again.
>
>
>
> Any thoughts?
>
>
>
> Thanks,
>
> Dave
>
>
>
> This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the sender immediately and delete
the original. Any other use of the email by you is prohibited.
>
>
--
James Stauffer http://www.geocities.com/stauffer_james/
Are you good? Take the test at http://www.livingwaters.com/good/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This message is for the designated recipient only and may contain privileged,
proprietary, or otherwise private information. If you have received it in
error, please notify the sender immediately and delete the original. Any other
use of the email by you is prohibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
