Very long processing of the Consumer in the file component…

Hi, I set-up a route with the following consumer URI: from("file:///tmp/junit6150402493774267253/in?initialDelay=500")... At one point in the log I get the following information: 2015/12/16 18:11:26,278 GMT+0100 FINE [org.apache.camel.impl.DefaultScheduledPollConsumerScheduler] : Scheduling

Re: Very long processing of the Consumer in the file component…

Also, to complete, there is this log just before the poll related to the locking, it is maybe linked: 2015/12/16 18:11:26,790 GMT+0100 FINE [org.apache.camel.component.file.FileEndpoint] : Parameters for Generic file process strategy {readLockMinAge=0, readLockMarkerFile=true,

CVE-2015-5348 - Apache Camel medium disclosure vulnerability

Apache Camel's Jetty/Servlet usage is vulnerable to Java object de-serialisation vulnerability If using camel-jetty, or camel-servlet as a consumer in Camel routes, then Camel will automatic de-serialize HTTP requests that uses the content-header: application/x-java-serialized-object. Please

Re: Camel / SpringBoot integration - Invalid shutdown sequence

Hi Thanks for reporting. Do you mind logging a JIRA ticket? http://camel.apache.org/support.html On Thu, Dec 17, 2015 at 12:14 PM, lchdev wrote: > I ran into the following problem when using autoconfiguration provided by > /camel-spring-boot/ artifact. By default, there is a

Re: Camel / SpringBoot integration - Invalid shutdown sequence

Done ! CAMEL-9431 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-SpringBoot-integration-Invalid-shutdown-sequence-tp5775220p5775223.html Sent from the Camel - Users mailing list archive at Nabble.com.

RE: Camel Routes: Identify end of Processing in a Route

You can do something like this: Set the route in the header... public class RouteStopProcessor implements Processor { @Override public void process(Exchange exchange) throws Exception { String routeIdToRestart = (String)exchange.getIn().getHeader("routeIdToRestart");

Re: Camel Routes: Identify end of Processing in a Route

Camel routes are event based. So each event is separate. There is no real notion of "all records". It is a recurring request though. So maybe we are missing a camel batch processing/ETL API. Christian On 17.12.2015 15:35, ganga_camel wrote: Hi, I am new to camel. I understand that Camel

Camel Routes: Identify end of Processing in a Route

Hi, I am new to camel. I understand that Camel routes once started continue to be active and in running status unless its manually stopped. I have a requirement where the route should automatically stop after the processing of all the records are complete. Is there a way we can programitically

Re: CVE-2015-5348 - Apache Camel medium disclosure vulnerability

Was curious how easy this was to exploit, so I decided to play around a little. We deploy entirely into OSGi environments either in apache servicemix or apache karaf, so that's where my testing was focused. There is a github project which handily creates sample payloads given a command of your

camel:run Issue

Dear, While I was trying to run the command: mvn camel:run on windows environment. I am getting the below error, Please help me what is the issue with it. Caused by: org.apache.camel.InvalidPayloadException: No body available of type: org.w3c.dom.Document but has value:

Re: Split and tokenizeXML not working with Jaxb unmarshal with Part class.

Maybe try with stax it works with pojos for splitting http://camel.apache.org/stax On Fri, Dec 18, 2015 at 7:26 AM, sonu123 wrote: > Hi, > > In below codes, I am reading a big XML file and then splitting on some > CcyXchg element. Until here, codes works. When

Split and tokenizeXML not working with Jaxb unmarshal with Part class.

Hi, In below codes, I am reading a big XML file and then splitting on some CcyXchg element. Until here, codes works. When I am trying to unmarshal into Java Object, I am getting all properties of CurrencyExchange6 as null. Any idea ho w I can convert the part XML into POJO. public void

Camel / SpringBoot integration - Invalid shutdown sequence

I ran into the following problem when using autoconfiguration provided by /camel-spring-boot/ artifact. By default, there is a configuration classes that automatically registers a /TypeConverter/ bean into the Spring context: The returned bean is an instance of /DefaultTypeConverter/, which in