My team currently has Railo 4.2.1.008 running on a production server. We
are experiencing an issue with the server locking up and requiring a
restart of Jetty.
Right now it happens roughly every 9 hours or so, but this interval has
been getting shorter and shorter as the service gains more users.
I believe I have tracked down the issue to be related to logging - Our
stderr log file shows this:
Wed May 18 19:49:23 EDT 2016-107 timeout after 10006 ms (10000 ms) occured while accessing file [/var/www/html/v2.ims-login.com/WEB-INF/railo/logs/login.log] Wed May 18 19:49:23 EDT 2016-107 conflict in same thread: on /var/www/html/v2.ims-login.com/WEB-INF/railo/logs/login.log java.lang.NullPointerException at railo.commons.io.retirement.RetireOutputStreamFactory$RetireThread.run(RetireOutputStreamFactory.java:43) Wed May 18 19:49:23 EDT 2016-108 conflict in same thread: on /var/www/html/v2.ims-login.com/WEB-INF/railo/logs/login.log Wed May 18 19:49:23 EDT 2016-108 conflict in same thread: on /var/www/html/v2.ims-login.com/WEB-INF/railo/logs/login.log
I’m not sure if the timeout and conflict messages are related in any way to
the RetireOutputStreamFactory messages, but they do happen around the same
When this happens, the server is unresponsive - Will accept a connection,
but just sits there not giving any response and eventually the connection
times out, and only restarting Jetty gets it going again, to which end we
have a monitor set up to automatically restart it if the connection times
out, which is far from an ideal solution for a production system.
Based on this post
here: https://groups.google.com/forum/#!topic/railo/bzW-clxkb44 - It seems
someone else had the same issue some time ago but it was never resolved for
Is this a bug that existed in Radilo 4.2.1.008, and has it been fixed in
P.S. I am also a Java developer, so any answers related to the Railo/Lucee
source won’t be a problem for me.