[
https://issues.apache.org/activemq/browse/CAMEL-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62308#action_62308
]
Christian Schneider commented on CAMEL-3193:
--------------------------------------------
A fixed reply queue will work but has more adminsitrative overhead. I also
never have used fixed reply queues with more than one consumer on them but I
guess camel will handle this case.
I will try to work out a patch in any case. If we do not get it into the 2.5.0
then I can still create a small branch for EnBW that contains the fix. But I
only do these things as soon as a fix is in trunk so I am sure the next release
will contain it.
Thanks for the fast reply. Btw. What is your estimation for the 2.5.0 release
date?
> 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: 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.
