[
https://issues.apache.org/jira/browse/QPID-7834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-7834:
-----------------------------
Attachment:
TEST-org.apache.qpid.client.AMQQueueDeferredOrderingTest.testMessagesSentByTwoThreadsAreDeliveredInOrder.txt
Attached logs with protocol trace logging for failed test
> [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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
