Could not refresh JMS Connection for destination 'XXX_QUEUE' - retrying in 2000 ms ???

2009-09-29 Thread Allen Lau
Hi, Been getting a lot of these types of messages from the DefaultMessageListenerContainer when I try to refresh or shutdown a camel route inside of an OSGi container. I know that I can tune the recoveryInterval( in the JmsConfiguration component) to a shorter period like 1000 or lower to allevi

Re: modify message before delivering to Dead Letter Queue

2009-10-19 Thread Allen Lau
Hi Claus, I think having Camel decorate the message is a great idea. We are having the same issue where when a message goes to the DLQ. For components/endpoints we create ourselves, we usually try to add such a header, but for existing Camel components, this information would be very helpful.

Re: modify message before delivering to Dead Letter Queue

2009-10-20 Thread Allen Lau
Thanks Claus. On Tue, Oct 20, 2009 at 12:46 AM, Claus Ibsen wrote: > On Tue, Oct 20, 2009 at 6:28 AM, Claus Ibsen > wrote: > > On Mon, Oct 19, 2009 at 8:44 PM, Allen Lau wrote: > >> Hi Claus, I think having Camel decorate the message is a great idea. > We > >>

Dynamically setting initialDelay & delay parameters for File component?

2009-11-11 Thread Allen Lau
Hi, I am using the File2 component with Spring DSL. Can not seem to find a good way to externalize the options of the File2 component that take an "int" like initialDelay and delay. For example, the following will fail. Any suggestions? Thanks, Allen

Re: Dynamically setting initialDelay & delay parameters for File component?

2009-11-13 Thread Allen Lau
hem rotate those directories daily. Is there a way to accomplish what I described? Thanks, Allen On Wed, Nov 11, 2009 at 9:24 PM, Claus Ibsen wrote: > On Thu, Nov 12, 2009 at 4:18 AM, Allen Lau wrote: > > Hi, > > > > I am using the File2 component with Spring DSL. > > &

Re: Dynamically setting initialDelay & delay parameters for File component?

2009-11-13 Thread Allen Lau
Ahh okay, didn't think of that. Thanks for the help. On Fri, Nov 13, 2009 at 7:23 AM, Claus Ibsen wrote: > On Fri, Nov 13, 2009 at 4:14 PM, Allen Lau wrote: > > Thanks, that is partially what I'm looking for. > > > > If I set the properties by defining an

Re: error-handling advice with queues

2010-03-23 Thread Allen Lau
How about just setting a header when you are done processing and there is an error? Then in your route, just send any message to the error queue when the header is detected. On Tue, Mar 23, 2010 at 11:57 AM, jfaath wrote: > > I'm looking for some advice on how to deal with errors during a large

Re: error-handling advice with queues

2010-03-23 Thread Allen Lau
XML) that I want to > send to the queue. > > FYI, here is a simplified version of my route: > > > from("jetty:http://0.0.0.0:8282/process";).convertBodyTo(String.class) >.inOnly("jms:queue:data.inbound") >.unmarshal(jaxbDf) >.beanRef

Re: error-handling advice with queues

2010-03-24 Thread Allen Lau
; I'll give this a shot. Can you give me a quick example or point me to a > sample that does something similar (ex. setting a header in code, > performing > conditional logic in a route based on a header). > > -JF > > > Allen Lau-2 wrote: > > > > I coul

Re: error-handling advice with queues

2010-03-25 Thread Allen Lau
; .beanRef("dataProcessor1", "process") > .when().xpath("/readingsType2") > .unmarshal(jaxbDf) > .beanRef("dataProcessor2", "process") > .otherwise().to("mock:invalid") > > > Allen Lau-2 wrote: > > > > Look