[
https://issues.apache.org/jira/browse/QPID-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie updated QPID-1427:
---------------------------------
Priority: Minor (was: Major)
Affects Version/s: M4
Fix Version/s: (was: M4)
Dropping to low priority and from M4 as it is a timeout issue not message loss
scenario.
We should look to change the way QTC handles timeouts, and potentially why the
messages are taking a bit too long.
Currently there is one default timeout of QpidTestCase.RECEIVE_TIMEOUT=1000;
We should have something like:
RECEIVE_TIMEOUT_EXPECTED_RECEIVE
RECEIVE_TIMEOUT_EXPECTED_TIMEOUT
> [Java] QueueBrowserDupsOKTest Failure
> -------------------------------------
>
> Key: QPID-1427
> URL: https://issues.apache.org/jira/browse/QPID-1427
> Project: Qpid
> Issue Type: Bug
> Affects Versions: M3, M4
> Reporter: Marnie McCormack
> Assignee: Martin Ritchie
> Priority: Minor
> Attachments:
> TEST-org.apache.qpid.test.client.QueueBrowserClientAckTest.testQueueBrowserMsgsRemainOnQueue.out
>
>
> Test: testQueueBrowserMsgsRemainOnQueue
> Class: org.apache.qpid.test.client.QueueBrowserDupsOkTest
>
> junit.framework.AssertionFailedError: Message 0 not retrieved from queue
> at
> org.apache.qpid.test.client.QueueBrowserAutoAckTest.validate(QueueBrowserAutoAckTest.java:334)
>
> at
> org.apache.qpid.test.client.QueueBrowserAutoAckTest.testQueueBrowserMsgsRemainOnQueue(QueueBrowserAutoAckTest.java:379)
>
> at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:186)
> at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:220)
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
