On 19 sept. 2012, at 15:34, "Merryweather, Darrell" <[email protected]> wrote:
> Hi Clement > > I'd be happy to, can you point me at the jira server and I'll try and get > it done before the end of the week Here it is: https://issues.apache.org/jira/browse/FELIX Don't forget to set the component to iPOJO (my filter is using this attribute :-)) Thanks ! Clement > > Thanks > > D > > On 19/09/2012 14:32, "Clement Escoffier" <[email protected]> > wrote: > >> Hi, >> >> It seems to be a new bug. Could you open a jira issue. >> >> Regards, >> >> Clement >> >> On 19 sept. 2012, at 14:23, "Merryweather, Darrell" >> <[email protected]> wrote: >> >>> Hi >>> >>> We are using version 1.8.2 of iPOJO >>> >>> Thanks >>> >>> Darrell Merryweather >>> >>> On 19/09/2012 13:17, "Clement Escoffier" <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Do you know which version of iPOJO he's using ? >>>> I think we fixed this bug already. >>>> >>>> Regards, >>>> >>>> Clement >>>> >>>> On 19 sept. 2012, at 13:55, Varun Mitra <[email protected]> wrote: >>>> >>>>> A customer is installing a package that restarts various other >>>>> bundles, one of these being the iPOJO framework so that it can pick up >>>>> all of the iPOJO's that have been created. The problem comes when >>>>> deploying multiple CQ5 pages. There appears to be some Threading issue >>>>> with the OSGI framework causing the below exception in the logs, the >>>>> end >>>>> result the OSGI framework is left with some bundles not being started >>>>> correctly. >>>>> The exception we see in the logs is: - >>>>> 31.07.2012 14:54:10.281 *ERROR* [FelixDispatchQueue] >>>>> org.apache.felix.ipojo FrameworkEvent ERROR >>>>> (java.util.ConcurrentModificationException) >>>>> java.util.ConcurrentModificationException >>>>> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) >>>>> at java.util.HashMap$KeyIterator.next(HashMap.java:828) >>>>> at >>>>> >>>>> org.apache.felix.ipojo.InstanceCreator.removeInstancesFromBundle(Instan >>>>> ce >>>>> Creator.java:117) >>>>> at >>>>> org.apache.felix.ipojo.Extender.closeManagementFor(Extender.java:147) >>>>> at org.apache.felix.ipojo.Extender.bundleChanged(Extender.java:129) >>>>> ... >>>>> Customer has an automated build and deploy landscape using ANT/IVY as >>>>> the build/dependency management tool. >>>>> As per the logs[1], it can be seen that one thread is trying to >>>>> register the iPOJO component while another is unregistering it. >>>>> Is there a way for having a thread safe mechanism for installing a >>>>> package and waiting for the OSGI bundles to be restarted? >>>>> >>>>> >>>>> >>>>> [1] >>>>> 31.07.2012 13:12:31.312 *INFO* [OsgiInstallerImpl] >>>>> org.apache.felix.ipojo Service [3067] ServiceEvent UNREGISTERING >>>>> 31.07.2012 13:12:31.315 *INFO* [Thread-1901] org.apache.felix.ipojo >>>>> Service [3184] ServiceEvent REGISTERED >>>>> 31.07.2012 13:12:31.335 *INFO* [OsgiInstallerImpl] >>>>> com.sap.components.contactcta Service [com.sap.cta.configuration,3066] >>>>> ServiceEvent UNREGISTERING >>>>> 31.07.2012 13:12:31.335 *ERROR* [FelixDispatchQueue] >>>>> org.apache.felix.ipojo FrameworkEvent ERROR >>>>> (java.util.ConcurrentModificationException) >>>>> java.util.ConcurrentModificationException >>>>> >>>>> >>>>> Varun mitra| Technical Support Engineer| adobe systems inc. >>>>> >>>> >>> >> >
