[
https://issues.apache.org/jira/browse/QPID-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Huston resolved QPID-2150.
--------------------------------
Resolution: Fixed
Assignee: Steve Huston
Thanks very much for the quick feedback, Andrew. Changed the threshold to 50
msec, left log level alone. Fixed in trunk r826093.
> Excessive warnings about Timer woken up late on Windows
> -------------------------------------------------------
>
> Key: QPID-2150
> URL: https://issues.apache.org/jira/browse/QPID-2150
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.6
> Environment: Windows
> Reporter: Steve Huston
> Assignee: Steve Huston
> Fix For: 0.6
>
>
> The C++ broker when running on Windows, shows a lot of warning messages like:
> 2009-10-15 21:48:37 warning Timer woken up 15ms late
> The lateness is usually between 10 and 15 msec, owing to the relative
> imprecision in waking up a thread on Windows. I have two suggestions for
> resolving this:
> 1. Change the message from warning to debug. I'm a bit concerned that,
> regardless of platform, if users of a product where speed is an issue start
> seeing messages about timers waking up late, they may be concerned, without
> any cause probably. I'm thinking that the only people interested in this
> message are those diagnosing things who may want to enable debug messages.
> 2. Allow a platform-specific value for the threshold at which lateness
> prompts a message. For example, the current 10 msec limit is tighter than is
> useful for Windows - 30msec would be better.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
