log4j & file handles

[Stephen James <sj...@netjets.com>]

Hello all,

 

I am using log4j in websphere environment, and I'm seeing the JVM hold
onto the file handle after a successful log (single thread). This issue
is preventing the RollingFileAppender from archiving the log file before
it is overwritten (in windows...the operation can't complete if there is
a handle open on the file). At this point I am not sure what level of
architecture is to blame, log4j, websphere, or j2ee. So my question is
has anyone else had a problem working with java where the JVM is not
releasing the file handle? I'm using log4j1.2.14.

 

Thanks for any help!

Steve

 


This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error,  please advise the sender by reply e-mail and delete the message.

Re: log4j & file handles

[Arnauld Van Muysewinkel <ar...@gmail.com>]

> On 9/21/07, Stephen James <sj...@netjets.com> wrote:

> > I am using log4j in websphere environment, and I'm seeing the JVM hold
> > onto the file handle after a successful log (single thread). This issue
> > is preventing the RollingFileAppender from archiving the log file before
> > it is overwritten (in windows...the operation can't complete if there is
> > a handle open on the file). At this point I am not sure what level of
> > architecture is to blame, log4j, websphere, or j2ee. So my question is
> > has anyone else had a problem working with java where the JVM is not
> > releasing the file handle? I'm using log4j1.2.14.

2007/9/27, Sangeetha Priya S <ss...@gmail.com>:
>  Yes this is log4j a problem in windows OS, but got a mail from another
> developer, that the 1.4.15 has a patch that fixed RFA. and also he has sent
> a patch to log4j which is not yet officially released.
> But he told that this will work in other OS. so i'm waiting to test this in
> Linux. (since that is my production server). If it works there then it is
> fine for me.
>
> Anyways waiting for the next release to fix these issues.


See also: http://issues.apache.org/bugzilla/show_bug.cgi?id=43374

Yours faithfully,

-- 
Ir. Arnauld Van Muysewinkel

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

Re: log4j & file handles

[Sangeetha Priya S <ss...@gmail.com>]

Hi,
 Yes this is log4j a problem in windows OS, but got a mail from another
developer, that the 1.4.15 has a patch that fixed RFA. and also he has sent
a patch to log4j which is not yet officially released.
But he told that this will work in other OS. so i'm waiting to test this in
Linux. (since that is my production server). If it works there then it is
fine for me.

Anyways waiting for the next release to fix these issues.

Hope this helps.

Regards,
Sangeetha
On 9/21/07, Stephen James <sj...@netjets.com> wrote:
>
>
> Hello all,
>
>
>
> I am using log4j in websphere environment, and I'm seeing the JVM hold
> onto the file handle after a successful log (single thread). This issue
> is preventing the RollingFileAppender from archiving the log file before
> it is overwritten (in windows...the operation can't complete if there is
> a handle open on the file). At this point I am not sure what level of
> architecture is to blame, log4j, websphere, or j2ee. So my question is
> has anyone else had a problem working with java where the JVM is not
> releasing the file handle? I'm using log4j1.2.14.
>
>
>
> Thanks for any help!
>
> Steve
>
>
>
>
> This message contains information which may be confidential and
> privileged. Unless you are the addressee (or authorized to receive for the
> addressee), you may not use, copy or disclose to anyone the message or any
> information contained in the message. If you have received the message in
> error,  please advise the sender by reply e-mail and delete the message.