[
https://issues.apache.org/jira/browse/QPID-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595172#action_12595172
]
Arnaud Simon commented on QPID-1004:
------------------------------------
There are two main issues with this test:
1) the consumer is created as asynchronous and cannot therefore be used for
synchronously consuming messages (this is the reason why this test is failing
actually)
2) this test does not test the current java broker TTL semantics as messages
can only expire when they are enqueued. Because messages are pre-fetched, for
testing the current implementation we need to create the consumer after having
produced the messages.
More generally we need to document how TTL is handled and think about
optionally expire pre-fetched messages.
> org.apache.qpid.test.testcases.TTLTest Fails
> --------------------------------------------
>
> Key: QPID-1004
> URL: https://issues.apache.org/jira/browse/QPID-1004
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Reporter: Senaka Fernando
>
> org.apache.qpid.test.testcases.TTLTest Fails with
> javax.jms.IllegalStateException("A listener has already been set."); in
> acquireReceiving() method of BasicMessageConsumer
> Regards,
> Senaka
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
