Re: StackOverflowException for route (using cxf component) sending to soap endpoint

How did you use the camel-cxf endpoint? I didn’t see any route about it. From the stack trace I can tell CXF wants to create a new HttpClient for sending the message and then the StackOverflowException is thrown. I just did quick search about this kind of StackOverflowException, I got these[1][2

Re: Http Component Post Parameters

Hi, When you use the content-type of "application/x-www-form-urlencoded”, you are supposed to send the parameters in message body instead of using URL options. You can find more information here[1] Please put paramters into the message body by using setBody DSL  setBody("serviceType=getNextIDF

Http Component Post Parameters

Hi all, I'm having some trouble making a REST service call with POST parameters. I saw a similar post but I didn't understand the solution and I need some more direction. http://camel.465427.n5.nabble.com/Http-Component-Sending-Post-Parameters-td5740321.html#a5740409 The following is my route

How to view the crypto signed messages

Is there any way to look or log signed message through camel - crypto component. I am digitally signing message like below .to("crypto:sign://rsa?algorithm=SHA1withRSA") which uses context.getEndpoint("crypto:sign://rsa?algorithm=SHA1withRSA", DigitalSignatureEndpoint.class).setPrivateKey(priva

StackOverflowException for route (using cxf component) sending to soap endpoint

Today we got an StackoverflowException for an route that worked some month in production. The route does (pseudo code): from(file).unmarshal().gzip().unmarshal().split().tokenize("\r\n|\n|\r").unmarshal().json() .process(rtdmProcessor) .process(rtdmSetNameFactory.get(rtdmTargetEvents)).id(RTDM_EVE

Re: Camel production use

yes. do you have any specific questions about creating routes? on the deployment side, Camel can be embedded in any existing Java app, run in Tomcat, in OSGi or standalone mode... I generally use Tomcat and Spring to bootstrap the context: http://camel.apache.org/servlet-tomcat-example.html o

Re: Aggregator - Problem with accepting files for second time

Hi You have noop=true, so camel wont pickup the same files again - its in idempotent mode. You can try setting the idempotent key to include the file size as shown on http://camel.apache.org/file2 Then if the files are changed it should pickup them again. On Thu, Mar 19, 2015 at 2:01 PM, Ange

Re: Relay Message from a normal TCP end-point to Websocket endpoint in camel

-- View this message in context: http://camel.465427.n5.nabble.com/Relay-Message-from-a-normal-TCP-end-point-to-Websocket-endpoint-in-camel-tp5764278p5764445.html Sent from the Camel - Users mailing list archive at Nabble.com.

Camel production use

Hi We are currently considering camel for production use in our application Do anybody have any experience in creating few hundreds of routes for some asynchronous data collection and processing?? Appreciate if some example be shared on live deployments -- View this message in context: http://

Aggregator - Problem with accepting files for second time

Hi, i've written following route: ${file:onlyname.noext} .. For the first arriving of each file it works as expected. But if the same two files arriving again (for example xy.grib and xy.md5) the aggregation doesn't start for a long time

Getting information about the route and step while executing a step

Hello,  I have configured a camel context with tracing, and configured an endpoint (activemq topic) where it should send the trace message. The message itself is sent to the specified topic, buti see no information related to the context, route which is executing or the current step.  Is there

Camel - CDI and Servlet Context Implementation

Hi, I have implemented Camel with Servlet implementation using ServletContext. I wish to implement CDI as well (which needs CdiCamelConext). I am unable to find a way to implement both. Please suggest. My web.xml routeBuilder-routes packagescan:com.example.api.routes CamelContextLifecycle

Re: MethodInfo evaluate expression

Thanx, it should be fixed by https://issues.apache.org/jira/browse/CAMEL-8437 -- View this message in context: http://camel.465427.n5.nabble.com/MethodInfo-evaluate-expression-tp5764359p5764399.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Slow FTP

Their last release is almost 2 years old. Users of Camel cannot wait another 2 years or so before they decide to do a release. On Thu, Mar 19, 2015 at 7:55 AM, yogu13 wrote: > Hello Claus, > > Not sure if camel needs to take that up as I think its already tracked by > the Apache Commons Net team

Re: Slow FTP

perhaps advising to set buffersize in the camel documentation for ftp can help get around it for time being. Regards, -Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/Slow-FTP-tp5764223p5764406.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Slow FTP

Hello Claus, Not sure if camel needs to take that up as I think its already tracked by the Apache Commons Net team NET-550 and this change would be available as part of their 3.4 release. Upgrading to 3.4 once release should do the trick for camel