I don’t know if split supports suspend/resume - I think it would have to be the underlying component (in this case the file component). Also, I believe suspend/resume is for a route or a context - not an exchange. I think the route is trying to complete the current exchange (i.e. the current file) before it goes down. You could try using .stopOnException(), but I’m not certain if that would help in this case or not.
Regardless, I don’t think you’ll be able to resume the exchange that’s inflight - it would need to start over (i.e. re-process the file). > On Aug 30, 2016, at 1:45 PM, Brad Johnson <brad.john...@mediadriver.com> > wrote: > > I suspect it's the streaming that's creating the problem but I can't be > sure without testing. If you test it by removing the streaming does the > route suspend/stop successfully? > > The reason I suggested using the ThrottlingRoutePolicy is you should be > able to set that maxInflightExchanges to 0 when you want. But I certainly > understand if you don't want to try that. > > On Tue, Aug 30, 2016 at 12:44 PM, saw <trapila...@hotmail.com> wrote: > >> Ranx thank you for your suggestions but what i was looking for was some >> insight into the original problem, not a workaround. >> >> I would really just like to know if the splitter supports suspend/resume >> and >> if i'm doing something wrong in the route configuration that are causing >> the >> exceptions. >> >> >> >> -- >> View this message in context: http://camel.465427.n5.nabble. >> com/Exception-when-suspending-splitter-tp5786964p5787007.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >>
