[
https://issues.apache.org/jira/browse/AMQNET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Gynnild resolved AMQNET-357.
----------------------------------
Resolution: Not A Problem
> Secondary failover causes an "InvalidDestinationException: Cannot publish to
> a deleted Destination" on the server side
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-357
> URL: https://issues.apache.org/jira/browse/AMQNET-357
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
> Environment: NMS 1.5.2
> Reporter: Frank Gynnild
> Assignee: Jim Gomes
> Priority: Critical
>
> The problem can be reproduced like this (using the failover protocol):
> 1) Server is started.
> 2) Broker is restarted to simulate a failover.
> 3) Client is started and uses the request/response pattern.
> 4) Everything is fine, request is sent by client, and received by the server,
> and response is received by the client.
> 5) Client is shut down.
> 6) Simulate another failover. (The server is still up and get an interrupt
> and then resume).
> 7) Start the client again and sends a request to the server.
> 8) Server gets the request, and attempts to send a response.
> 9) The response fails to get sent with the following message:
> Apache.NMS.InvalidDestinationException: Cannot publish to a deleted
> Destination: temp-queue://ID:DEV-121-56700-634583731461528772-1:0:1 <= the
> problem
> But according to the broker log the temporary destination hasn't been deleted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
