Re: FileEndpoint definition + File Language

Hi Looks like some information got lost in your mail? Anyway try with CAMEL 2.3-SNAPSHOT as we fixed some Windows File stuff in there. http://camel.apache.org/download.html Camel 2.3 is planned to be released later this month. On Wed, May 12, 2010 at 8:17 AM, Marcin Za-pa wrote: > > Using Ca

FileEndpoint definition + File Language

Using Camel 2.2 JVM 1.5 + tomcat 6.0 and Windows XP SP3 Hi, I spent much time trying to figure out why my solution doesn't work as written in documentation. I want to configure file endpoint with move parameter, but only the last case from those described below works: (Am I doing sth wrong or the

Re: routingSlip and async destinations

On Wed, May 12, 2010 at 1:21 AM, Jon Anstey wrote: > In RoutingSlipCreator maybe add a slip like > "jms:foo?exchangePattern=InOut,jms:bar?exchangePattern=InOut" instead of > just the plain endpoint URIs. > Yeah the MEP impacts how the messages gets routed in the Routing Slip EIP. You use InOnly

Re: routingSlip and async destinations

Of course, in your case use activemq:foo not jms:foo :) On Tue, May 11, 2010 at 8:51 PM, Jon Anstey wrote: > In RoutingSlipCreator maybe add a slip like > "jms:foo?exchangePattern=InOut,jms:bar?exchangePattern=InOut" instead of > just the plain endpoint URIs. > > On Tue, May 11, 2010 at 7:12 PM,

Re: routingSlip and async destinations

In RoutingSlipCreator maybe add a slip like "jms:foo?exchangePattern=InOut,jms:bar?exchangePattern=InOut" instead of just the plain endpoint URIs. On Tue, May 11, 2010 at 7:12 PM, Scott Parkerson wrote: > Camel riders, > > I've got a route that makes use of the Routing Slip EIP. Right now, a > pr

routingSlip and async destinations

Camel riders, I've got a route that makes use of the Routing Slip EIP. Right now, a processor is used to create the header to be used with the routingSlip processor. Once that is done, the routingSlip then passes the messages on to one or more ActiveMQ queues as targets. It was my understanding t

Re: Recovery From Netty Connection Drop

On Tue, May 11, 2010 at 5:20 PM, Gareth Collins wrote: > > Hello Claus, > > I tested the changes in my environment (sent a message, removed network > connectivity and sent another message, waited until the connection timed > out, restored network connectivity and sent another message). They worked

Re: Recovery From Netty Connection Drop

Hello Claus, I tested the changes in my environment (sent a message, removed network connectivity and sent another message, waited until the connection timed out, restored network connectivity and sent another message). They worked. Thanks! regards, Gareth Claus Ibsen-2 wrote: > > On Tue, May

Re: Out of Memory Crash with Seda (Camel 2.1.0)

Hi See this FAQ http://camel.apache.org/why-does-camel-use-too-many-threads-with-producertemplate.html You should create one instance of ProducerTemplate and keep it around. And you should remember to stop it after use, if you create a new instance all the time. In Camel 2.3 Camel will help shut

Out of Memory Crash with Seda (Camel 2.1.0)

Hi, I have a route which uses the SEDA endpoint. After a week or two the JVM would crash due to out of memory. When I use youkit to profile the JVM I see a bunch of mbeanserver.NamedObject created overtime related to the seda queue. Those mbeanserver.NamedObject are stored in a HashMap. Does any

Re: Recipient List with optional destinations.

Oh and the same option should be added to Routing Slip EIP as well. On Tue, May 11, 2010 at 11:06 AM, Claus Ibsen wrote: > On Tue, May 11, 2010 at 11:03 AM, Eric Bouer wrote: >> >> Hi. >> You're right about that, I added errorhandler that just suppressed the >> warrning. >> But throwing an exce

Re: Recovery From Netty Connection Drop

On Tue, May 11, 2010 at 8:35 AM, Claus Ibsen wrote: > Hi Gareth > > Thanks for your findings. I will get it committed to trunk. (Apache > SVN is not working at this moment). > Committed fixes to trunk. Gareth can you test it on your system? > > On Tue, May 11, 2010 at 4:55 AM, Gareth Collins >

Re: Recipient List with optional destinations.

On Tue, May 11, 2010 at 11:03 AM, Eric Bouer wrote: > > Hi. > You're right about that, I added errorhandler that just suppressed the > warrning. > But throwing an exception (filling all the stack trace) is a CPU intensive > task, rather than just skipping and moving on to the next recipient. > Wou

Re: Recipient List with optional destinations.

Hi. You're right about that, I added errorhandler that just suppressed the warrning. But throwing an exception (filling all the stack trace) is a CPU intensive task, rather than just skipping and moving on to the next recipient. Would it be appropriate to open a JIRA for that? Thanks. willem.ji

Re: Spring 3.0 and Camel 2.2 - Route configure() called before Spring beans injected

I'm using camel 2.2.0 and spring 3.0 without any problem here.. Not sure why you see this problem ? Could you double check that you don't have old versions of spring mixed with the new ones in your classpath ? Bye, Norman 2010/5/11 Willem Jiang : > Claus Ibsen wrote: >> >> Hi >> >> Yeah implemen