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 <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, August 23, 2016 at 9:14 PM To: "[email protected]" <[email protected]> Subject: Re: Detecting persistent-id sharing... No ideas? On Sun, Aug 21, 2016 at 9:44 AM James Carman <[email protected]<mailto:[email protected]>> 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é <[email protected]<mailto:[email protected]>> 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é [email protected]<mailto:[email protected]> http://blog.nanthrax.net Talend - http://www.talend.com
