Hi J.B. , hi Francois, thanks for your quick answer and sorry for the delay.
Is there any way to detect such a cycle, i.e. is there a command such as feature:tree like for the dependency tree in maven that could help me identifying such cycles? Strange thing is: the exact same setup worked fine with Karaf 4.3.2. So probably one of our referenced features in other feature repositories causes this behavior. Kind regards, Thomas Am Sa., 18. Sept. 2021 um 06:22 Uhr schrieb Jean-Baptiste Onofre < [email protected]>: > Hi Thomas, > > I think you have a loop in your features (a feature A require feature B > that require feature A). > > I know that Pax CDI has a cycle like this (I have a fix but not yet > released). > > Regards > JB > > > Le 17 sept. 2021 à 17:00, Thomas Driessen <[email protected]> > a écrit : > > > > Hi, > > > > we just updated to the new Karaf 4.3.3 and suddenly we always get a > StackOverflowError as soon as we try to do a feature:refresh: > > > > 2021-09-17T14:56:44,239 | ERROR | Karaf local console user karaf | > ShellUtil | 44 - org.apache.karaf.shell.core - 4.3.3 > | Exception caught while executing command > > java.util.concurrent.ExecutionException: java.lang.StackOverflowError > > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > ~[?:?] > > at java.util.concurrent.FutureTask.get(FutureTask.java:191) > ~[?:?] > > at > org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.run(CommandSessionImpl.java:855) > ~[?:?] > > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > ~[?:?] > > at java.util.concurrent.FutureTask.run(FutureTask.java:264) > ~[?:?] > > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > ~[?:?] > > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > ~[?:?] > > at java.lang.Thread.run(Thread.java:829) [?:?] > > Caused by: java.lang.StackOverflowError > > at > org.apache.karaf.features.internal.region.Subsystem.<init>(Subsystem.java:149) > ~[?:?] > > at > org.apache.karaf.features.internal.region.SubsystemResolver.prepare(SubsystemResolver.java:127) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:390) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.handlePrerequisites(Deployer.java:1121) > ~[?:?] > > at > org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:394) > ~[?:?] > > > > Is this a known bug? Or is there anyone else experiencing this? > > > > Kind regards, > > Thomas > >
