[jira] Commented: (AMQ-2905) InvalidDestinationException when using temporaryQueues and disabling advisorySupport

["Gary Tully (JIRA)" <ji...@apache.org>]

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

Gary Tully commented on AMQ-2905:
---------------------------------

Advisories are used to accurately determine if a temp queue has been deleted, if broker advisory support is disabled then the advisory consumer will not get any updates so it should be disabled.
The attribute watchTopicAdvisories=false on a an activemq connection factory will disable the advisory consumer. Or as a broker url parameter to the connection factory. {code}?jms.watchTopicAdvisories=false{code}
Then a temp queue will be assumed to exist.

> InvalidDestinationException when using temporaryQueues and disabling advisorySupport
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-2905
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2905
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: ubuntu 10.04LTS
>            Reporter: Adriaan Wisse
>
> I recently disabled advisory messages on our broker by setting the property advisorySupport="false" on the broker element.
> Since then all our communication using temporary queues fails with the following exception:
> org.springframework.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://ID:LAPTOP-ubuntu-53836-1283944838261-0:1:1;
> re-enabling advisorySupport fixes this problem.
> Do temporary queues rely on advisory messages?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.