There are a couple of items I might suggest. One is to use a ThrottlingRoutePolicy with your throttler. That can permit to write your own control so you can turn it up or down when you need to.
http://camel.apache.org/route-throttling-example.html Notice how it has a percent of maximum and resume max percent. So you can set upper and lower thresholds. But if you wanted you could either write your own or extend it and make it so you could set it. Or his another example that sort of segregates what the ThrottlingRoutePolicy does. http://camel.apache.org/routepolicy.html Notice how the policy refs can be chained together. <bean id="date" class="org.apache.camel.routepolicy.quartz.SimpleDate"/> <bean id="startPolicy" class="org.apache.camel.routepolicy.quartz.SimpleScheduledRoutePolicy"> <property name="routeStartDate" ref="date"/> <property name="routeStartRepeatCount" value="1"/> <property name="routeStartRepeatInterval" value="3000"/> </bean> <bean id="throttlePolicy" class="org.apache.camel.impl.ThrottlingInflightRoutePolicy"> <property name="maxInflightExchanges" value="10"/> </bean> <camelContext id="testRouteContext" xmlns=" http://camel.apache.org/schema/spring";> <route id="testRoute" autoStartup="false" routePolicyRef="startPolicy, throttlePolicy"> <from uri="seda:foo?concurrentConsumers=20"/> <to uri="mock:result"/> </route> </camelContext> </route> On Tue, Aug 30, 2016 at 12:10 AM, saw <trapila...@hotmail.com> wrote: > The route is suspended from another thread by calling > > > Our use case is such that we need this functionality. The file needs to be > parsed at a controlled rate and processed only at certain times. So every > once in a while parsing needs to be paused and resumed later. > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Exception-when-suspending-splitter-tp5786964p5786969.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
