You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jakub Herkel <jh...@gmail.com> on 2021/04/07 18:07:53 UTC

Karaf 4.3.1 issue when KARAF_BASE is set

Hi,

During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
lines before karaf start:
karaf: Ignoring predefined value for KARAF_HOME
WARNING: package org.apache.karaf.specs.locator not in java.base
Error starting karaf activator
org.apache.karaf.specs.activator.Activator:
org/apache/karaf/specs/locator/OsgiLocator

After some testing I found out that problem appears when KARAF_BASE is
set and it is not the same directory as KARAF_HOME. I think that
problem is in karaf.sh where I can see :
cd "${KARAF_BASE}"
ant later there is a line:
--patch-module java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar

So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
line is prefixed with KARAF_HOME?
i.e. --patch-module
java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar

with best regards

jakub

Re: Karaf 4.3.1 issue when KARAF_BASE is set

Posted by Freeman Fang <fr...@gmail.com>.
Hi Jakub,

Thanks for reporting this and this is a good catch!

Yes, we need to fix it up this way. I created
https://issues.apache.org/jira/browse/KARAF-7095 to track it.

Best Regards
Freeman

On Wed, Apr 7, 2021 at 2:08 PM Jakub Herkel <jh...@gmail.com> wrote:

> Hi,
>
> During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
> lines before karaf start:
> karaf: Ignoring predefined value for KARAF_HOME
> WARNING: package org.apache.karaf.specs.locator not in java.base
> Error starting karaf activator
> org.apache.karaf.specs.activator.Activator:
> org/apache/karaf/specs/locator/OsgiLocator
>
> After some testing I found out that problem appears when KARAF_BASE is
> set and it is not the same directory as KARAF_HOME. I think that
> problem is in karaf.sh where I can see :
> cd "${KARAF_BASE}"
> ant later there is a line:
> --patch-module
> java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
>
> So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
> KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
> line is prefixed with KARAF_HOME?
> i.e. --patch-module
> java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
>
> with best regards
>
> jakub
>

Re: Karaf 4.3.1 issue when KARAF_BASE is set

Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi Jakub,

Yes, we will fix that on wrapper as well.

Thanks,
Regards
JB

> Le 8 avr. 2021 à 09:35, Jakub Herkel <jh...@gmail.com> a écrit :
> 
> Today I found out that there is also similar problem with
> chronos-wraper. Could you also please check this?
> 
> Jakub
> 
> On Thu, Apr 8, 2021 at 7:12 AM Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
>> 
>> Hi Jakub,
>> 
>> Good catch. FYI, this "issue" is there for a while on main branch.
>> 
>> Freeman already did a fix, it will be included in Karaf 4.3.2.
>> 
>> Thanks !
>> Regards
>> JB
>> 
>>> Le 7 avr. 2021 à 20:07, Jakub Herkel <jh...@gmail.com> a écrit :
>>> 
>>> Hi,
>>> 
>>> During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
>>> lines before karaf start:
>>> karaf: Ignoring predefined value for KARAF_HOME
>>> WARNING: package org.apache.karaf.specs.locator not in java.base
>>> Error starting karaf activator
>>> org.apache.karaf.specs.activator.Activator:
>>> org/apache/karaf/specs/locator/OsgiLocator
>>> 
>>> After some testing I found out that problem appears when KARAF_BASE is
>>> set and it is not the same directory as KARAF_HOME. I think that
>>> problem is in karaf.sh where I can see :
>>> cd "${KARAF_BASE}"
>>> ant later there is a line:
>>> --patch-module java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
>>> 
>>> So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
>>> KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
>>> line is prefixed with KARAF_HOME?
>>> i.e. --patch-module
>>> java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
>>> 
>>> with best regards
>>> 
>>> jakub
>> 


Re: Karaf 4.3.1 issue when KARAF_BASE is set

Posted by Jakub Herkel <jh...@gmail.com>.
chronos-wrapper.conf -> karaf-wrapper.conf

On Thu, Apr 8, 2021 at 9:35 AM Jakub Herkel <jh...@gmail.com> wrote:
>
> Today I found out that there is also similar problem with
> chronos-wraper. Could you also please check this?
>
> Jakub
>
> On Thu, Apr 8, 2021 at 7:12 AM Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
> >
> > Hi Jakub,
> >
> > Good catch. FYI, this "issue" is there for a while on main branch.
> >
> > Freeman already did a fix, it will be included in Karaf 4.3.2.
> >
> > Thanks !
> > Regards
> > JB
> >
> > > Le 7 avr. 2021 à 20:07, Jakub Herkel <jh...@gmail.com> a écrit :
> > >
> > > Hi,
> > >
> > > During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
> > > lines before karaf start:
> > > karaf: Ignoring predefined value for KARAF_HOME
> > > WARNING: package org.apache.karaf.specs.locator not in java.base
> > > Error starting karaf activator
> > > org.apache.karaf.specs.activator.Activator:
> > > org/apache/karaf/specs/locator/OsgiLocator
> > >
> > > After some testing I found out that problem appears when KARAF_BASE is
> > > set and it is not the same directory as KARAF_HOME. I think that
> > > problem is in karaf.sh where I can see :
> > > cd "${KARAF_BASE}"
> > > ant later there is a line:
> > > --patch-module java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> > >
> > > So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
> > > KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
> > > line is prefixed with KARAF_HOME?
> > > i.e. --patch-module
> > > java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> > >
> > > with best regards
> > >
> > > jakub
> >

Re: Karaf 4.3.1 issue when KARAF_BASE is set

Posted by Jakub Herkel <jh...@gmail.com>.
Today I found out that there is also similar problem with
chronos-wraper. Could you also please check this?

Jakub

On Thu, Apr 8, 2021 at 7:12 AM Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
>
> Hi Jakub,
>
> Good catch. FYI, this "issue" is there for a while on main branch.
>
> Freeman already did a fix, it will be included in Karaf 4.3.2.
>
> Thanks !
> Regards
> JB
>
> > Le 7 avr. 2021 à 20:07, Jakub Herkel <jh...@gmail.com> a écrit :
> >
> > Hi,
> >
> > During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
> > lines before karaf start:
> > karaf: Ignoring predefined value for KARAF_HOME
> > WARNING: package org.apache.karaf.specs.locator not in java.base
> > Error starting karaf activator
> > org.apache.karaf.specs.activator.Activator:
> > org/apache/karaf/specs/locator/OsgiLocator
> >
> > After some testing I found out that problem appears when KARAF_BASE is
> > set and it is not the same directory as KARAF_HOME. I think that
> > problem is in karaf.sh where I can see :
> > cd "${KARAF_BASE}"
> > ant later there is a line:
> > --patch-module java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> >
> > So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
> > KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
> > line is prefixed with KARAF_HOME?
> > i.e. --patch-module
> > java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> >
> > with best regards
> >
> > jakub
>

Re: Karaf 4.3.1 issue when KARAF_BASE is set

Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi Jakub,

Good catch. FYI, this "issue" is there for a while on main branch.

Freeman already did a fix, it will be included in Karaf 4.3.2.

Thanks !
Regards
JB

> Le 7 avr. 2021 à 20:07, Jakub Herkel <jh...@gmail.com> a écrit :
> 
> Hi,
> 
> During migration from servicemix 7.0.1 to karaf 4.3.1 I can see these
> lines before karaf start:
> karaf: Ignoring predefined value for KARAF_HOME
> WARNING: package org.apache.karaf.specs.locator not in java.base
> Error starting karaf activator
> org.apache.karaf.specs.activator.Activator:
> org/apache/karaf/specs/locator/OsgiLocator
> 
> After some testing I found out that problem appears when KARAF_BASE is
> set and it is not the same directory as KARAF_HOME. I think that
> problem is in karaf.sh where I can see :
> cd "${KARAF_BASE}"
> ant later there is a line:
> --patch-module java.base=lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> 
> So org.apache.karaf.specs.locator-4.3.1.jar has to be located under
> KARAF_BASE/lib.  Due to this reason wouldn't it be better when the
> line is prefixed with KARAF_HOME?
> i.e. --patch-module
> java.base=$KARAF_HOME/lib/endorsed/org.apache.karaf.specs.locator-4.3.1.jar
> 
> with best regards
> 
> jakub