You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by huntc <hu...@mac.com> on 2010/06/23 13:57:59 UTC
Re: Problem with maintaining a JMS subscription after waking from
sleep
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 afraid!
BTW: Is there a big issue with regards to upgrading Camel to Spring 3?
Kind regards,
Christopher
--
View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510888.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by huntc <hu...@mac.com>.
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 me that a few Apache projects need a strategy to move toward
Spring 3. We've got to upgrade sometime.
Given the build profile you mention, how about releasing Camel as Spring 3,
but require that slower moving projects build their own distribution based
on Spring 2?
--
View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510985.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jun 23, 2010 at 4:01 PM, Willem Jiang <wi...@gmail.com> 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.
>
> If you are using OSGi, camel also has a feature file (features-spring3.xml)
> which depends on Spring 3.x.
>
Yeah I think we will wait for Camel 3.0 to be JDK 1.6+ Spring 3.0+ as min.
> Willem
> ----------------------------------
> Apache Camel, Apache CXF committer
> Open SOA http://www.fusesource.com
> Blog http://willemjiang.blogspot.com
> Tiwtter http://twitter.com/willemjiang
>
> huntc wrote:
>>
>> 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
>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by Willem Jiang <wi...@gmail.com>.
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
(features-spring3.xml) which depends on Spring 3.x.
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open SOA http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
huntc wrote:
>
> 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
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by huntc <hu...@mac.com>.
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-after-waking-from-sleep-tp510193p510895.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by huntc <hu...@mac.com>.
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://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p511279.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Jun 24, 2010 at 11:58 PM, huntc <hu...@mac.com> 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.
>>
>> And in Camel you can register the listener using the
>> exceptionListener=#myListener configuration in the endpoint uri.
>>
>> If it fixes it we can create a listener to be shipped out of the box.
>>
>>
> Hi Claus,
>
> I can expend the effort to do this however I've now moved and tested my
> application in UAT based on Spring 3 (I had to move quickly). In addition an
> exception listener sounds like a hack. Can we not move to Spring 3 and
> provide a Spring 2 profile (swap the profile situation around?). That way
> any AMQ and SMX dependency issue is resolved as they can build their own
> distributions from source.
>
> BTW: I don't see much value in shipping Camel with AMQ nowadays; I
> appreciate the history, but they're really two very independent things. I
> can't imagine why someone would prefer to use an AMQ bundled Camel vs. the
> one generally available. Also, given SMX's relationship to OSGi and thus its
> great handling at dependencies I'm not sure I get why Camel needs to be
> strongly coupled there either.
>
> Let's not have other projects constrain what we do here.
> --
If you use maven in your project it should be just a matter of
changing the spring version in your pom.xml by adding a properties as
shown here:
<properties>
<spring-version>3.0.2.RELEASE</spring-version>
</properties>
> View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p511190.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by huntc <hu...@mac.com>.
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 the
> exceptionListener=#myListener configuration in the endpoint uri.
>
> If it fixes it we can create a listener to be shipped out of the box.
>
>
Hi Claus,
I can expend the effort to do this however I've now moved and tested my
application in UAT based on Spring 3 (I had to move quickly). In addition an
exception listener sounds like a hack. Can we not move to Spring 3 and
provide a Spring 2 profile (swap the profile situation around?). That way
any AMQ and SMX dependency issue is resolved as they can build their own
distributions from source.
BTW: I don't see much value in shipping Camel with AMQ nowadays; I
appreciate the history, but they're really two very independent things. I
can't imagine why someone would prefer to use an AMQ bundled Camel vs. the
one generally available. Also, given SMX's relationship to OSGi and thus its
great handling at dependencies I'm not sure I get why Camel needs to be
strongly coupled there either.
Let's not have other projects constrain what we do here.
--
View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p511190.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jun 23, 2010 at 1:57 PM, huntc <hu...@mac.com> 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.
>>
>
> Hi Claus,
>
> That was the entire stack trace I'm afraid!
>
> BTW: Is there a big issue with regards to upgrading Camel to Spring 3?
>
No you can replace the spring jars.
> Kind regards,
> Christopher
> --
> View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510888.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: Problem with maintaining a JMS subscription after waking from
sleep
Posted by Claus Ibsen <cl...@gmail.com>.
On Wed, Jun 23, 2010 at 1:57 PM, huntc <hu...@mac.com> 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.
>>
>
> Hi Claus,
>
> That was the entire stack trace I'm afraid!
>
> BTW: Is there a big issue with regards to upgrading Camel to Spring 3?
>
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 the
exceptionListener=#myListener configuration in the endpoint uri.
If it fixes it we can create a listener to be shipped out of the box.
> Kind regards,
> Christopher
> --
> View this message in context: http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510193p510888.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus