JDK-6799101 : Circular logging
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2009-01-29
  • Updated: 2014-02-24
  • Resolved: 2014-02-24
Related Reports
Relates :  
Relates :  
I got a request from a CU to implement circular logging. It means that when an output file becomes X bytes large - start overwriting the head of the dump file with the new data. This may be useful when logging output of  -XX:+PrintGC -XX:+PrintGCDetails. The CU is interested in this feature on Windows but I do not see a difference.

-XX:UseGCLogFileRotation can be used to achieve similar results. Closing as WNF

PUBLIC COMMENTS My initial answer was that this can be implemented without any changes in vm. If a command line launcher was used then redirect stderr/stdout output to a program that does this type of logging. If a custom launcher is used then in Windows the app can grab console handles and do processing of output that way. On Solaris and Unix pipes should do the trick. Not sure how this can be done when java plugin is used.. However I am seeking other opinions in the runtime team and perspectives of this RFE.