<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Bengt,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class=""><br class="">Yes, providing logging that is not interleaved with other logging is indeed one of the main reasons for moving over to the new logging framework. I agree that this should make things much easier for tools that parse the log files in the future.<br class=""></div></blockquote><div><br class=""></div>Well, I would argue for something a little stronger. </div><div><br class=""></div><div>For example we have this</div><div><br class=""></div><div><pre style="background-color: rgb(255, 255, 255); font-family: Menlo; font-size: 12pt;" class=""><span style="color:#808080;font-style:italic;" class="">10.099: [GC (Allocation Failure) 10.099: [ParNew10.100: [SoftReference, 0 refs, 0.0000141 secs]10.100: [WeakReference, 0 refs, 0.0000029 secs]10.100: [FinalReference, 0 refs, 0.0000026 secs]10.100: [PhantomReference, 0 refs, 0 refs, 0.0000033 secs]10.100: [JNI Weak Reference, 0.0000045 secs] (promotion failed): 72353K->71961K(78656K), 0.0009583 secs]10.100: [CMS10.100: [CMS-concurrent-abortable-preclean: 0.210/2.397 secs] [Times: user=15.12 sys=0.27, real=2.40 secs]</span></pre><pre style="background-color: rgb(255, 255, 255); font-family: Menlo; font-size: 12pt;" class=""><span style="font-family: Helvetica; font-size: 12px; white-space: normal;" class="">which is really an ParNew allocation failure dropping into a concurrent mode failure which closes off the abortable-preclean phase and the record contains reference processing information. All good information.</span></pre><div class=""><pre style="background-color: rgb(255, 255, 255); font-family: Menlo; font-size: 12pt;" class=""><span style="color: rgb(128, 128, 128); font-style: italic;" class="">10.099: [GC (Allocation Failure) 10.099: [ParNew (promotion failed): 72353K->71961K(78656K), 0.0009583 secs]</span></pre><pre style="background-color: rgb(255, 255, 255); font-family: Menlo; font-size: 12pt;" class=""><span style="color: rgb(128, 128, 128); font-style: italic;" class="">10.100: [CMS10.100: [CMS-concurrent-abortable-preclean: 0.210/2.397 secs] [Times: user=15.12 sys=0.27, real=2.40 secs]</span></pre><pre style="background-color: rgb(255, 255, 255);" class=""><pre style="font-family: Menlo; font-size: 12pt;" class=""><span style="color: rgb(128, 128, 128); font-style: italic;" class="">10.100: [SoftReference, 0 refs, 0.0000141 secs]10.100: [WeakReference, 0 refs, 0.0000029 secs]10.100: [FinalReference, 0 refs, 0.0000026 secs]10.100: [PhantomReference, 0 refs, 0 refs, 0.0000033 secs]10.100: [JNI Weak Reference, 0.0000045 secs]</span></pre><div style="font-family: Menlo; font-size: 12pt;" class=""><br class=""></div><div class=""><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">Without reference processing (-XX:+PrintReferenceGC I think is the flag) you’ll get this</span></font></pre><div style="font-family: Menlo; font-size: 12pt;" class=""><br class=""></div></div><div class=""><pre style="font-size: 12pt; font-family: Menlo;" class=""><span style="color: rgb(128, 128, 128); font-style: italic;" class="">10.099: [GC (Allocation Failure) 10.099: [ParNew (promotion failed)10.100: [CMS10.100: [CMS-concurrent-abortable-preclean: 0.210/2.397 secs] [Times: user=15.12 sys=0.27, real=2.40 secs]</span></pre><pre class=""><pre style="font-size: 12pt; font-family: Menlo;" class=""><span style="color: rgb(128, 128, 128); font-style: italic;" class="">: 72353K->71961K(78656K), 0.0009583 secs]</span></pre><pre class=""><pre style="font-size: 12px; font-family: Menlo;" class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">Not so bad that the concurrent phase gets closed in the same line as the ParNew but that the Reference GC shifts it over is a bit of a pain.</span></font></pre><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">I would hope that this record would look the same irregardless if the equivalent of PrintReferenceGC was turned on or not.</span></font></pre><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">I can root around for better example if you’re interested. Or, maybe there is a way I can make my DB of gc logs available.</span></font></pre><pre class=""><br class=""></pre><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">One point on date stamps. The can often get misaligned with the time stamp. So I’m inclined to pick up the first date as a reference point and then calculate dates using the time stamp from there on. It gets rid of most weird conditions that can happen when the values get misaligned and you think you’ve gone back in time when you haven’t.</span></font></pre><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class=""><br class=""></span></font></pre><pre class=""><font face="Helvetica" class=""><span style="white-space: normal;" class="">Kind regards,</span></font></pre><pre class=""><span style="white-space: normal; font-family: Helvetica;" class="">Kirk</span></pre><pre class=""><br class=""></pre></pre></pre></div></pre></div></div></div></body></html>