You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Hodgson (JIRA)" <ji...@apache.org> on 2017/01/03 20:07:58 UTC

[jira] [Commented] (AMQ-5437) cacheTempDestinations is not caching temp destinations

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

Gary Hodgson commented on AMQ-5437:
-----------------------------------

This appears still (also?) not to work in 5.12.0. Unless my expectations are wrong.  

When I kill a consumer process the producer process still throws "javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:garyhodgson-PC-50108-1483473568352-1:1:1"

In the activemq config I have set the following attributes on the broker tag: cacheTempDestinations="true" timeBeforePurgeTempDestinations="20000"

> cacheTempDestinations is not caching temp destinations
> ------------------------------------------------------
>
>                 Key: AMQ-5437
>                 URL: https://issues.apache.org/jira/browse/AMQ-5437
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.10.0
>            Reporter: Jakub Korab
>
> When using BrokerService.cacheTempDestinations=true, according to a post on SO by gtully (http://stackoverflow.com/questions/6432672/activemq-how-to-handle-broker-failovers-while-using-temporary-queues) the broker should keep the destinations around for the time defined by BrokerService.timeBeforePurgeTempDestinations before removing them. This is not happening; there are no tests around this area.
> When I kill a temporary queue consumer process with a kill -9, I can see the temporary destination being removed immediately on the broker and an advisory message to that effect being sent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)