Leap second and Java woes
Tags java, leap second
This is kind of an old event however I thought I'd talk about it for both myself in the future and for anyone looking for an answer when it happens again. There is a bug in java or the kernel in which leap seconds cause some really nasty behavior. For instance, All app servers which include Jetty, Tomcat, and JBoss were pegged at 100% CPU usage and ridiculously high load averages. I don't know if this affects weblogic because if I recall they ship their own custom build of java which may or may not have this issue fixed. Restarting the app server does not resolve the issue however bouncing the entire server does resolve the issue (and destroys uptime). After the community put their heads together on the issue an easy fix was discovered. Simply restarting ntpd with some additional commands resolves the problem and java will chug on normally without the extra cpu load. In a nutshell here are those commands and the source where I found them.
Code:
/etc/init.d/ntpd stop date date $(date +"%m%d%H%M%C%y.%S") /etc/init.d/ntpd start
Total Comments 0
