You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/04/23 13:12:47 UTC
[jira] Created: (QPID-1825) Improve TimeToLiveTest to prevent
spurious failures
Improve TimeToLiveTest to prevent spurious failures
---------------------------------------------------
Key: QPID-1825
URL: https://issues.apache.org/jira/browse/QPID-1825
Project: Qpid
Issue Type: Improvement
Components: Java Tests
Affects Versions: M4, 0.5
Reporter: Martin Ritchie
Summary:
Currently the systest TimeToLiveTest fails on the Java profile as some of the messages sent with a TTL value are expected to time out and the test does not account for the situation when they have not.
An improvement to the test would be to ensure that not all of the messages are recevied as that would signify that TTL is actually broken in the server.
A little further investigation into why some of the messages are returning would also be useful.
Currently the test sends messages with a TTL of 100ms in a transaction. After the commit (so the broker definitely has the messages) it waits 100ms then starts the consumer, yet some of the messages have not been expired by the Java broker.
--
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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1825) Improve TimeToLiveTest to prevent
spurious failures
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1825:
---------------------------------
Status: Ready To Review (was: In Progress)
> Improve TimeToLiveTest to prevent spurious failures
> ---------------------------------------------------
>
> Key: QPID-1825
> URL: https://issues.apache.org/jira/browse/QPID-1825
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M4, 0.5
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: 0.7
>
>
> Summary:
> Currently the systest TimeToLiveTest fails on the Java profile as some of the messages sent with a TTL value are expected to time out and the test does not account for the situation when they have not.
> An improvement to the test would be to ensure that not all of the messages are recevied as that would signify that TTL is actually broken in the server.
> A little further investigation into why some of the messages are returning would also be useful.
> Currently the test sends messages with a TTL of 100ms in a transaction. After the commit (so the broker definitely has the messages) it waits 100ms then starts the consumer, yet some of the messages have not been expired by the Java broker.
--
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:dev-subscribe@qpid.apache.org
[jira] Assigned: (QPID-1825) Improve TimeToLiveTest to prevent
spurious failures
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie reassigned QPID-1825:
------------------------------------
Assignee: Martin Ritchie
> Improve TimeToLiveTest to prevent spurious failures
> ---------------------------------------------------
>
> Key: QPID-1825
> URL: https://issues.apache.org/jira/browse/QPID-1825
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M4, 0.5
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: 0.7
>
>
> Summary:
> Currently the systest TimeToLiveTest fails on the Java profile as some of the messages sent with a TTL value are expected to time out and the test does not account for the situation when they have not.
> An improvement to the test would be to ensure that not all of the messages are recevied as that would signify that TTL is actually broken in the server.
> A little further investigation into why some of the messages are returning would also be useful.
> Currently the test sends messages with a TTL of 100ms in a transaction. After the commit (so the broker definitely has the messages) it waits 100ms then starts the consumer, yet some of the messages have not been expired by the Java broker.
--
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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1825) Improve TimeToLiveTest.testActive to
prevent spurious failures
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1825:
---------------------------------
Fix Version/s: 0.7
Summary: Improve TimeToLiveTest.testActive to prevent spurious failures (was: Improve TimeToLiveTest to prevent spurious failures)
> Improve TimeToLiveTest.testActive to prevent spurious failures
> --------------------------------------------------------------
>
> Key: QPID-1825
> URL: https://issues.apache.org/jira/browse/QPID-1825
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tests
> Affects Versions: M4, 0.5
> Reporter: Martin Ritchie
> Assignee: Martin Ritchie
> Fix For: 0.7
>
>
> Summary:
> Currently the systest TimeToLiveTest fails on the Java profile as some of the messages sent with a TTL value are expected to time out and the test does not account for the situation when they have not.
> An improvement to the test would be to ensure that not all of the messages are recevied as that would signify that TTL is actually broken in the server.
> A little further investigation into why some of the messages are returning would also be useful.
> Currently the test sends messages with a TTL of 100ms in a transaction. After the commit (so the broker definitely has the messages) it waits 100ms then starts the consumer, yet some of the messages have not been expired by the Java broker.
--
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:dev-subscribe@qpid.apache.org