XML DSL ignores a missing element

Hello guys the following XML DSL prints: 2003-05-24 16:06:35,496 INFO [Im Logging WHEN] 2003-05-24 16:06:35,496 INFO [Im Logging OTHERWISE] ${body.list}

Re: Camel Quartz and JobStore

JBoss 7 does not have Quartz in its modules. Is this problem related to this issue https://issues.apache.org/jira/browse/CAMEL-6067? thanx -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Quartz-and-JobStore-tp5732853p5733043.html Sent from the Camel - Users mailing li

Re: Camel Quartz and JobStore

Hi mpaiva. The jboss 7 disable feature is not directly related to your issue. It seems your jboss7 disable procedure is shutting down your CamelContext and your quartz routes as well. Can u certify yourself if the tables data disapears at CamelContext shutdown? []s -- View this message in con

Re: Headers are disapearing in RoutePolicy.onExchangeDone

Nothing! The out attribute is null. Here´s an Eclipse inspection of my exchange object: breakpoint_print.jpg exchange.hasOut() returns false. BUT... :) I was using Camel 2.10.2. In Camel 2.11.0 this problem seems to be f

Re: Headers are disapearing in RoutePolicy.onExchangeDone

Hi, Claus.. sorry for delay.. I had to abandon this project for a while. I added a step after routingSlip and the problem still remains. Yes! The destination in #2 is the same as 1#. Please, see the routes I already had tested: works1.xml

Headers are disapearing in RoutePolicy.onExchangeDone

Hi, Friends #1) consider the route below: / / when my app runs that route, my RoutePolicy bean perform onExchangeBegin and onExchangeDone methods which prints /"onExc

Re: Prolems with parametrized bean method call via simple

Hi, Claus I was using 2.9.2. The same problem happens even after updating to 2.10.3: /java.text.ParseException: Unexpected end of expression/. Thanx []s -- View this message in context: http://camel.465427.n5.nabble.com/Prolems-with-parametrized-bean-method-call-via-simple-tp5728319p5728476

Prolems with parametrized bean method call via simple

Hi friends I´m facing a strange behavior when performing this XML DSL statement. When I call /validateFiringUnitSchedule /method passing its 2 parameters, the second argument has its value splited just because it contains ",". For example, when ${in.body.cronExpression} is "0 0 10,11,12 * * ?" its

Re: Camel Quartz Bug

Thanx Christian. You are right. Set Exchange.MAXIMUM_ENDPOINT_CACHE_SIZE property before camel1.start() is the key to solve my problem. This is not a bug after all. Thanx again []s -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Quartz-Bug-tp5726285p5726392.html Sen

Re: Camel Quartz Bug

Thanks Claus. I redesigned my scheduler project to solve my problem but is a matter of time until my application start more than 1000 again. I couldn´t find nothing related to "reasonable" stateful job limit in the Quartz docs. Using plain quartz this problem does not happens. Using plain Quartz

Camel Quartz Bug

Friends, I think there´s a bug in camel-quartz component. When I start 500 camel quartz routes I have 500 triggers fired. When I start 600 camel quartz routes I have 600 triggers fired. When I start 700 camel quartz routes I have 700 triggers fired. When I start 800 camel quartz routes I have 800

Re: Camel QuartzComponent failed on recreating endpoint

It´s a nice approach. I solved my problem setting camel quartz endpoint as stateful. But this comes at a high cost. With around 1500 jobs I lost 18MB in heap memory because my Exchanges have around 25kb. Trying to solve the memory issue, I changed the RamJobStore to JdbcJobStore but Quartz also

Re: Camel QuartzComponent failed on recreating endpoint

Hello change the release solve the problem? I´m facing the same problem in production environment when I start more than 500 quartz endpoints. The failure occurs at fire time. I cannot reproduce this error in dev environment. The error just not happens. My Camel version is 2.10.1. -- View th

Re: Howto use delay message brokerage in a Camel Route using AMQ_SCHEDULED_DELAY

I found the problem. Is something between Eclipse and Maven Plugin (M2Eclipse). When I ran /mvn clean install -e/ my test cases were executed by Maven lifecycle. My testCases has a Thread.sleep(1) at the last line. Sometimes, I did not wait these 10 seconds and I killed Maven process through

Re: Howto use delay message brokerage in a Camel Route using AMQ_SCHEDULED_DELAY

Hello I´m producing my scheduled messages but when AMQ push the message to consumer I´m receiving this error: (...) [ ActiveMQ Task-1] FailoverTransport INFO Successfully connected to tcp://localhost:61616 [ main] SpringCamelContext

Using correlationid to isolate jms queues in multiple camelContexts

Dear friends I´m facing the folowing problem: I have 2 producers systems sending messages to 1 jms queue that is consumed by 2 consumers systems. Ignore the VM where they are. #a) a producerSystem_1.war has the folowing camelContext: ... ... #b) a producerSystem_2.war has

RE: RoutePolicy + Split

Hi Graham Thanx a lot for your replies. I´ll try another approach to do what I want. The localSmsDeliveryEntry is an activemq endpoint. I thought that splited Exchanges could fire onExchangeDone because they heir its parent Exchange headers, including correlationID, and localSmsDeliveryEntry is

RoutePolicy + Split

Hy guys I wrote the route below to perform this behavior: 1) call onExchangeBegin once 2) call onExchangeDone /body.envelopeList.size()/ times ${body.envelopeList} But the current behavior is: 1) call

Re: Too slow JMS pipeline when disableReplyTo=false

/Have you seen the section on the Camel JMS doc page about request/reply over JMS? / Yes. /I assume you mean request/reply over JMS, where the caller waits for the reply? / Exactly. /If you do request/reply over a JMS queue, you need a consumer on the processingQueue to pickup the incoming messag

Too slow JMS pipeline when disableReplyTo=false

I need to send messages to a JMS queue (jboss-messaging) and consume it in a sync way. I´ve tried this this first approach: This approach provides me 2 advantages and 1 (adn awful) disadva

Re: split strategyRef rejects GroupedExchangeAggregationStrategy, UseLatestAggregationStrategy, UseOriginalAggregationStrategy

Ok Claus. Thanks -- View this message in context: http://camel.465427.n5.nabble.com/split-strategyRef-rejects-GroupedExchangeAggregationStrategy-UseLatestAggregationStrategy-UseOriginay-tp5634122p5635946.html Sent from the Camel - Users mailing list archive at Nabble.com.

split strategyRef rejects GroupedExchangeAggregationStrategy, UseLatestAggregationStrategy, UseOriginalAggregationStrategy

/... Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.apache.camel.processor.aggregate.UseOriginalAggregationStrategy]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.apache.camel.processor.aggregate.UseOr

Re: Apparent Duplicated Log (Log4J)

Thanx, Claus I am using JBoss 5.1.0 and did this: - remove /slf4j-jboss-logging.jar/ and /slf4j-api.jar/ from *JBOSS_HOME\common\lib*; - download /slf4j-api-1.6.4.jar/ from http://mvnrepository.com/artifact/org.slf4j/slf4j-api/1.6.4 and place it in *JBOSS_HOME\common\lib*; - in my pom.xml I change

Re: Apparent Duplicated Log (Log4J)

I noticed that an error occurs during jboss startup. A conflict between SL4J (embedded in jboss) and SL4J required by Camel is printed: /2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: Class path contains multiple SLF4J bindings. 2012-04-10 10:05:06,424 ERROR [STDERR] (main) SLF4J: Found bin

Apparent Duplicated Log (Log4J)

Hello.. #1) In a JEE enviroment, why my logging lines are printing like this: /10:36:02,584 INFO [STDOUT] 10:36:02,583 INFO [MyClass] Whatever logging!/ #2) When it should been like this: /10:36:02,583 INFO [MyClass] Whatever logging!/ My application is deployed in JBossAS 5.1 using Apache Lo

Re: Throttling: maximumRequestsPerPeriod problem

Yes. It would be nice. I just have to find a free time =/ thank you too much -- View this message in context: http://camel.465427.n5.nabble.com/Throttling-maximumRequestsPerPeriod-problem-tp5586898p5628534.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Throttling: maximumRequestsPerPeriod problem

One more! There´s no need to separate the routes due to a throttle nested in a split. So my first spring xml works. Thanx too much regards -- View this message in context: http://camel.465427.n5.nabble.com/Throttling-maximumRequestsPerPeriod-problem-tp5586898p5599379.html Sent from the Camel -

Re: Throttling: maximumRequestsPerPeriod problem

I found the problem. It was caused by /garryHeader /header. It was null. In fact, I was sending my body using ProducerTemplate.sendBody(Endpoint endpoint, Object body). So /garryHeader /does not exist. I had to debug org.apache.camel.processor.Throttler to discover that [1]. I don´t think the

Re: Throttling: maximumRequestsPerPeriod problem

i´ll change the route instead, so I can use the *ref* property. that´s my xml updated: http://camel.465427.n5.nabble.com/file/n5596345/throttler-test-context.xml throttler-test-context.xml (I´m still setting up the tests) regards -- View this message in context: http://camel.465427.n5.nabble.

Re: Throttling: maximumRequestsPerPeriod problem

These namespaces are already declared. The browser you´re using probably hides the namespace declarations. If you right click my attached xml and choose "Show Source Code" (or something like, depending on your browser) the namespace will be shown. I´ll checkout your test and post the results. tha

Re: Throttling: maximumRequestsPerPeriod problem

Still throwing *Caused by: java.lang.IllegalStateException: The maximumRequestsPerPeriod must be a positive number, was: 0*. Are the namespaces in spring xml correct? Thanks again regards -- View this message in context: http://camel.465427.n5.nabble.com/Throttling-maximumRequestsPerPeriod-pro

Re: Throttling: maximumRequestsPerPeriod problem

thanx Christian this is my spring xml: http://camel.465427.n5.nabble.com/file/n5589498/throttler-test-context.xml throttler-test-context.xml About your tests, I couldn´t execute it because the some imports in your source code make reference to older camel version. An example, the org.apache.cam

Re: Throttling: maximumRequestsPerPeriod problem

Yes! I´ve tried: * 20 * and * garryHeader * both are displaying: /Caused by: java.lang.IllegalStateException: The maximumRequestsPerPeriod must be a positive number, was: 0/ -- View this message in context: http://camel.465427.n5.nabble.com/Throttl

Throttling: maximumRequestsPerPeriod problem

Hi! I´m trying to use Throttle in my xml CamelContext under 2.9 Camel version, but when I set the /maximumRequestsPerPeriod/ property my compilation fails displaying this message: *cvc-complex-type.3.2.2: Attribute 'maximumRequestsPerPeriod' is not allowed to appear in element 'camel:thr

Re: Choice always return turn in first test [SOLVED]

Yeah.. it works.. thank you so much.. but I tryed to access the map with [key] and did not work.. so, I think it worked fine but I didn´t pay attention... sorry spend your time.. at least, now I know that I can use the quotes in 2.9 ;) thanks -- View this message in context: http://camel.4654

Re: Choice always return turn in first test

I already tried that =( -- View this message in context: http://camel.465427.n5.nabble.com/Choice-always-return-true-in-first-test-tp4717029p4719253.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Choice always return turn in first test

In my code, setters n getterns are ommited... I already have getProperty method =/ i havn´t tried this: ${in.body.property.get[key]} can it works?? -- View this message in context: http://camel.465427.n5.nabble.com/Choice-always-return-true-in-first-test-tp4717029p4719256.html Sent from the

Choice always return turn in first test

uot;;} }* My xml is: ${in.body.property['