Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2015-11-25 Thread Mullally, Mark
Immense gratitude for this post as I am now not obligated to work
Thanksgiving Day to resolve the issue ... years later I am witnessing
exactly the same behavior as you described and the remedy of removing the
update-strategy="reload" attribute also resolved the issue.

The only insight I can contribute at the moment is that the undesirable
behavior is only exhibited when more than one bundle accesses a particular
property persistence id; if a property persistence id is unique per bundle,
all is copacetic.

This seemingly innocent defect causes catastrophic failure without even so
much as a single log statement as to why every Camel Context in every
bundle is being bounced over and over again.


   -

   Version 3.0.4
   
   of Apache Karaf 
   -

   Version 5.11.1 
   of ActiveMQ 
   -

   Version 2.15.2  of Camel
   
   -

   Version 3.0.4  of CXF
   


-- 
Mark P. Mullally
Cherokee Nation Technologies, LLC (CNT)
Contractor to DOI, U.S. Fish & Wildlife Service
ECOS applications for USFWS
2150 Centre Ave., Bldg C
Fort Collins, CO 80526


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-06-12 Thread Martin Stiborský
Hello, it's deployed to Karaf 2.3.1

On Wed, Jun 12, 2013 at 4:35 AM, Willem Jiang  wrote:
> which version of Karaf are you using? It looks like a Karaf issue.
> I don't think camel's change will cause this issue.
>
> 发自我的 iPhone
>
> 在 2013-6-12,上午1:51,Martin Stiborský  写道:
>
>> It's been a while but now I had some time to investigate this problem again.
>> I think I have found the problem.
>> It's caused by property-placeholder in blueprint, to be specific -
>> it's restarting over and over when there is configured
>> update-strategy="reload".
>>
>> Without this option, it works. I tried also camel 2.11.1-SNAPSHOT but
>> it seems that the problem is there as well.
>>
>> So far I don't know more, just that without this option I haven't
>> noticed any problem.
>>
>> On Thu, May 23, 2013 at 3:25 PM, Martin Stiborský
>>  wrote:
>>> Hi!
>>> We are using "features" for deployment
>>> (https://cwiki.apache.org/KARAF/46-provisioning.html).
>>>
>>> I did a quick test with Camel 2.11 and Karaf 2.3.1, completely fresh
>>> installation and this I have there some dependencies troubles, like
>>> missing "osgi.wiring.package=org.apache.aries.util" and few others.
>>> This seems to be like problem on our side. I'll know more soon hopefully.
>>>
>>> On Thu, May 23, 2013 at 2:12 PM, Raul Kripalani  wrote:
 It could be an issue with the way you deploy your bundles.

 If you drop them in the deploy/ directory, and you happen to deploy
 libraries that fulfill optional imports elsewhere, the OSGi framework could
 force a refresh of the entire bundle set. Hence justifying the observed
 behaviour to some extent.

 How exactly do you deploy your bundles?

 *Raúl Kripalani*
 Enterprise Architect, Open Source Integration specialist, Program
 Manager | Apache
 Camel Committer
 http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
 http://blog.raulkr.net | twitter: @raulvk

 On Thu, May 23, 2013 at 1:04 PM, Martin Stiborský <
 martin.stibor...@gmail.com> wrote:

> Not yet - I hasn't spent too much time on this and we postponed Camel
> 2.11 upgrade right now.
> I'll check debug log of camel and try to find the problem there.
>
> It seems I'm not alone on this :)
>
> http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html
>
> On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
>> Hi
>>
>> Did you figure out this problem?
>>
>> On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
>>  wrote:
>>> Hi guys,
>>> I'm trying to upgrade Camel and Karaf in our project to newer version,
>>> as the Camel 2.11 is out.
>>>
>>> Camel 2.10.1 -> 2.11
>>> Karaf 2.2.10 -> 2.3.1
>>>
>>> There were needed few modifications. nothing serious, but Camel and
>>> Karaf behaves a little bit weird - CamelContent is created and
>>> immediatelly shut down and then created down and again and again…
>>> I can't see anything wrong in log output. Sometimes it even start ok,
>>> sometimes it needs few tries to start correctly, but it's weird.
>>> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
>>> similar, so I know it's hard to find possible problem from such
>>> description I provided here.
>>>
>>> Just if you spot something obvious or I missed something related to
> upgrade..
>>>
>>> --
>>> S pozdravem / Best regards
>>> Martin Stiborský
>>>
>>> Jabber: st...@njs.netlab.cz
>>> Twitter: http://www.twitter.com/stibi
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> Email: cib...@redhat.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> S pozdravem / Best regards
> Martin Stiborský
>
> Jabber: st...@njs.netlab.cz
> Twitter: http://www.twitter.com/stibi
>>>
>>>
>>>
>>> --
>>> S pozdravem / Best regards
>>> Martin Stiborský
>>>
>>> Jabber: st...@njs.netlab.cz
>>> Twitter: http://www.twitter.com/stibi
>>
>>
>>
>> --
>> S pozdravem / Best regards
>> Martin Stiborský
>>
>> Jabber: st...@njs.netlab.cz
>> Twitter: http://www.twitter.com/stibi



-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-06-11 Thread Willem Jiang
which version of Karaf are you using? It looks like a Karaf issue.
I don't think camel's change will cause this issue.

发自我的 iPhone

在 2013-6-12,上午1:51,Martin Stiborský  写道:

> It's been a while but now I had some time to investigate this problem again.
> I think I have found the problem.
> It's caused by property-placeholder in blueprint, to be specific -
> it's restarting over and over when there is configured
> update-strategy="reload".
> 
> Without this option, it works. I tried also camel 2.11.1-SNAPSHOT but
> it seems that the problem is there as well.
> 
> So far I don't know more, just that without this option I haven't
> noticed any problem.
> 
> On Thu, May 23, 2013 at 3:25 PM, Martin Stiborský
>  wrote:
>> Hi!
>> We are using "features" for deployment
>> (https://cwiki.apache.org/KARAF/46-provisioning.html).
>> 
>> I did a quick test with Camel 2.11 and Karaf 2.3.1, completely fresh
>> installation and this I have there some dependencies troubles, like
>> missing "osgi.wiring.package=org.apache.aries.util" and few others.
>> This seems to be like problem on our side. I'll know more soon hopefully.
>> 
>> On Thu, May 23, 2013 at 2:12 PM, Raul Kripalani  wrote:
>>> It could be an issue with the way you deploy your bundles.
>>> 
>>> If you drop them in the deploy/ directory, and you happen to deploy
>>> libraries that fulfill optional imports elsewhere, the OSGi framework could
>>> force a refresh of the entire bundle set. Hence justifying the observed
>>> behaviour to some extent.
>>> 
>>> How exactly do you deploy your bundles?
>>> 
>>> *Raúl Kripalani*
>>> Enterprise Architect, Open Source Integration specialist, Program
>>> Manager | Apache
>>> Camel Committer
>>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>>> http://blog.raulkr.net | twitter: @raulvk
>>> 
>>> On Thu, May 23, 2013 at 1:04 PM, Martin Stiborský <
>>> martin.stibor...@gmail.com> wrote:
>>> 
 Not yet - I hasn't spent too much time on this and we postponed Camel
 2.11 upgrade right now.
 I'll check debug log of camel and try to find the problem there.
 
 It seems I'm not alone on this :)
 
 http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html
 
 On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
> Hi
> 
> Did you figure out this problem?
> 
> On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
>  wrote:
>> Hi guys,
>> I'm trying to upgrade Camel and Karaf in our project to newer version,
>> as the Camel 2.11 is out.
>> 
>> Camel 2.10.1 -> 2.11
>> Karaf 2.2.10 -> 2.3.1
>> 
>> There were needed few modifications. nothing serious, but Camel and
>> Karaf behaves a little bit weird - CamelContent is created and
>> immediatelly shut down and then created down and again and again…
>> I can't see anything wrong in log output. Sometimes it even start ok,
>> sometimes it needs few tries to start correctly, but it's weird.
>> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
>> similar, so I know it's hard to find possible problem from such
>> description I provided here.
>> 
>> Just if you spot something obvious or I missed something related to
 upgrade..
>> 
>> --
>> S pozdravem / Best regards
>> Martin Stiborský
>> 
>> Jabber: st...@njs.netlab.cz
>> Twitter: http://www.twitter.com/stibi
> 
> 
> 
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cib...@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
 
 
 
 --
 S pozdravem / Best regards
 Martin Stiborský
 
 Jabber: st...@njs.netlab.cz
 Twitter: http://www.twitter.com/stibi
>> 
>> 
>> 
>> --
>> S pozdravem / Best regards
>> Martin Stiborský
>> 
>> Jabber: st...@njs.netlab.cz
>> Twitter: http://www.twitter.com/stibi
> 
> 
> 
> -- 
> S pozdravem / Best regards
> Martin Stiborský
> 
> Jabber: st...@njs.netlab.cz
> Twitter: http://www.twitter.com/stibi


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-06-11 Thread Martin Stiborský
It's been a while but now I had some time to investigate this problem again.
I think I have found the problem.
It's caused by property-placeholder in blueprint, to be specific -
it's restarting over and over when there is configured
update-strategy="reload".

Without this option, it works. I tried also camel 2.11.1-SNAPSHOT but
it seems that the problem is there as well.

So far I don't know more, just that without this option I haven't
noticed any problem.

On Thu, May 23, 2013 at 3:25 PM, Martin Stiborský
 wrote:
> Hi!
> We are using "features" for deployment
> (https://cwiki.apache.org/KARAF/46-provisioning.html).
>
> I did a quick test with Camel 2.11 and Karaf 2.3.1, completely fresh
> installation and this I have there some dependencies troubles, like
> missing "osgi.wiring.package=org.apache.aries.util" and few others.
> This seems to be like problem on our side. I'll know more soon hopefully.
>
> On Thu, May 23, 2013 at 2:12 PM, Raul Kripalani  wrote:
>> It could be an issue with the way you deploy your bundles.
>>
>> If you drop them in the deploy/ directory, and you happen to deploy
>> libraries that fulfill optional imports elsewhere, the OSGi framework could
>> force a refresh of the entire bundle set. Hence justifying the observed
>> behaviour to some extent.
>>
>> How exactly do you deploy your bundles?
>>
>> *Raúl Kripalani*
>> Enterprise Architect, Open Source Integration specialist, Program
>> Manager | Apache
>> Camel Committer
>> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
>> http://blog.raulkr.net | twitter: @raulvk
>>
>> On Thu, May 23, 2013 at 1:04 PM, Martin Stiborský <
>> martin.stibor...@gmail.com> wrote:
>>
>>> Not yet - I hasn't spent too much time on this and we postponed Camel
>>> 2.11 upgrade right now.
>>> I'll check debug log of camel and try to find the problem there.
>>>
>>> It seems I'm not alone on this :)
>>>
>>> http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html
>>>
>>> On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
>>> > Hi
>>> >
>>> > Did you figure out this problem?
>>> >
>>> > On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
>>> >  wrote:
>>> >> Hi guys,
>>> >> I'm trying to upgrade Camel and Karaf in our project to newer version,
>>> >> as the Camel 2.11 is out.
>>> >>
>>> >> Camel 2.10.1 -> 2.11
>>> >> Karaf 2.2.10 -> 2.3.1
>>> >>
>>> >> There were needed few modifications. nothing serious, but Camel and
>>> >> Karaf behaves a little bit weird - CamelContent is created and
>>> >> immediatelly shut down and then created down and again and again…
>>> >> I can't see anything wrong in log output. Sometimes it even start ok,
>>> >> sometimes it needs few tries to start correctly, but it's weird.
>>> >> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
>>> >> similar, so I know it's hard to find possible problem from such
>>> >> description I provided here.
>>> >>
>>> >> Just if you spot something obvious or I missed something related to
>>> upgrade..
>>> >>
>>> >> --
>>> >> S pozdravem / Best regards
>>> >> Martin Stiborský
>>> >>
>>> >> Jabber: st...@njs.netlab.cz
>>> >> Twitter: http://www.twitter.com/stibi
>>> >
>>> >
>>> >
>>> > --
>>> > Claus Ibsen
>>> > -
>>> > Red Hat, Inc.
>>> > FuseSource is now part of Red Hat
>>> > Email: cib...@redhat.com
>>> > Web: http://fusesource.com
>>> > Twitter: davsclaus
>>> > Blog: http://davsclaus.com
>>> > Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>>
>>>
>>> --
>>> S pozdravem / Best regards
>>> Martin Stiborský
>>>
>>> Jabber: st...@njs.netlab.cz
>>> Twitter: http://www.twitter.com/stibi
>>>
>
>
>
> --
> S pozdravem / Best regards
> Martin Stiborský
>
> Jabber: st...@njs.netlab.cz
> Twitter: http://www.twitter.com/stibi



-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-05-23 Thread Martin Stiborský
Hi!
We are using "features" for deployment
(https://cwiki.apache.org/KARAF/46-provisioning.html).

I did a quick test with Camel 2.11 and Karaf 2.3.1, completely fresh
installation and this I have there some dependencies troubles, like
missing "osgi.wiring.package=org.apache.aries.util" and few others.
This seems to be like problem on our side. I'll know more soon hopefully.

On Thu, May 23, 2013 at 2:12 PM, Raul Kripalani  wrote:
> It could be an issue with the way you deploy your bundles.
>
> If you drop them in the deploy/ directory, and you happen to deploy
> libraries that fulfill optional imports elsewhere, the OSGi framework could
> force a refresh of the entire bundle set. Hence justifying the observed
> behaviour to some extent.
>
> How exactly do you deploy your bundles?
>
> *Raúl Kripalani*
> Enterprise Architect, Open Source Integration specialist, Program
> Manager | Apache
> Camel Committer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>
> On Thu, May 23, 2013 at 1:04 PM, Martin Stiborský <
> martin.stibor...@gmail.com> wrote:
>
>> Not yet - I hasn't spent too much time on this and we postponed Camel
>> 2.11 upgrade right now.
>> I'll check debug log of camel and try to find the problem there.
>>
>> It seems I'm not alone on this :)
>>
>> http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html
>>
>> On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
>> > Hi
>> >
>> > Did you figure out this problem?
>> >
>> > On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
>> >  wrote:
>> >> Hi guys,
>> >> I'm trying to upgrade Camel and Karaf in our project to newer version,
>> >> as the Camel 2.11 is out.
>> >>
>> >> Camel 2.10.1 -> 2.11
>> >> Karaf 2.2.10 -> 2.3.1
>> >>
>> >> There were needed few modifications. nothing serious, but Camel and
>> >> Karaf behaves a little bit weird - CamelContent is created and
>> >> immediatelly shut down and then created down and again and again…
>> >> I can't see anything wrong in log output. Sometimes it even start ok,
>> >> sometimes it needs few tries to start correctly, but it's weird.
>> >> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
>> >> similar, so I know it's hard to find possible problem from such
>> >> description I provided here.
>> >>
>> >> Just if you spot something obvious or I missed something related to
>> upgrade..
>> >>
>> >> --
>> >> S pozdravem / Best regards
>> >> Martin Stiborský
>> >>
>> >> Jabber: st...@njs.netlab.cz
>> >> Twitter: http://www.twitter.com/stibi
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -
>> > Red Hat, Inc.
>> > FuseSource is now part of Red Hat
>> > Email: cib...@redhat.com
>> > Web: http://fusesource.com
>> > Twitter: davsclaus
>> > Blog: http://davsclaus.com
>> > Author of Camel in Action: http://www.manning.com/ibsen
>>
>>
>>
>> --
>> S pozdravem / Best regards
>> Martin Stiborský
>>
>> Jabber: st...@njs.netlab.cz
>> Twitter: http://www.twitter.com/stibi
>>



-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-05-23 Thread Raul Kripalani
It could be an issue with the way you deploy your bundles.

If you drop them in the deploy/ directory, and you happen to deploy
libraries that fulfill optional imports elsewhere, the OSGi framework could
force a refresh of the entire bundle set. Hence justifying the observed
behaviour to some extent.

How exactly do you deploy your bundles?

*Raúl Kripalani*
Enterprise Architect, Open Source Integration specialist, Program
Manager | Apache
Camel Committer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Thu, May 23, 2013 at 1:04 PM, Martin Stiborský <
martin.stibor...@gmail.com> wrote:

> Not yet - I hasn't spent too much time on this and we postponed Camel
> 2.11 upgrade right now.
> I'll check debug log of camel and try to find the problem there.
>
> It seems I'm not alone on this :)
>
> http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html
>
> On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
> > Hi
> >
> > Did you figure out this problem?
> >
> > On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
> >  wrote:
> >> Hi guys,
> >> I'm trying to upgrade Camel and Karaf in our project to newer version,
> >> as the Camel 2.11 is out.
> >>
> >> Camel 2.10.1 -> 2.11
> >> Karaf 2.2.10 -> 2.3.1
> >>
> >> There were needed few modifications. nothing serious, but Camel and
> >> Karaf behaves a little bit weird - CamelContent is created and
> >> immediatelly shut down and then created down and again and again…
> >> I can't see anything wrong in log output. Sometimes it even start ok,
> >> sometimes it needs few tries to start correctly, but it's weird.
> >> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
> >> similar, so I know it's hard to find possible problem from such
> >> description I provided here.
> >>
> >> Just if you spot something obvious or I missed something related to
> upgrade..
> >>
> >> --
> >> S pozdravem / Best regards
> >> Martin Stiborský
> >>
> >> Jabber: st...@njs.netlab.cz
> >> Twitter: http://www.twitter.com/stibi
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > Red Hat, Inc.
> > FuseSource is now part of Red Hat
> > Email: cib...@redhat.com
> > Web: http://fusesource.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> S pozdravem / Best regards
> Martin Stiborský
>
> Jabber: st...@njs.netlab.cz
> Twitter: http://www.twitter.com/stibi
>


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-05-23 Thread Martin Stiborský
Not yet - I hasn't spent too much time on this and we postponed Camel
2.11 upgrade right now.
I'll check debug log of camel and try to find the problem there.

It seems I'm not alone on this :)
http://camel.465427.n5.nabble.com/prevent-CamelContext-from-shutting-down-in-blueprint-td5733004.html

On Fri, May 3, 2013 at 8:35 AM, Claus Ibsen  wrote:
> Hi
>
> Did you figure out this problem?
>
> On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
>  wrote:
>> Hi guys,
>> I'm trying to upgrade Camel and Karaf in our project to newer version,
>> as the Camel 2.11 is out.
>>
>> Camel 2.10.1 -> 2.11
>> Karaf 2.2.10 -> 2.3.1
>>
>> There were needed few modifications. nothing serious, but Camel and
>> Karaf behaves a little bit weird - CamelContent is created and
>> immediatelly shut down and then created down and again and again…
>> I can't see anything wrong in log output. Sometimes it even start ok,
>> sometimes it needs few tries to start correctly, but it's weird.
>> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
>> similar, so I know it's hard to find possible problem from such
>> description I provided here.
>>
>> Just if you spot something obvious or I missed something related to upgrade..
>>
>> --
>> S pozdravem / Best regards
>> Martin Stiborský
>>
>> Jabber: st...@njs.netlab.cz
>> Twitter: http://www.twitter.com/stibi
>
>
>
> --
> Claus Ibsen
> -
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cib...@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen



-- 
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi


Re: Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-05-02 Thread Claus Ibsen
Hi

Did you figure out this problem?

On Wed, May 1, 2013 at 1:42 PM, Martin Stiborský
 wrote:
> Hi guys,
> I'm trying to upgrade Camel and Karaf in our project to newer version,
> as the Camel 2.11 is out.
>
> Camel 2.10.1 -> 2.11
> Karaf 2.2.10 -> 2.3.1
>
> There were needed few modifications. nothing serious, but Camel and
> Karaf behaves a little bit weird - CamelContent is created and
> immediatelly shut down and then created down and again and again…
> I can't see anything wrong in log output. Sometimes it even start ok,
> sometimes it needs few tries to start correctly, but it's weird.
> I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
> similar, so I know it's hard to find possible problem from such
> description I provided here.
>
> Just if you spot something obvious or I missed something related to upgrade..
>
> --
> S pozdravem / Best regards
> Martin Stiborský
>
> Jabber: st...@njs.netlab.cz
> Twitter: http://www.twitter.com/stibi



-- 
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen


Upgrade Camel 2.10.1 - 2.11.0 - Camel keeps restarting

2013-05-01 Thread Martin Stiborský
Hi guys,
I'm trying to upgrade Camel and Karaf in our project to newer version,
as the Camel 2.11 is out.

Camel 2.10.1 -> 2.11
Karaf 2.2.10 -> 2.3.1

There were needed few modifications. nothing serious, but Camel and
Karaf behaves a little bit weird - CamelContent is created and
immediatelly shut down and then created down and again and again…
I can't see anything wrong in log output. Sometimes it even start ok,
sometimes it needs few tries to start correctly, but it's weird.
I'm using Blueprint and some libraries, like camel-cxf, camel-ldap and
similar, so I know it's hard to find possible problem from such
description I provided here.

Just if you spot something obvious or I missed something related to upgrade..

--
S pozdravem / Best regards
Martin Stiborský

Jabber: st...@njs.netlab.cz
Twitter: http://www.twitter.com/stibi