RFR (S): 8008314 - Unimplemented() Atomic::load breaks the applications

[Jesper Wilhelmsson]

Hi Vladimir,

Do I understand your question correct if I say that you want to save the log 
file from an old VM when a new VM is started instead of overwriting the old log 
file as is done today?

This was discussed when log file rotation was introduced. Possible solutions 
could be to attach the PID to the log file name, or maybe use the timestamp when 
the VM is started as a way to get a unique file name. There is an RFE for this 
(JDK-6950794). I don't think anyone is actively working on this right now.

There are also different external tools that can be used for log rotation that 
may have the functionality you are looking for. RFE JDK-7090324 is requesting 
better support for these tools, so I don't know if there are any problems with 
the current logging that makes it hard to use these tools.

Cheers,
/Jesper



On 21/2/13 5:35 PM, Vladimir Sitnikov wrote:
> Is there a chance to get "rotate gc log on startup" option?
>
> I do respect the importance of rotation policy based on file size. However, log
> rotation on startup is crucial to have gc log at all in case of failure.
>
> I often face a problem when a customer reboots the application, and does not
> backup gc log beforehand.
>
> Regards,
> Vladimir Sitnikov
>