qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QPID-7834) [Java Broker] [AMQP 1.0] Test AMQQueueDeferredOrderingTest#testMessagesSentByTwoThreadsAreDeliveredInOrder failed with profile java-bdb.1-0
Date Thu, 07 Sep 2017 12:43:00 GMT

     [ https://issues.apache.org/jira/browse/QPID-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Keith Wall resolved QPID-7834.
------------------------------
    Resolution: Invalid

This is a test issue.  In the failing cases I have examined, the commit of the publish of
the 151st message occurs at least two seconds after the consumer has acknowledged the 150th,
hence the timeout.  This test AMQQueueDeferredOrderingTest didn't really have any value. 
I have removed the test at 09ef11365a5fbf56886756d85810d1d1d62a94fc.

> [Java Broker] [AMQP 1.0] Test AMQQueueDeferredOrderingTest#testMessagesSentByTwoThreadsAreDeliveredInOrder
failed with profile java-bdb.1-0
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-7834
>                 URL: https://issues.apache.org/jira/browse/QPID-7834
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: qpid-java-broker-7.0.0
>            Reporter: Alex Rudyy
>             Fix For: qpid-java-broker-7.0.0
>
>         Attachments: TEST-org.apache.qpid.client.AMQQueueDeferredOrderingTest.testMessagesSentByTwoThreadsAreDeliveredInOrder.txt,
TEST-org.apache.qpid.client.AMQQueueDeferredOrderingTest.testMessagesSentByTwoThreadsAreDeliveredInOrder.txt
>
>
> Test {{AMQQueueDeferredOrderingTest.testMessagesSentByTwoThreadsAreDeliveredInOrder}}
failed when it was ran using 1-0  persistent bdb profile with qpid-jsm-client 0.23.
> The test publishes 150 messages in separate transactions, than, it starts consuming the
published messages using AUTO_ACK mode whilst publishing another 150 messages in parallel
(transacted). It appears, that second publisher failed to publish 150 messages but the client
behaved as if it published messages successfully. It looks  to me, that issues is caused by
the  client defect, but, I was not able to reproduce it locally on my machine. Further investigation
is required.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message