You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by James Carman <ja...@carmanconsulting.com> on 2016/08/20 19:43:37 UTC
Detecting persistent-id sharing...
We have a situation where we don't really know where we have the issue of
two Blueprint bundles attempting to share the same persistent-id. We just
see the "spinning" symptom, so we assume that it's there. Is there any
command that can help me narrow it down?
Re: Detecting persistent-id sharing...
Posted by James Carman <ja...@carmanconsulting.com>.
I think they are in two separate bundles. This isn't something that is
intentional. We have our system set up as plug-ins. So, I don't know who is
the offender. We just add the plug-ins to our container and they get
registered using the whiteboard pattern
On Sun, Aug 21, 2016 at 1:55 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi James,
>
> you mean that you use <cm:property-placeholder/> in two blueprint
> descriptors using the same persistent-id ?
>
> Are the blueprint descriptors in two containers (two bundles) or the
> same one ?
>
> Regards
> JB
>
> On 08/20/2016 09:43 PM, James Carman wrote:
> > We have a situation where we don't really know where we have the issue
> > of two Blueprint bundles attempting to share the same persistent-id. We
> > just see the "spinning" symptom, so we assume that it's there. Is there
> > any command that can help me narrow it down?
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Detecting persistent-id sharing...
Posted by James Carman <ja...@carmanconsulting.com>.
Hmmmm. I'll have to see if that applies. Thanks!
On Tue, Aug 23, 2016 at 9:24 PM Nick Baker <nb...@pentaho.com> wrote:
> We actually just had an occurrence of the “spinning” blueprint due to a
> <property-placeholder update-strategy=reload> but it wasn’t two bundles. It
> was one bundle referenced in two features! Removing the reference from one
> and adding a feature dependency instead “fixed” it for us.
>
>
>
> -Nick
>
>
>
> *From: *James Carman <ja...@carmanconsulting.com>
> *Reply-To: *"user@karaf.apache.org" <us...@karaf.apache.org>
> *Date: *Tuesday, August 23, 2016 at 9:14 PM
> *To: *"user@karaf.apache.org" <us...@karaf.apache.org>
> *Subject: *Re: Detecting persistent-id sharing...
>
>
>
> No ideas?
>
> On Sun, Aug 21, 2016 at 9:44 AM James Carman <ja...@carmanconsulting.com>
> wrote:
>
> And, yes, that is exactly what I am talking about. A property placeholder
> is defined in two different blueprint containers in two different bundles.
> They both try to use the same configuration and it starts this "spinning"
> process
>
>
>
> On Sun, Aug 21, 2016 at 1:55 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
> Hi James,
>
> you mean that you use <cm:property-placeholder/> in two blueprint
> descriptors using the same persistent-id ?
>
> Are the blueprint descriptors in two containers (two bundles) or the
> same one ?
>
> Regards
> JB
>
> On 08/20/2016 09:43 PM, James Carman wrote:
> > We have a situation where we don't really know where we have the issue
> > of two Blueprint bundles attempting to share the same persistent-id. We
> > just see the "spinning" symptom, so we assume that it's there. Is there
> > any command that can help me narrow it down?
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
Re: Detecting persistent-id sharing...
Posted by Nick Baker <nb...@pentaho.com>.
We actually just had an occurrence of the “spinning” blueprint due to a <property-placeholder update-strategy=reload> but it wasn’t two bundles. It was one bundle referenced in two features! Removing the reference from one and adding a feature dependency instead “fixed” it for us.
-Nick
From: James Carman <ja...@carmanconsulting.com>
Reply-To: "user@karaf.apache.org" <us...@karaf.apache.org>
Date: Tuesday, August 23, 2016 at 9:14 PM
To: "user@karaf.apache.org" <us...@karaf.apache.org>
Subject: Re: Detecting persistent-id sharing...
No ideas?
On Sun, Aug 21, 2016 at 9:44 AM James Carman <ja...@carmanconsulting.com>> wrote:
And, yes, that is exactly what I am talking about. A property placeholder is defined in two different blueprint containers in two different bundles. They both try to use the same configuration and it starts this "spinning" process
On Sun, Aug 21, 2016 at 1:55 AM Jean-Baptiste Onofré <jb...@nanthrax.net>> wrote:
Hi James,
you mean that you use <cm:property-placeholder/> in two blueprint
descriptors using the same persistent-id ?
Are the blueprint descriptors in two containers (two bundles) or the
same one ?
Regards
JB
On 08/20/2016 09:43 PM, James Carman wrote:
> We have a situation where we don't really know where we have the issue
> of two Blueprint bundles attempting to share the same persistent-id. We
> just see the "spinning" symptom, so we assume that it's there. Is there
> any command that can help me narrow it down?
>
--
Jean-Baptiste Onofré
jbonofre@apache.org<ma...@apache.org>
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Detecting persistent-id sharing...
Posted by James Carman <ja...@carmanconsulting.com>.
No ideas?
On Sun, Aug 21, 2016 at 9:44 AM James Carman <ja...@carmanconsulting.com>
wrote:
> And, yes, that is exactly what I am talking about. A property placeholder
> is defined in two different blueprint containers in two different bundles.
> They both try to use the same configuration and it starts this "spinning"
> process
>
> On Sun, Aug 21, 2016 at 1:55 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi James,
>>
>> you mean that you use <cm:property-placeholder/> in two blueprint
>> descriptors using the same persistent-id ?
>>
>> Are the blueprint descriptors in two containers (two bundles) or the
>> same one ?
>>
>> Regards
>> JB
>>
>> On 08/20/2016 09:43 PM, James Carman wrote:
>> > We have a situation where we don't really know where we have the issue
>> > of two Blueprint bundles attempting to share the same persistent-id. We
>> > just see the "spinning" symptom, so we assume that it's there. Is there
>> > any command that can help me narrow it down?
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
Re: Detecting persistent-id sharing...
Posted by James Carman <ja...@carmanconsulting.com>.
And, yes, that is exactly what I am talking about. A property placeholder
is defined in two different blueprint containers in two different bundles.
They both try to use the same configuration and it starts this "spinning"
process
On Sun, Aug 21, 2016 at 1:55 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Hi James,
>
> you mean that you use <cm:property-placeholder/> in two blueprint
> descriptors using the same persistent-id ?
>
> Are the blueprint descriptors in two containers (two bundles) or the
> same one ?
>
> Regards
> JB
>
> On 08/20/2016 09:43 PM, James Carman wrote:
> > We have a situation where we don't really know where we have the issue
> > of two Blueprint bundles attempting to share the same persistent-id. We
> > just see the "spinning" symptom, so we assume that it's there. Is there
> > any command that can help me narrow it down?
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Detecting persistent-id sharing...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi James,
you mean that you use <cm:property-placeholder/> in two blueprint
descriptors using the same persistent-id ?
Are the blueprint descriptors in two containers (two bundles) or the
same one ?
Regards
JB
On 08/20/2016 09:43 PM, James Carman wrote:
> We have a situation where we don't really know where we have the issue
> of two Blueprint bundles attempting to share the same persistent-id. We
> just see the "spinning" symptom, so we assume that it's there. Is there
> any command that can help me narrow it down?
>
--
Jean-Baptiste Onofr�
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com