Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 14 Dec 2011 15:37:30 +0000 (UTC)
From: "Timothy Bish (Commented) (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1632805036.11232.1323877050818.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <478183360.32641.1322774200754.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQNET-357) Secondary failover causes an
 "InvalidDestinationException: Cannot publish to a deleted Destination" on
 the server side
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish commented on AMQNET-357:
-------------------------------------

One option is to turn off watching topic advisories on the client, via the watchTopicAdvisories=false uri options. 
                
> 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