[jira] Commented: (CAMEL-3193) After a longer connection loss to the jms server a jms endpoint does not work anymore even if the jms server comes back online

["Claus Ibsen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62305#action_62305 ] 

Claus Ibsen commented on CAMEL-3193:
------------------------------------

Chrsitian the title of this ticket is misleading. Could you change it.

Its a problem with failover/re-connection on some brokers such as Tibco EMS which doesn't automatic failover temporary queues.
It ought to be the brokers problem to ensure this works out of the box.

What happens when the _other_ side returns back a reply on that _old_ temporary queue? You can't just create a new temporary queue on re-connection/failover.
Hence I think its more a broker problem than the camel-jms component.

> After a longer connection loss to the jms server a jms endpoint does not work anymore even if the jms server comes back online
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3193
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3193
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.5.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 2.5.0
>
>         Attachments: patch.txt
>
>
> To recreate the problem you need a route with a jms inout endpoint that is configured to use a temporary destination for replies. Till now I was only able to show the problem with tibco ems.
> - Start broker
> - Start the jms consumer that replies to the request
> - Start the route 
> - Send a request/reoply exchange (should work)
> - Stop the broker
> - Wait long enough for the client to do a full reconnect (I used connectionFactory.setReconnAttemptCount(1) on the client so I do not have to wait so long)
> - Start the broker -> The jms component will do a full new connect
> - Send a request/reoply exchange -> Now a InvalidDestination Exception happens
> The client route will not work anymore until a restart as it creates the temporary destination only once and it is invalid now.

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