We had a stress test this and last week with our app on the glassfish gem v. 0.9.5 This test showed the JVM process
was killed a couple of times for apparently no reason, after degraded performance. The only thing the crashes had in
common was that the previous log file had reached it's 2000 bytes limit and no new log file was created. The old log
file was renamed to something like "prd.log_2009-08-04T15-07-59", but no new empty prd.log is being created.

This is a serious problem for our app going live with this version of the gem. Is there any chance this will be fixed
in an upcoming version of the gem?

Date: 2009-11-13 22:02
Sender: Vivek Pandey

With the current changes, the JVM crash would not happen. However
there is no rotation support. Everything is piped thru JDK
logger.

Can you try http://hudson.glassfish.org/job/glassfish-gem-build/1
25/artifact/gem/target/stage/pkg/glassfish-0.9.6.dev-universal-ja
va.gem? If it does not fix this behavior reopen the issue.