You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/10/04 11:44:40 UTC
[jira] Updated: (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
[ https://issues.apache.org/activemq/browse/CAMEL-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3193:
-------------------------------
Summary: 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 (was: After a longer connection loss to the jms server a jms endpoint does not work anymore even if the jms server comes back online)
Affects Version/s: 2.4.0
(was: 2.5.0)
> 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: 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.