Hi JB, I've failed to create a simple example that demos the problem, however I've located the issue and it is more complex than I first thought. Basically felix is attempting to refresh the packages of a webapp whilst other webapps are being deployed. This leads to a complex deadlock that is mainly caused because pax only has a single deployment thread. The knock effect is that felix is blocked from refreshing bundles or resolving optional packages.
I am going to look at the effect of increasing the number of pax-web deployment threads. Cheers Paul ________________________________ From: Jean-Baptiste Onofré <[email protected]> Sent: 05 July 2022 17:23 To: dev <[email protected]> Subject: Re: Optional dependencies are not being resolved on Karaf 4.4.1-SNAPSHOT Hi Paul, do you have a simple test case to reproduce it ? Regards JB On Tue, Jul 5, 2022 at 4:21 PM Paul Stanley <[email protected]> wrote: > > Hi JB, > > Sorry I've tried a distribution based on 4.4.0, however it keep hitting a new > issue with a bundle dead lock on startup. Rather than investigate that I > will go back to looking at what is causing the optional package resolution > issue in 4.4.1 > If you have any pointers then please let me know. > > Thanks > Paul > > Get TypeApp for Android<http://www.typeapp.com/r> > On 2 Jul 2022, at 19:18, "Jean-Baptiste Onofré" > <[email protected]<mailto:[email protected]>> wrote: > > Do you observe same behavior on 4.4.0 ? > > Le ven. 1 juil. 2022 à 17:23, Paul Stanley <[email protected]> a écrit : > > Hello. > > > Has anyone else observed optional package resolution issues on karaf > 4.4.1-SNAPSHOT. > > > When I build the karaf deployment for my application the majority of the > base artifacts get added to the etc/startup.cfg file. These in turn get > loaded by the main deployment thread in karaf. At the end of the deployment > process these bundles get re-assessed to see if the bundles need to get > updated, however this process appears to ignore optional package > requirements. > > > The result is that many of the core services (such as spring-webmvc) fail > to functional correctly. This wasn't an issue in karaf 4.3. As such, > please can the community let me know if this is a general issue that has > been seen elsewhere? Or is it something that is peculiar to my setup. > > > Thanks > > Paul > > >
