Transactions do seem to be the reason it's behaving this way. I don't have much experience with transactions at this point, so I'm a bit ignorant on the subject.
This may not be the correct place to go into detail about this, but I thought I read somewhere that the boundary of a transaction can't cross to a new JMS queue, since they're different threads. Can you explain why, on an in-only exchange to a second JMS queue, the message isn't available until the thread finishes splitting the file? I'm curious how the split exchanges are "queued" to be sent to the second JMS queue until the split is complete, and then dumped into the second JMS queue all at once. Any extra light you can shed on this subject is appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/Unexpected-behavior-with-splitter-tp5747564p5747661.html Sent from the Camel - Users mailing list archive at Nabble.com.
