Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-users] useFileMappedBuffer doesn't appear to disable memory mapped log file created from webapp - Jetty 7.3 - Apache Commons Daemon


I'm trying to determine if Jetty 7.3 can be configured to 'deal with locked windows files' when the file (shibboleth idp-process.log) exists outside of the jetty directory and is written to from a context deployed webapp (IdP) under Jetty.

I was able to disable file memory mapping for CSS/JSP files inside of %JETTY_HOME%' using instructions in this link:

Unfortunately it didn't work for the shibboleth logfile, which results in daily log rotation failing.

My Shibboleth IdP 2.3.8 is running under jetty 7.3, which is running as a service on Windows Server 2008 using Apache daemons - procrun.

I read the following post:

I installed "Handle" from (targetted at searching for open file references) and the output of this command on idp-process:

Handle v3.51
Copyright (C) 1997-2013 Mark Russinovich
Sysinternals -

java.exe pid: 3688 type: File 5F8: C:\opt\shibboleth-idp\logs\idp-process.log

I'm trying to understand if this is a locking issue with Jetty or with Apache Commons Procrun ?

Any help or pointers with this would be greatly appreciated,

Thanks and Kind Regards


*Karen Murphy*
Systems Analyst - Bibliographic Services
The Library at Queen's
Queen's University Belfast
Belfast BT7 1LP
Tel: 028 90976260
Email: k.l.murphy@xxxxxxxxx

Back to the top