Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <18866902.post@talk.nabble.com>
Date: Thu, 7 Aug 2008 02:26:36 -0700 (PDT)
From: seven <horia.muntean@gmail.com>
To: camel-user@activemq.apache.org
Subject: RE: DefaultMessageListenerContainer threading issue - possible
 false alert
In-Reply-To: <4C1FB9C00D24A140906239533638C4D204DBAB79@EXVS04.exserver.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <18811410.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D204DBAB58@EXVS04.exserver.dk>
 <18845718.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D204DBAB79@EXVS04.exserver.dk>


Hi,

I just found out that due to the mode I started my app in my class path wer=
e
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 and turned to direct sprin=
g
message listeners so when I have some time I will revert the configration
and let you know if the problem is still there.

Regards,
Horia


Claus Ibsen wrote:
>=20
> Hi
>=20
> I recall there was a issue like this 1-2 months ago. Try searching the
> user and dev forums.=20
>=20
> Can you try with activeMQ instead of WebSphereMQ to see if it has the sam=
e
> issue? We would like to narrow it down what is the problem.=20
>=20
>=20
> Med venlig hilsen
> =20
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsg=C3=A5rdsv=C3=A6nget 21
> 8362 H=C3=B8rning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>=20
>=20

--=20
View this message in context: http://www.nabble.com/DefaultMessageListenerC=
ontainer-threading-issue-tp18811410s22882p18866902.html
Sent from the Camel - Users mailing list archive at Nabble.com.