camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3193) request/reply over JMS using temporary queues - if connection lost the temporary queue is not re-created which causes the producer to not work anymore
Date Mon, 04 Oct 2010 12:40:41 GMT

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

Christian Schneider commented on CAMEL-3193:
--------------------------------------------

Hi Claus,

I have to wait till I am at home to be able to test the patch. From what I tested in the morning
I think you will also need to do "setReplyTo(null)" to let camel forget the old destination.

Thanks for the quick help

Christian


> request/reply over JMS using temporary queues - if connection lost the temporary queue
is not re-created which causes the producer to not work anymore
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3193
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-3193
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.4.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 2.5.0
>
>         Attachments: CAMEL-3193.patch, ClientTest.java, 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.


Mime
View raw message