Hi Claus,
I'm not quite sure how creating a property in my pom file influences the
version of Spring that Camel depends on... did you mean a classifier on my
Camel dependency declarations?
Sorry if I'm missing something here...
Kind regards,
Christopher
--
View this message in context:
http:/
On Thu, Jun 24, 2010 at 11:58 PM, huntc wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> I think we can fix the issue with a custom exceptionListener which
>> fixes the null message.
>>
>> Can you test it by creating a custom javax.jms.ExceptionListener class
>> and then set the message to a non null value
Claus Ibsen-2 wrote:
>
> I think we can fix the issue with a custom exceptionListener which
> fixes the null message.
>
> Can you test it by creating a custom javax.jms.ExceptionListener class
> and then set the message to a non null value.
>
> And in Camel you can register the listener using
Hi Willem,
Willem.Jiang wrote:
>
> Hi,
>
> As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
> Spring version in Camel.
> But there is spring3 profile in camel parent/pom.xml, you can build
> camel with spring 3.0.3.RELEASE with that profile if you like.
>
>
Sounds to
On Wed, Jun 23, 2010 at 1:57 PM, huntc wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> Can you post a bit more on the stacktrace? Maybe we can find a spot in
>> the camel-jms component to workaround this issue by setting an non
>> null message on the JmsException. This may help prevent this spring
>> bug.
On Wed, Jun 23, 2010 at 4:01 PM, Willem Jiang wrote:
> Hi,
>
> As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
> Spring version in Camel.
> But there is spring3 profile in camel parent/pom.xml, you can build camel
> with spring 3.0.3.RELEASE with that profile if you like.
>
Hi,
As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
Spring version in Camel.
But there is spring3 profile in camel parent/pom.xml, you can build
camel with spring 3.0.3.RELEASE with that profile if you like.
If you are using OSGi, camel also has a feature file
(feature
Claus Ibsen-2 wrote:
>
> No you can replace the spring jars.
>
Upgrading to Spring 3.0.3.RELEASE fixes the problem.
Should we move Camel to Spring 3?
Kind regards,
Christopher
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-aft
On Wed, Jun 23, 2010 at 1:57 PM, huntc wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> Can you post a bit more on the stacktrace? Maybe we can find a spot in
>> the camel-jms component to workaround this issue by setting an non
>> null message on the JmsException. This may help prevent this spring
>> bug.
Claus Ibsen-2 wrote:
>
> Can you post a bit more on the stacktrace? Maybe we can find a spot in
> the camel-jms component to workaround this issue by setting an non
> null message on the JmsException. This may help prevent this spring
> bug.
>
Hi Claus,
That was the entire stack trace I'm afr
On Wed, Jun 23, 2010 at 11:53 AM, huntc wrote:
>
> After a little more research, I think its because the version of Spring we're
> using has this bug:
>
> https://jira.springsource.org/browse/SPR-5275
>
> Any recommendations?
>
Can you post a bit more on the stacktrace? Maybe we can find a spot i
On Wed, Jun 23, 2010 at 11:47 AM, huntc wrote:
>
> I've just made a discovery on my own machine. Looks as though this issue may
> actually be related to Spring. What I did was start up a broker, start up my
> application that subscribes to a topic, shutdown the broker and:
>
>
> Exception in threa
After a little more research, I think its because the version of Spring we're
using has this bug:
https://jira.springsource.org/browse/SPR-5275
Any recommendations?
Kind regards,
Christopher
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subs
I've just made a discovery on my own machine. Looks as though this issue may
actually be related to Spring. What I did was start up a broker, start up my
application that subscribes to a topic, shutdown the broker and:
Exception in thread "DefaultMessageListenerContainer-1"
java.lang.NullPointer
Just for the record, I've updated the broker to 5.3.2 as well. I'm now using
the latest of everything.
I shall now start looking at the Camel component...
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510
OK, upgrading to AMQ 5.3.2 didn't help either.
Help!
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510536.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Willem,
Thanks for that. Just to note that upgrading to Camel 2.3.0 did not change
the outcome i.e. my application failed to re-connect to the topic upon
waking up.
I have now built and deployed a release using 5.3.2 AMQ artefacts so we'll
see if that makes any difference (I shall know in abo
Hi,
I think it should be OK to use Camel 2.3.0 with ActiveMQ 5.3.x, as we
ran the development tests of Camel with ActiveMQ 5.3.x.
Willem
huntc wrote:
I was using Camel 2.2.0 so I've now upgraded to 2.3.0 in the hope that the
problem may go away.
My other thought is to upgrade the camel-act
I was using Camel 2.2.0 so I've now upgraded to 2.3.0 in the hope that the
problem may go away.
My other thought is to upgrade the camel-activemq component. I noticed that
I'm using activemq-camel:5.2.0 as per the doco. and that this brings in
activemq-core:5.2.0 and activemq-pool:5.2.0. This is
19 matches
Mail list logo
