You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Kevin Earls (JIRA)" <ji...@apache.org> on 2012/06/26 21:13:44 UTC
[jira] [Created] (AMQ-3900) Thread.sleep call in
TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test
timeout
Kevin Earls created AMQ-3900:
--------------------------------
Summary: Thread.sleep call in TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test timeout
Key: AMQ-3900
URL: https://issues.apache.org/jira/browse/AMQ-3900
Project: ActiveMQ
Issue Type: Test
Environment: Ubuntu 10.04
Reporter: Kevin Earls
Priority: Minor
Attachments: TopicProducerFlowControlTest.patch
The onMessage() method of this test calls Thread.sleep(1) on every call. On Ubuntu 10.04 this actually sleeps for an average of 10 milliseconds, which causes the test to timeout.
I've added a patch which has onMessage() sleep for 100 millisecond on every 100 iterations instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3900) Thread.sleep call in
TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test
timeout
Posted by "Kevin Earls (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Earls updated AMQ-3900:
-----------------------------
Attachment: TopicProducerFlowControlTest.patch
This patch changes onMessage() so that instead of calling Thread.sleep(1) each time it is invoked, it calls Thread.sleep(100) on every 100th invocation
> Thread.sleep call in TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test timeout
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-3900
> URL: https://issues.apache.org/jira/browse/AMQ-3900
> Project: ActiveMQ
> Issue Type: Test
> Environment: Ubuntu 10.04
> Reporter: Kevin Earls
> Priority: Minor
> Attachments: TopicProducerFlowControlTest.patch
>
>
> The onMessage() method of this test calls Thread.sleep(1) on every call. On Ubuntu 10.04 this actually sleeps for an average of 10 milliseconds, which causes the test to timeout.
> I've added a patch which has onMessage() sleep for 100 millisecond on every 100 iterations instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3900) Thread.sleep call in
TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test
timeout
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3900.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Seems like a reasonable change, patch applied. Thanks.
> Thread.sleep call in TopicProducerFlowControlTest sleeps too long on Ubuntu, causing test timeout
> -------------------------------------------------------------------------------------------------
>
> Key: AMQ-3900
> URL: https://issues.apache.org/jira/browse/AMQ-3900
> Project: ActiveMQ
> Issue Type: Test
> Environment: Ubuntu 10.04
> Reporter: Kevin Earls
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
> Attachments: TopicProducerFlowControlTest.patch
>
>
> The onMessage() method of this test calls Thread.sleep(1) on every call. On Ubuntu 10.04 this actually sleeps for an average of 10 milliseconds, which causes the test to timeout.
> I've added a patch which has onMessage() sleep for 100 millisecond on every 100 iterations instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira