On 6/21/07, samg <[EMAIL PROTECTED]> wrote:
(original thread here: http://www.nabble.com/replies-to-JMS-and-recoverability-tf3431435s12049.html ) Hello again, I made the simple change in servicemix-jms necessary to use a permanent queue rather than a temporary one for the replies of in-out message exchanges.
Which change ? It should just be a change in configuration. Else could you please create a JIRA and attach your patch ? While this fixes the problem of not being able to find a deleted
temporary queue when restarting after a crash, there is (and I should have seen this coming) another problem. The collection of pending exchanges in the multiplexing provider processor is not persistent, and so of course even though the response can be passed back through the queue, upon arriving back at the provider processor its exchange is missing. This is beginning to make me think I'm barking up the wrong tree; it seems like the only way to make this work would be to not only persist whatever is necessary to reconstruct the exchange, but also to guarantee that every component involved in the workflow does the same (not an issue in my case, but would it generalize?). There would also need to be a facility for instantiating an exchange and telling it that it is actually not a new exchange, but instead the continuation of (response to) an exchange that was lost during an outage. I'm not sure that this is a good approach. Do other people who want this kind of reliability do it all with in-only messages?
Yeah, there are several components that have a state kept in memory which it not the best way to do things. What if the exchange itself is put inside a JMS property on the message ? Maybe as an optional storage. We can also use the Store from servicemix-services instead of a Map (that would be a first step). I think the JMS property could be used but this means that the consumer has to send back the exchange with the reply (which is not a problem if the consumer is another ServiceMix). Else using a store is the best appropriate thing to do I guess. Wdyt ? Regards,
Sam -- View this message in context: http://www.nabble.com/JMS-and-recoverability-%28moved-from-User-list%29-tf3961576s12049.html#a11242457 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
