That's strange.
Just some thoughts ...
Is this specific to a particular appender? ... or is Log4j shutting
down entirely for all appenders? So, if you were writing to a JDBC appender
in A for example, does shutting down B stop the JDBC calls too.
Also, if B is started up again, does A pick back up?
I was just curious also if A and B are in the same JVM. I'm assuming from
your subject line the JVM's are different.
Mike
-----Original Message-----
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Friday, February 28, 2003 12:51 PM
To: Log4J Users List
Subject: RE: Question regarding two JVMs, one file
Hi,
I'm not asking for synchronization across JVMs. I don't care about the
order of logging statements in the file itself or anything like that.
I just don't want System B's shutdown to affect System A. Right now the
only spot at which System B's shutdown affects System A is that System A's
logging statements do not show up in the file.
Yoav Shapira
Millennium ChemInformatics
>-----Original Message-----
>From: Ceki G�lc� [mailto:[EMAIL PROTECTED]
>Sent: Friday, February 28, 2003 12:47 PM
>To: Log4J Users List
>Subject: Re: Question regarding two JVMs, one file
>
>
>Well, this is "normal" because there is no synchronization of resources
>between multiple JVMs. I am not sure if the NIO API has changed this but
>for regular java.io you can't share across JVMs.
>
>At 12:42 PM 2/28/2003 -0500, you wrote:
>
>>Howdy,
>>I have the following:
>>
>>System A uses a log4j configuration file, which defines one file
>>appender.
>>System B uses the same log4j configuration file, so it's writing to the
>>same file appender.
>>
>>System A is long-lived, typically weeks at a time. System B is
>>short-lived, typically runs once a day for about an hour. Whenever
>>System B is started, System A is already running and writing to the log
>>file.
>>
>>It seems like System B starts up OK, reads and configuration file, and
>>starts writing to the same log file as System A. So far so good.
>>However, it also seems like when System B is done, it exits (the JVM
>>exits) properly, and then System A can no longer write to the log file.
>>
>>System B does not explicitly shut down log4j, so I would expect System A
>>to continue to hold an open handle to the log file and keep writing to
>>it. Am I missing something? There are no exceptions in any of my logs
>>nor on the console.
>>
>>Thanks in advance,
>>
>>Yoav Shapira
>>Millennium ChemInformatics
>>
>>
>>
>>
>>
>>This e-mail, including any attachments, is a confidential business
>>communication, and may contain information that is confidential,
>>proprietary and/or privileged. This e-mail is intended only for the
>>individual(s) to whom it is addressed, and may not be saved, copied,
>>printed, disclosed or used by anyone else. If you are not the(an)
>>intended recipient, please immediately delete this e-mail from your
>>computer system and notify the sender. Thank you.
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>
>--
>Ceki
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential, proprietary
and/or privileged. This e-mail is intended only for the individual(s) to
whom it is addressed, and may not be saved, copied, printed, disclosed or
used by anyone else. If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the
sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------------------
This message and any included attachments are from Siemens Medical Solutions
Health Services Corporation and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
