Advice needed - throttling jms producing

Usecase: I have a route which ends with sending to a jms queue. OutOnly - no req/res. In order to avoid producing too fast I want to throttle the production rate based on queue depth (or ratio of max queue depth). I have api's to query the queuedepth. I've been looking at http://camel.apache.or

AllowUseOriginalMessage do i need it?

I am not sure about "AllowUseOriginalMessage is enabled. If access to the original message is not needed, then its recommended to turn this option off as it may improve performance." In my route the original message is not used in error handler but i attached a RoutePolicy that implements onExchan

Re: AllowUseOriginalMessage do i need it?

No Its only if you call the getOriginalMessage method or have configured the error handler to use the original message when it moves messages to a DLQ etc. On Thu, Oct 22, 2015 at 2:19 PM, dermoritz wrote: > I am not sure about > "AllowUseOriginalMessage is enabled. If access to the original m

How to log the messages for enrich

HI , I have route with enrich to communicate with host in soap message format. but how can i log the outgoing / incoming messages of soap using spring dsl. Thanks, Kumar -- View this message in context: http://camel.465427.n5.nabble.com/How-to-log-the-messages-for-enrich-tp5772970.html Sent

Re: Rest DSL Jetty multiple handlers causes java.lang.StackOverflowError

This seems similar to https://issues.jboss.org/browse/ENTESB-2619 Also for brevity, below are the two handler beans:

Jetty server startup warnings when using handlers in Rest DSL

Hi, When I have my restConfiguration as follows: When the app is starting, I'm finding the logs are as follo

Java Standalone Application Stopped Automatically

I have a standalone Java camel application (Spring Based) running in Unix sever. Sometimes it is getting stopped automatically without anyone killing the process manually. I verified nmon report for that that period all resources (CPU, Disk IO, Ram) are well with in limits. To trace of exception

Re: Possible bug with BeanInfo.introspect in 2.15.3 version

I have created issue https://issues.apache.org/jira/browse/CAMEL-9243 with some test code to demonstrate this regression in 2.15.3. -- View this message in context: http://camel.465427.n5.nabble.com/Possible-bug-with-BeanInfo-introspect-in-2-15-3-version-tp5772875p5772977.html Sent from the Cam

Camel 2.15.3: multicast with aggregationStrategy() not working ...

I'm using Camel 2.15.3 with a route that reads from *netty4:udp* and multicasts to two SEDA queues and uses *aggregationStrategy()* to choose the correct response to send back to the client as the UDP reply. I can see the correct reply coming into the aggregate() method, but setting the *Exchange.

Camel 2.15.3: multicast (default is take the latest reply?)

>From Apache Camel Multicast Examples it states: /"The final output from the multicast is the the latest reply message and it discards any earlier replies. If you want a different aggregation strategy to include even other rep

Re: Java Standalone Application Stopped Automatically

What do your application/camel logs say ? -- View this message in context: http://camel.465427.n5.nabble.com/Java-Standalone-Application-Stopped-Automatically-tp5772974p5772982.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.15.3: multicast (default is take the latest reply?)

Maybe use wire tap instead to send the 1st seda, and a regular to for the 2nd, then you dont need multicast. On Thu, Oct 22, 2015 at 8:36 PM, SteveR wrote: > From Apache Camel Multicast Examples > it > states: /"The final ou

Re: Camel 2.15.3: multicast with aggregationStrategy() not working ...

Exchange.AGGREGATION_COMPLETE_CURRENT_GROUP is for the aggreagator eip, not muilticast. On Thu, Oct 22, 2015 at 8:15 PM, SteveR wrote: > I'm using Camel 2.15.3 with a route that reads from *netty4:udp* and > multicasts to two SEDA queues and uses *aggregationStrategy()* to choose the > correct re