[
https://issues.apache.org/jira/browse/AMQ-3615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448569#comment-13448569
]
Tran Minh Dung commented on AMQ-3615:
-------------------------------------
Hi Timothy Bish,
Pls help me !
My application use JMS for sending message. My client sends a request to the
server. While the server is working with my request, my client stops (network
problem) before the server finishes.
When the server is finished, it'll return to the client, but the server can't
see the client which sent the request to server, at which point, the server
will return an exception in log file.
The exception is :
javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination:
temp-queue://ID:PC0092-49463-1344231871819-0:0:9 [^]
And now I use jms.watchTopicAdvisories for fix this problem, And it's ok, I
can't see this problem in the log file.
My question is : what are you doing with exception in this case :) ?
Sorry If it's stupid question :)
Thanks,
Dung
> Advisory broker replay of destination advisories needs to distinguish temp
> destination from regular destination
> ---------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-3615
> URL: https://issues.apache.org/jira/browse/AMQ-3615
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Reporter: Gary Tully
> Assignee: Timothy Bish
> Labels: advisory, temp
> Fix For: 5.6.0
>
>
> By default an activemq connection registers an advisory consumer for temp
> destinations. This is configurable via: {{jms.watchTopicAdvisories}}. This
> allow the client to respond to a request to a deleted temp destination
> without a round trip to the broker and avoid a possible auto creation.
> At the moment, that advisory consumer gets notified of *all* destinations,
> not just temp destinations. So if there are large amounts of destinations,
> there is an unnecessary flood of advisories on the initial subscribe.
> The workaround, for clients who don't use temps is to disable this advisory
> monitor, using {{jms.watchTopicAdvisories=false}} on the connection factory
> broker url or setting the corresponding property on the connection factory or
> connection.
--
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
