High-resolution hardware timer failed sanity check
Hi Andreas,
Please see High-resolution hardware timer failed sanity check?
I have looked through the agent log files and it turns out that I find this message in 3 of 5 servers.
There is one that displays this message consistently and this is also the one that have problems with transformation time. The other 2 displays this Message occationally, but does not have problems with transformation time.
Best regards,
Jarl Petter
Extracts from log-files:
Failing agent/server - Message is logged consistently:
2014-03-20 10:15:10 [00000688] info [native] High-resolution hardware timer failed sanity check - returned 28ms when it should have been between 283ms and 343ms
2014-03-20 10:15:10 [00000688] info [native] High-resolution Windows timer detected.
[...]
2014-03-20 10:15:15 [00000688] warning [native] Average transformation time for 1333 classes/modules expected to be 60ms maximum, but was 207ms
2014-03-20 10:15:15 [00000688] info [native] The expected transformation time can be set via the Agent option: transformationmaxavgwait=<ms>. Please consult the documentation for further information.
Another agent/server - Message is logged approx 1 of 4 restarts:
2014-03-20 08:50:42 [00000688] info [native] High-resolution hardware timer failed sanity check - returned 218ms when it should have been between 284ms and 344ms
2014-03-20 08:50:42 [00000688] info [native] High-resolution Windows timer failed sanity check - returned 406ms when it should have been between 283ms and 343ms
2014-03-20 08:50:42 [00000688] info [native] Java Hi-Res timer capabilities: maxvalue=9223372036854775807, skipforward=no, skipbackward=no
2014-03-20 08:50:42 [00000688] info [native] High-resolution Java timer failed sanity check - returned 406ms when it should have been between 284ms and 344ms
2014-03-20 08:50:42 [00000688] info [native] Standard timer detected.
[...]
2014-03-20 08:50:45 [00000688] info [native] Average transformation time for 1333 classes/modules was 0ms - maximum set to 60ms
Still another agent/server - Message is logged approx 1 of 4 restarts:
2014-03-06 08:27:07 [00000688] info [native] High-resolution hardware timer failed sanity check - returned 277ms when it should have been between 284ms and 344ms
2014-03-06 08:27:07 [00000688] info [native] High-resolution Windows timer detected.
[...]
2014-03-06 08:27:13 [00000688] info [native] Average transformation time for 1333 classes/modules was 5ms - maximum set to 60ms
I would open a support ticket. If you do so let them know about these two forum postings
Hi. Can you give us more details on this error message? Is this something you see in the Agent Log Files?
