Hi
Ah yeah of course. If you dont define any spring bean with the id=jms
then Camel will use the default component and thats the
org.apache.camel.component.jms.JmsComponent and it's default
configuration.
So you have to override this by adding your own jms bean id, as you did.
On Mon, Dec 15, 2
I tried using org.apache.activemq.camel.component.ActiveMQComponent and that
had the same issue. I've got it fixed by configuring like this:
And referencing all my JMS endpoints as jms:queue:blahbla
Yes, sorry, ActiveMQ version 5.2.
I've created a very basic Eclipse project that demonstrates the issue.
http://www.mediafire.com/file/h2bmqyynwnt/CamelTest.zip
Simply launch in debug mode and watch the thread counter for
DefaultMessageListenerContainer tick away once per second.
Claus Ibsen-2
Hi
AMQ v 1.5.2? Are you sure it's the correct version number? The latest
release is 5.2.
Could you create a unit test sample that demonstrates this issue? It's
much easier to get started with if we have something we can run right
away.
And you are using the JmsComponent. But for ActiveMQ we encu
Sample code and config here. Very simple example that is sufficient to make
the threading issue happen.
http://rafb.net/p/G3g4wd71.html
--
View this message in context:
http://www.nabble.com/DefaultMessageListenerContainer-threading-issue-tp18811410s22882p20981731.html
Sent from the Camel - U
I'm having the same issue with DefaultMessageListenerContainer endlessly
creating threads.
Active MQ 1.5.2
Spring 2.5.6
I've tried specifying the taskExecutor and executorService, but it still
burns through threads.
: DefaultMessageListenerContainer threading issue - possible false
alert
Hi,
I just found out that due to the mode I started my app in my class path were
both camel jars ( old ones and camel-1.4.0 ) and my application loaded at
runtime the old jars.
So it's possible that camel-1.4 does not have this problem anymor
Hi,
I just found out that due to the mode I started my app in my class path were
both camel jars ( old ones and camel-1.4.0 ) and my application loaded at
runtime the old jars.
So it's possible that camel-1.4 does not have this problem anymore but
unfortunately we ditched the camel jms component
..
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-Original Message-
From: seven [mailto:[EMAIL PROTECTED]
Sent: 6. august 2008 09:27
To: camel-user@activemq.apache.org
Subject: RE: DefaultMessageListenerContainer threading issue
Hello
Hello,
Yes I do. Every second a new thread is spawned and of course the old thread
goes away.
Regards,
Horia
Claus Ibsen wrote:
>
> Hi
>
> Are you still having problems with this one?
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ..
> Silverbullet
> Skovsg
Hi
Are you still having problems with this one?
Med venlig hilsen
Claus Ibsen
..
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-Original Message-
From: seven [mailto:[EMAIL PROTECTED]
Sent: 4. august 2008
11 matches
Mail list logo
