What you could also try is to increase the timeout. It is currently set to 100ms. Every two out-of-order messages separated by more than 100 ms in time cannot be resequenced properly then. Try using 3000 ms, for example. Does that help? -- View this message in context: http://camel.465427.n5.nabble.com/Resequence-Stream-ConcurrentModificationException-tp524555p1044702.html Sent from the Camel - Users mailing list archive at Nabble.com.
- Re: Resequence Stream ConcurrentModificationException Willem.Jiang
- Re: Resequence Stream ConcurrentModificationException Martin Krasser
- Re: Resequence Stream ConcurrentModificationExcept... Martin Krasser
- Re: Resequence Stream ConcurrentModificationEx... Martin Krasser