Details
-
Test
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
servicemix-quartz-2009.01
-
None
Description
The test stops the component, flushes the messages, sleeps for a second and then tests that no messages have arrived while the test was sleeping. The problem seems to be that not all the messages that were triggered before the component was stopped have sufficient time to be delivered before the message list is flushed. So, these messages arrive after the list is flushed and the test fails.
This happens mostly on slow or heavily-loaded machines (like CI build servers )