Finally while trying to reproduce the defect in testcase , I was able to nail
down the problem, it would have been a easier fix if were not using new
technologies, and old time classic code reviews would have helped
Lets say we have route using Spring Route Builder
from("timer://foo?fixedRate=tr
On 02/04/2011 07:38 PM, Christian Müller wrote:
Opened a ticket for it: https://issues.apache.org/jira/browse/CAMEL-3624
Add yourself as a watcher to track the progress...
Thank you all for quick help!
Can you reproduce this consistently?
Hadrian
On Feb 4, 2011, at 7:15 PM, s2010in wrote:
>
> Still not sure where the bug is, Used Camel timer, then Quartz timer, and
> finally created a separate TimerTask with java.util.Timer
>
> All of them do same, to get around have created my own daemon th
Still not sure where the bug is, Used Camel timer, then Quartz timer, and
finally created a separate TimerTask with java.util.Timer
All of them do same, to get around have created my own daemon thread now
which is working as I need to fire event after a fixed period.
Please let me know if anyone
Hi Claus,
Thanks for the link. I think I am using similar approach. My first route
"calcQueue" takes incoming message and puts it on a user specific queue
(e.g. activemq:queue:Order.User1, activemq:queue:Order.User2)
>
>
>
>
>
>
"OrderProcessor" bean in second route "ProcessOrder
See my comment on the issue.
On Fri, Feb 4, 2011 at 19:46, Guillaume Nodet wrote:
> I'll work on that, but I think that's actually a tricky issue. More
> on that later...
>
> On Friday, February 4, 2011, Bengt Rodehav wrote:
>> That looks a bit discouraging :-(
>>
>> Has this issues stopped com
I'll work on that, but I think that's actually a tricky issue. More
on that later...
On Friday, February 4, 2011, Bengt Rodehav wrote:
> That looks a bit discouraging :-(
>
> Has this issues stopped completely then or is any progress being mad?
>
> /Bengt
>
>
>
> 2011/2/4 ben.oday
>
>>
>> I was
Thanks, that seems to help!
I did actually read the docs while investigating the issue but it wasn't too
clear:
http://camel.apache.org/jms.html
disableReplyTo falseIf true, a producer will behave like a InOnly exchange
with the exception that JMSReplyTo header is sent out and not be suppre
Opened a ticket for it: https://issues.apache.org/jira/browse/CAMEL-3624
Add yourself as a watcher to track the progress...
That looks a bit discouraging :-(
Has this issues stopped completely then or is any progress being mad?
/Bengt
2011/2/4 ben.oday
>
> I was working on adding this features, but have been unable to get it
> deployed properly (https://issues.apache.org/jira/browse/CAMEL-3519). If
> anyone has
I was working on adding this features, but have been unable to get it
deployed properly (https://issues.apache.org/jira/browse/CAMEL-3519). If
anyone has the steps to get this to work, let me know...
-
Ben O'Day
IT Consultant -http://benoday.blogspot.com
--
View this message in context:
h
Correct
from 8:19 to 8:36 - Quartz is firing and timer seems working from tracer
logs, it stops after 8:36 which it is not sure why, similar thing happens
when timer is used
from 8:19 to 8:26 - Bean method is called from camel route, after which even
if timer is fired no bean method is called, t
Our system is built on top of the recipientList component and camel
components URI parameters, we are using FTP, JMS, email and HTTP
therefore we'd need a way to 'cleanup' the list of allocated endpoints,
can't you provide a way of forcing endpoints list cleanup or perhaps
customizing the maximum
Dont know what's causing this.
Generally the timer component would stop firing if it exist the run
method. Which it would only do if a java.lang.Error was thrown (not
caught).
Quartz ought to be resilient and fire according to the schedule.
So I think it fires but there is some issue in your bea
On Fri, Feb 4, 2011 at 4:00 PM, Marco Crivellaro
wrote:
>
> Hi All,
> I am working together with Sri in a project which makes an extensive use of
> camel (you've seen some posts from me in the past).
> I can confirm the number of endpoints being created grows constantly using
> any protocol,
> wit
Hi All,
I am working together with Sri in a project which makes an extensive use of
camel (you've seen some posts from me in the past).
I can confirm the number of endpoints being created grows constantly using
any protocol,
with our system we are serving a very high number of endpoints and at the
Hi
See
http://camel.465427.n5.nabble.com/Message-blocks-route-until-all-redelivery-attempts-are-exhausted-tp472319p472319.html
On Fri, Feb 4, 2011 at 3:37 PM, rxm0203 wrote:
>
> Hi Claus,
>
> I upgraded to Camel 2.4 but I see still see blocking behavior. Here are the
> contents of my camel-cont
On Fri, Feb 4, 2011 at 3:36 PM, waterback wrote:
>
> Hi Claus,
>
> i know this is a rather old post, but i have a question referring to your
> response:
>
> Does this mean, that if you have - lets say - 10 transacted routes, which
> all use the same RedeliveryHandler
> that if even if you don't ha
I tried using exception handling now, there is no exception thrown for a
reference also displaying a log snippet
onException(Throwable.class)
.useOriginalMessage()
.handled(true)
...
>From logs you can see after 8:26 onwards The bean ref method of test service
is
Hi Claus,
I upgraded to Camel 2.4 but I see still see blocking behavior. Here are the
contents of my camel-context.xml.
http://camel.apache.org/schema/spring";>
With above configuration if activemq:queue:Order.User1
Hi Claus,
i know this is a rather old post, but i have a question referring to your
response:
Does this mean, that if you have - lets say - 10 transacted routes, which
all use the same RedeliveryHandler
that if even if you don't have an exception that triggers a redelivery,
those 10 routes won't
I will have a look on it later today...
Am 04.02.2011 07:07 schrieb "Claus Ibsen" :
On Fri, Feb 4, 2011 at 2:36 AM, Alex MadMind wrote:
> Hello!
>
> I use came...
Could you take a look in the camel-smpp source code. Its most likely a
matter of adding the unbind logic in the doStop method of the
Hi Claus,
It works fine !
Thanks,
Xavier
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-route-with-method-Unit-Testing-tp3370644p3370740.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Do you see any exceptions in the log as the TimerConsumer does a try
.. catch and logs the exception.
} catch (Exception e) {
getExceptionHandler().handleException("Error processing
exchange", exchange, exchange.getException());
}
My only thought could be that some
On Fri, Feb 4, 2011 at 10:01 AM, Claus Ibsen wrote:
> Hi
>
> Using a registry.
>
> Map map = new HashMap();
> map.put("beanId", beanInstance);
>
Ah was a bit to quick, you need to use SimpleRegistry instead of the
Map. But it extends HashMap.
> this.context = new DefaultCamelContext(map);
>
>
Hi
Using a registry.
Map map = new HashMap();
map.put("beanId", beanInstance);
this.context = new DefaultCamelContext(map);
See details about registry in chapter 4 in the Camel book.
Or google the website.
There is also a ton of unit tests in camel-core you can take a look
at, eg for the bean
Hello,
I am currently trying to write a unit test for a camel route which contains
a .method("beanId","methodName") component:
from(this.incomingSource)
.split().method("splitterBean", "splitMessages")
.choice()
.when(isValid)
.marshal(jaxb).to(this.outgoingDestination)
27 matches
Mail list logo
