[
https://issues.apache.org/jira/browse/QPIDJMS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDJMS-231:
---
Summary: closing a consumer used since prior commit/rollback holds its
prefetched messages until the next commit/rollback (was: Prefetched messages
are not released on consumer close)
Updated title to reflect that the issue is more nuanced. It isn't simply that
it doesnt release prefetched messages on consumer close (which is often not
going to be required, as closing the link implicitly ends any hold the link has
on them), but that in the case you actually encountered the sessions current
transaction was still in progress with messages previously consumed using that
JMS consumer before it was closed. The client is currently handling that
scenario by not closing the link until the commit/rollback, which with
prefetching enabled creates the issue you saw should you want to consume them
using other consumers in the same transaction before calling commit/rollback.
> closing a consumer used since prior commit/rollback holds its prefetched
> messages until the next commit/rollback
>
>
> Key: QPIDJMS-231
> URL: https://issues.apache.org/jira/browse/QPIDJMS-231
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
>Affects Versions: 0.11.0
>Reporter: Alex Rudyy
>
> The messages prefetched by the consumer and not yet delivered to the
> application are not released on consumer close. As result, the new consumer
> cannot consume the messages prefetched by closed consumer.
> This issue was discovered for a transacted consumer. I did not investigate
> whether other acknowledgment modes are affected by it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
