Hi I'm quite well aware that the "base problem" regarding leap seconds is not connected to Resin, but to JVM and OS.
However I saw some strange behaviour in the aftermatch, that might be interesting to clear up. Normally we run Resin 3.1.12 without any specific configuration for <stat-service>. This means a default sample-period of 60 seconds. Because of this every 59th second this was logged: [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.000][02:14:59.000] StatService[] cpu-load=41.05 ... ~26600 lines later [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 [2012-07-01 02:14:59.999][02:14:59.999] StatService[] cpu-load=41.05 This seemed a bit much to log every 60th second. I tried to add a <stat-service> section with 10 minute sample-period, and saw that those ~26600 lines was now only logged every 10th minute. But still loads more than usual (I would expect just a single line beeing logged). Was Resin to blame for this (ie. is there a possible bug around here?) or was it the JVM and OS? Regards, Jens Dueholm Christensen Survey IT
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
