FYI, I tried setting transacted=false in the URI for the endpoint where the transacted consumer ends up sending subsequent messages. No change in behavior...it still waits for the consumer to return before anything actually shows up in the queue.
Any suggestions on how to force a new/separate transaction, or at least some sort of immediate queueing of subsequent sends inside a transactional consumer? --Dan Claus Ibsen-2 wrote: > > Just a quick idea. Maybe in the producer template sendBody you could > use a JMS endpoint where you set transacted=false. > -- View this message in context: http://www.nabble.com/How-to-control-transactions-when-already-in-a-transaction-tp23873683p23877666.html Sent from the Camel - Users mailing list archive at Nabble.com.
