activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4472) consumer.close() on transacted session does not release prefetched messages
Date Wed, 24 Apr 2013 19:17:16 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640814#comment-13640814
] 

Hiram Chirino commented on AMQ-4472:
------------------------------------

So using preftech=0 is just a work-around. It should also work for any preftech value.
IMO, as long as the consumer has not acked any of the prefetched messages, it should not consider
itself as being part of the transaction.

                
> consumer.close() on transacted session does not release prefetched messages
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-4472
>                 URL: https://issues.apache.org/jira/browse/AMQ-4472
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.8.0
>            Reporter: Jason Sherman
>              Labels: transactions
>         Attachments: amq-4472.zip
>
>
> When using transactions an issue can arise where the consumer has messages in it's prefetch
and when consumer.close() is called the consumer is not closed and does not release the messages.
 
> The use case is as follows:
> 1) Create producer
> 2) Create consumer
> 3) Send message to queue
> 4) Commit session
> 5) Send a new message
> 6) Close the consumer
> 7) Start a new consumer
> 8) Try to receive the message
> Test case will be attached shortly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message