Hi Bernd, I must correct myself. Adding the 'ns3'-prefix to all of the children does help. It seems all of the tags without prefix are ignored at boot-time which causes the OOM. So maybe a fix in the karaf-maven-plugin would be best, the prefix should be added to each child...
Kind regards, Steven On Sat, Nov 27, 2021 at 9:56 PM Steven Huypens <steven.huyp...@gmail.com> wrote: > Hi Bernd, > > - I do see 'blacklistedRepositories' in > http://karaf.apache.org/xmlns/features-processing/v1.0.0 > - With the namespace-prefix my app goes OOM immediately, so I cannot > compare both running systems. > - I tried adding the prefix to each child, but that did not help > > Kind regards, > Steven > > On Sat, Nov 27, 2021 at 9:23 PM Bernd Eckenfels <e...@zusammenkunft.net> > wrote: > >> In that case maybe the child (deny* list?) is ignored, not sure how >> strict the parser is in regards to namespaces. I don’t see a >> blacklistRepository element in the Schema anyway. It’s maybe best you >> inspect the running systems with feature:* commands and look for >> differences. >> >> >> >> -- >> http://bernd.eckenfels.net >> ________________________________ >> Von: Steven Huypens <steven.huyp...@gmail.com> >> Gesendet: Saturday, November 27, 2021 8:58:20 PM >> An: dev@karaf.apache.org <dev@karaf.apache.org> >> Betreff: Re: karaf-maven-plugin generates another >> org.apache.karaf.features.xml with Java 8/Java 11 >> >> Hi Bernd, >> >> Thanks for your response. The child elements have no prefix, eg. >> <blacklistedRepositories></blacklistedRepositories> >> >> I'm sorry but I do not understand what you mean. You think part of my >> org.apache.karaf.features.xml was previously ignored ? I haven't double >> checked, but that would really surprise me because we have quite some >> blacklistedFeatures en blacklistedBundles which would cause problems if >> ignored. >> >> Best regards, >> Steven >> >> On Sat, Nov 27, 2021 at 8:22 PM Bernd Eckenfels <e...@zusammenkunft.net> >> wrote: >> >> > Hello Steven >> > >> > How do the child elements of that element look like? Are they using >> > default/f/ns2 prefix and maybe the (semantically equivalent) change >> affects >> > your memory only because the old form ignored a actual entry for >> dependency? >> > >> > Bernd >> > >> > -- >> > http://bernd.eckenfels.net >> > ________________________________ >> > Von: Romain Manni-Bucau <rmannibu...@gmail.com> >> > Gesendet: Samstag, November 27, 2021 8:14 PM >> > An: dev >> > Betreff: Re: karaf-maven-plugin generates another >> > org.apache.karaf.features.xml with Java 8/Java 11 >> > >> > Hi Steven, >> > >> > >> > Maybe force jaxb version to an earlier one in karag pluhin dependencies >> in >> > your pom. >> > >> > >> > Le sam. 27 nov. 2021 à 20:05, Steven Huypens <steven.huyp...@gmail.com> >> a >> > écrit : >> > >> > > Hi all, >> > > >> > > I tried to create my custom Karaf distribution (using >> karaf-maven-plugin >> > > 4.3.2) with Java 11 for the first time, and I noticed a difference in >> the >> > > resulting org.apache.karaf.features.xml >> > > >> > > The line >> > > >> > > <featuresProcessing xmlns=" >> > > http://karaf.apache.org/xmlns/features-processing/v1.0.0" xmlns:f=" >> > > http://karaf.apache.org/xmlns/features/v1.6.0"> >> > > >> > > has been changed into >> > > >> > > <ns3:featuresProcessing xmlns:ns2=" >> > > http://karaf.apache.org/xmlns/features/v1.6.0" xmlns:ns3=" >> > > http://karaf.apache.org/xmlns/features-processing/v1.0.0"> >> > > >> > > which means a namespace has been added. Unfortunately this little >> change >> > > has a big impact because now my app immediately runs OutOfMemory when >> I >> > > start Karaf. There is very little DEBUG-logging, the behaviour is >> > somewhat >> > > like described in https://issues.apache.org/jira/browse/KARAF-6068 >> > > >> > > Removing the namespace fixes the problem. >> > > >> > > >> > > >> > > Do you have any idea how I can prevent my app from going OOM after >> this >> > > change ? Or how I can prevent the namespace from being added with Java >> > 11 ? >> > > It would be nice to understand the exact problem here. >> > > >> > > >> > > >> > > Kind regards, >> > > Steven >> > > >> > >> >