Hi James, The general picture is that I have a multithreaded client sending requests to A and I have multiple servers listening on B. In the middle, I have a route builder which reads from A, annotates the message with some headers and then passes them on to B. This allows the servers in B to use message selectors to retrieve only those messages that they can service efficiently (according to the headers we added). Once a server has consumed a message and computed the reply, that reply wants to go to the queue originally named in the message replyTo when it was sent to A (so the whole routing from A to B plus annotation is transparent to the replyTo mechanism).
With respect to the InOut thing - we're not using camel client libraries at either end of this. Both the client sending to A and the servers consuming on B are using AMQ libraries. I presume that means the InOut pattern you mentioned doesn't apply - or perhaps I don't understand where it lives.. I think there are probably two separate problems for me here. One is that the addition of the various headers causes difficulties (triggered the dead letter handler and also introducing an expectation of a correlationID in the reply). We changed the server end to honour the correlationID and that part started working, but we don't really want the message expiry stuff. In fact I raised another discussion on this forum a while ago to discuss how I could do my own expiry because the dead letter stuff didn't behave properly! The second issue we seem to have is that when the dead letter handler does kick in it appears to break, failing to acquire a synchronisation lock somewhere. This concerns me mainly because it might be some of my code that's holding the troublesome lock - I can't tell very easily. In a way I don't particularly mind that the handler fails, because I'm trying not to use it anyway, but I do worry that it suggests something else is wrong. -Dominic -- View this message in context: http://www.nabble.com/TimeoutException-when-using-ReplyTo--tp15043879s22882p15044864.html Sent from the Camel - Users mailing list archive at Nabble.com.
