RE: Building Distribution with decanter boot feature

[Jörg Jansen]

Hi JB,

just created KARAF-6992.

Kind regards,
Joerg

From: Jean-Baptiste Onofre 
Sent: Dienstag, 12. Januar 2021 06:10
To: user@karaf.apache.org
Subject: Re: Building Distribution with decanter boot feature

Yes, please, create a Jira, I will fix.

Regards
JB


Le 11 janv. 2021 à 20:48, Jörg Jansen 
mailto:joerg.jan...@inform-software.com>> a 
écrit :

Hi JB,

thanks for your response.
I just tested with version 4.2.9 but with the same  result.
Switching back to decanter 2.2.0 works as expected, so it seem to be located to 
the config entry.

Should I rase a JIRA ticket?

Regards,
Joerg

From: Jean-Baptiste Onofre mailto:j...@nanthrax.net>>
Sent: Montag, 11. Januar 2021 17:00
To: user mailto:user@karaf.apache.org>>
Subject: Re: Building Distribution with decanter boot feature

Hi Joerg,

This config file is provided by  element of the decanter-common 
feature:

https://github.com/apache/karaf-decanter/blob/master/assembly/src/main/feature/feature.xml#L22

It should not be created "physically" by default (as it’s , not 
).

Does the assembly work with Karaf 4.2.9 maven plugin ?

Let me try to reproduce (on Linux, as it could be a Windows issue).

Regards
JB



Le 11 janv. 2021 à 16:48, Jörg Jansen 
mailto:joerg.jan...@inform-software.com>> a 
écrit :

Dear all,

I’m trying to build my customized distribution, using the karaf-maven-plugin.
When I’m adding the bootFeature decanter-collector-jmx, the build failed, 
because of a fileNotFoundException.

Caused by: java.nio.file.NoSuchFileException: 
O:\ws\gslisa\lisa-base\assemblies\gs-lisa-standalone\target\assembly\etc\org.apache.felix.eventadmin.impl.EventAdmin.cfg
at sun.nio.fs.WindowsException.translateToIOException 
(WindowsException.java:85)

Does anybody else face the same issue or know a fix/workaround?

Used versions:
Karaf: 4.3.0
Decanter: 2.5.0

Thanks,
Joerg

Re: JDK version for Karaf 4.3.0

[Jean-Baptiste Onofre]

Thanks for the update !

Regards
JB

> Le 12 janv. 2021 à 01:47, Oleg Cohen  a écrit :
> 
> Worked for me with JDK 15.0.1
> 
> Thank you!
> Oleg 
> 
> Sent from my iPhone
> 
>> On Jan 11, 2021, at 9:54 AM, Oleg Cohen > > wrote:
>> 
>> This is good news! I will try with my stuff.
>> 
>> Sent from my iPhone
>> 
>>> On Jan 11, 2021, at 9:23 AM, Michal Hlavac >> > wrote:
>>> 
>>> 
>>> Hi,
>>> 
>>> from what I've tested, it works on JDK 15 on project:
>>> https://github.com/hlavki/g-suite-identity-sync 
>>> 
>>> m.
>>> 
>>> On pondelok 11. januára 2021 15:12:02 CET Jean-Baptiste Onofre wrote:
>>> > Hi Oleg,
>>> >
>>> > JDK 11 works fine with Karaf 4.3.0.
>>> >
>>> > I’m testing JDK14/JDK15 now.
>>> >
>>> > Regards
>>> > JB
>>> >
>>> > > Le 11 janv. 2021 à 13:47, Oleg Cohen >> > > > a écrit :
>>> > >
>>> > > Greetings,
>>> > >
>>> > > Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.
>>> > >
>>> > > I am now using 11. Would love to move to a later one.
>>> > >
>>> > > Thank you!
>>> > > Oleg
>>> > >
>>> > 
>>> --
>>> [ michal hlavac ] [ m...@hlavki.eu  ] [ tel: +420 
>>> 773 205 794 ]

Re: Building Distribution with decanter boot feature

[Jean-Baptiste Onofre]

Yes, please, create a Jira, I will fix.

Regards
JB

> Le 11 janv. 2021 à 20:48, Jörg Jansen  a 
> écrit :
> 
> Hi JB,
>  
> thanks for your response.
> I just tested with version 4.2.9 but with the same  result.
> Switching back to decanter 2.2.0 works as expected, so it seem to be located 
> to the config entry.
>  
> Should I rase a JIRA ticket?
>  
> Regards,
> Joerg
>  
> From: Jean-Baptiste Onofre  
> Sent: Montag, 11. Januar 2021 17:00
> To: user 
> Subject: Re: Building Distribution with decanter boot feature
>  
> Hi Joerg,
>  
> This config file is provided by  element of the decanter-common 
> feature:
>  
> https://github.com/apache/karaf-decanter/blob/master/assembly/src/main/feature/feature.xml#L22
>  
> 
>  
> It should not be created "physically" by default (as it’s , not 
> ).
>  
> Does the assembly work with Karaf 4.2.9 maven plugin ?
>  
> Let me try to reproduce (on Linux, as it could be a Windows issue).
>  
> Regards
> JB
> 
> 
> Le 11 janv. 2021 à 16:48, Jörg Jansen  > a écrit :
>  
> Dear all, 
>  
> I’m trying to build my customized distribution, using the karaf-maven-plugin.
> When I’m adding the bootFeature decanter-collector-jmx, the build failed, 
> because of a fileNotFoundException.
>  
> Caused by: java.nio.file.NoSuchFileException: 
> O:\ws\gslisa\lisa-base\assemblies\gs-lisa-standalone\target\assembly\etc\org.apache.felix.eventadmin.impl.EventAdmin.cfg
> at sun.nio.fs.WindowsException.translateToIOException 
> (WindowsException.java:85)
>  
> Does anybody else face the same issue or know a fix/workaround?
>  
> Used versions: 
> Karaf: 4.3.0
> Decanter: 2.5.0
>  
> Thanks,
> Joerg

Re: Cave 4.2.1 - "Error downloading mvn:org.apache.cxf.karaf/cxf-karaf-commands/3.3.4" when install from custom distro on a disconnected server.

[Jean-Baptiste Onofre]

Hi,

I’m suspecting more a missing in the CXF feature. Cave don’t use 
cxf-karaf-commands, just CXF feature.

Let me check.

Regards
JB

> Le 11 janv. 2021 à 18:32, Paul Spencer  a écrit :
> 
> Karaf 4.2.9
> Cave 4.2.1
> 
> I have created a custom distribution including Cave 4.2.1 that will be 
> installed on a disconnected server.  Installing the feature cave-repository 
> fails with the following error:
> 
>   karaf@root()> feature:install cave-repository
>   Error executing command: Error:
>   Error downloading mvn:org.apache.cxf.karaf/cxf-karaf-commands/3.3.4
> 
> Adding the feature cxf-commands to the installedFeatures within the 
> karaf-maven-plugin resolved the issue.
> 
> Is this bug in the Cave feature definition?
>  If not, where is the bug?
> 
> 
> ***
> * From a working pom.xml
> ***
>
>org.apache.karaf.tooling
>karaf-maven-plugin
>${karaf.version}
>true
>
>
>
>standard
>
>
>cxf-commands 
>cave-repository
>
>true
>true
>false
>true
>
>
> 
> 
> Paul Spencer
> 

Re: JDK version for Karaf 4.3.0

[Oleg Cohen]

Worked for me with JDK 15.0.1

Thank you!
Oleg

Sent from my iPhone

On Jan 11, 2021, at 9:54 AM, Oleg Cohen  wrote:

This is good news! I will try with my stuff.

Sent from my iPhone

On Jan 11, 2021, at 9:23 AM, Michal Hlavac  wrote:



Hi,

from what I've tested, it works on JDK 15 on project:

https://github.com/hlavki/g-suite-identity-sync

m.

On pondelok 11. januára 2021 15:12:02 CET Jean-Baptiste Onofre wrote:

> Hi Oleg,

>

> JDK 11 works fine with Karaf 4.3.0.

>

> I’m testing JDK14/JDK15 now.

>

> Regards

> JB

>

> > Le 11 janv. 2021 à 13:47, Oleg Cohen  a
écrit :

> >

> > Greetings,

> >

> > Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.

> >

> > I am now using 11. Would love to move to a later one.

> >

> > Thank you!

> > Oleg

> >

>
-- 

[ michal hlavac ] [ m...@hlavki.eu ] [ tel: +420 773 205 794 ]

RE: Building Distribution with decanter boot feature

[Jörg Jansen]

Hi JB,

thanks for your response.
I just tested with version 4.2.9 but with the same  result.
Switching back to decanter 2.2.0 works as expected, so it seem to be located to 
the config entry.

Should I rase a JIRA ticket?

Regards,
Joerg

From: Jean-Baptiste Onofre 
Sent: Montag, 11. Januar 2021 17:00
To: user 
Subject: Re: Building Distribution with decanter boot feature

Hi Joerg,

This config file is provided by  element of the decanter-common 
feature:

https://github.com/apache/karaf-decanter/blob/master/assembly/src/main/feature/feature.xml#L22

It should not be created "physically" by default (as it’s , not 
).

Does the assembly work with Karaf 4.2.9 maven plugin ?

Let me try to reproduce (on Linux, as it could be a Windows issue).

Regards
JB


Le 11 janv. 2021 à 16:48, Jörg Jansen 
mailto:joerg.jan...@inform-software.com>> a 
écrit :

Dear all,

I’m trying to build my customized distribution, using the karaf-maven-plugin.
When I’m adding the bootFeature decanter-collector-jmx, the build failed, 
because of a fileNotFoundException.

Caused by: java.nio.file.NoSuchFileException: 
O:\ws\gslisa\lisa-base\assemblies\gs-lisa-standalone\target\assembly\etc\org.apache.felix.eventadmin.impl.EventAdmin.cfg
at sun.nio.fs.WindowsException.translateToIOException 
(WindowsException.java:85)

Does anybody else face the same issue or know a fix/workaround?

Used versions:
Karaf: 4.3.0
Decanter: 2.5.0

Thanks,
Joerg

Cave 4.2.1 - "Error downloading mvn:org.apache.cxf.karaf/cxf-karaf-commands/3.3.4" when install from custom distro on a disconnected server.

[Paul Spencer]

Karaf 4.2.9
Cave 4.2.1

I have created a custom distribution including Cave 4.2.1 that will be 
installed on a disconnected server.  Installing the feature cave-repository 
fails with the following error:

   karaf@root()> feature:install cave-repository
   Error executing command: Error:
Error downloading mvn:org.apache.cxf.karaf/cxf-karaf-commands/3.3.4

Adding the feature cxf-commands to the installedFeatures within the 
karaf-maven-plugin resolved the issue.

Is this bug in the Cave feature definition?
  If not, where is the bug?


***
* From a working pom.xml
***

org.apache.karaf.tooling
karaf-maven-plugin
${karaf.version}
true



standard


cxf-commands 
cave-repository

true
true
false
true




Paul Spencer

Re: Building Distribution with decanter boot feature

[Jean-Baptiste Onofre]

Hi Joerg,

This config file is provided by  element of the decanter-common 
feature:

https://github.com/apache/karaf-decanter/blob/master/assembly/src/main/feature/feature.xml#L22
 


It should not be created "physically" by default (as it’s , not 
).

Does the assembly work with Karaf 4.2.9 maven plugin ?

Let me try to reproduce (on Linux, as it could be a Windows issue).

Regards
JB

> Le 11 janv. 2021 à 16:48, Jörg Jansen  a 
> écrit :
> 
> Dear all, 
>  
> I’m trying to build my customized distribution, using the karaf-maven-plugin.
> When I’m adding the bootFeature decanter-collector-jmx, the build failed, 
> because of a fileNotFoundException.
>  
> Caused by: java.nio.file.NoSuchFileException: 
> O:\ws\gslisa\lisa-base\assemblies\gs-lisa-standalone\target\assembly\etc\org.apache.felix.eventadmin.impl.EventAdmin.cfg
> at sun.nio.fs.WindowsException.translateToIOException 
> (WindowsException.java:85)
>  
> Does anybody else face the same issue or know a fix/workaround?
>  
> Used versions: 
> Karaf: 4.3.0
> Decanter: 2.5.0
>  
> Thanks,
> Joerg

Building Distribution with decanter boot feature

[Jörg Jansen]

Dear all,

I'm trying to build my customized distribution, using the karaf-maven-plugin.
When I'm adding the bootFeature decanter-collector-jmx, the build failed, 
because of a fileNotFoundException.

Caused by: java.nio.file.NoSuchFileException: 
O:\ws\gslisa\lisa-base\assemblies\gs-lisa-standalone\target\assembly\etc\org.apache.felix.eventadmin.impl.EventAdmin.cfg
at sun.nio.fs.WindowsException.translateToIOException 
(WindowsException.java:85)

Does anybody else face the same issue or know a fix/workaround?

Used versions:
Karaf: 4.3.0
Decanter: 2.5.0

Thanks,
Joerg

Re: JDK version for Karaf 4.3.0

[Oleg Cohen]

This is good news! I will try with my stuff.

Sent from my iPhone

On Jan 11, 2021, at 9:23 AM, Michal Hlavac  wrote:



Hi,

from what I've tested, it works on JDK 15 on project:

https://github.com/hlavki/g-suite-identity-sync

m.

On pondelok 11. januára 2021 15:12:02 CET Jean-Baptiste Onofre wrote:

> Hi Oleg,

>

> JDK 11 works fine with Karaf 4.3.0.

>

> I’m testing JDK14/JDK15 now.

>

> Regards

> JB

>

> > Le 11 janv. 2021 à 13:47, Oleg Cohen  a
écrit :

> >

> > Greetings,

> >

> > Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.

> >

> > I am now using 11. Would love to move to a later one.

> >

> > Thank you!

> > Oleg

> >

>
-- 

[ michal hlavac ] [ m...@hlavki.eu ] [ tel: +420 773 205 794 ]

Re: JDK version for Karaf 4.3.0

[Michal Hlavac]

Hi,

from what I've tested, it works on JDK 15 on project:
https://github.com/hlavki/g-suite-identity-sync

m.

On pondelok 11. januára 2021 15:12:02 CET Jean-Baptiste Onofre wrote:
> Hi Oleg,
> 
> JDK 11 works fine with Karaf 4.3.0.
> 
> I’m testing JDK14/JDK15 now.
> 
> Regards
> JB
> 
> > Le 11 janv. 2021 à 13:47, Oleg Cohen  a écrit :
> > 
> > Greetings,
> > 
> > Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.
> > 
> > I am now using 11. Would love to move to a later one.
> > 
> > Thank you!
> > Oleg
> > 
> 
-- 
[ michal hlavac ] [ m...@hlavki.eu[1] ] [ tel: +420 773 205 794 ] 


[1] mailto:m...@hlavki.eu

Re: Bundle transitions to and stays Waiting when service it depends on stops/starts

[Kevin Schmidt]

JB,

Yes, when the service is started, the client bundle using the service
remains in the waiting state.  But the REST endpoint the client bundle is
providing continues to work.

And yes, restarting the client bundle causes it to go back to active.

And yes, I'm aware of the proxy and grace period.  I actually start both
the client and server bundles and have both active before doing the steps I
outlined.  So the grace period should no longer be in play should it?  Note
that the client bundle remains in the waiting state forever, it doesn't
seem to timeout like it would on startup due to the grace period so this
seems different.

Also, I made versions of the service that use Blueprint and just an
Activator, instead of using DS, and itt behaves the same.

When the client is in the waiting state, diag returns this:

Status: Waiting
Blueprint
1/11/21 5:53 AM
Missing dependencies:
(objectClass=)
Declarative Services

However, doing a service:list on the service interface name shows there is
a service registered:

 service.bundleid = 155
 service.id = 174
 service.scope = singleton
Provided by :
 
Used by:
 

So it is unclear why the client remains in the waiting state.

Yes, in this case I'm directly using stop/start on the bundle and these
bundles are not part of a feature.  It is unclear to me though why that
should make a difference?  Since Blueprint is using a proxy, it seems
normal that one should be able to stop/start the bundle providing the
proxied service and as long as that restart happens when no requests in
in-flight (which works fine), or if a request is in-flight the restart
happens before the Blueprint configured timeout occurs (this is the
scenario that doesn't work), the client should be unaffected and remain or
get back to the active state.  Being stuck in the waiting state is
incorrect and misleading since the bundle is operating correctly, IMHO.

What specifically would have to be a feature to get the resolver involved
and have it work?  Would I need a feature that includes the client, service
interface, and service implementation bundles?  Or something different?  If
a feature is required, I'm just surprised as I didn't pick up on that in
any docs or using Karaf over a number of years, but I guess one can learn
something new every day!

I'm happy to provide sample source code for my scenario if needed.

Thanks,

Kevin

On Sun, Jan 10, 2021 at 10:28 PM Jean-Baptiste Onofre 
wrote:

> Hi Kevin,
>
> To be sure I understand your use case: when you start the bundle providing
> the service, the bundles using it stay in waiting state ?
>
> If you restart the "client" bundles, does it work ?
>
> As reminder, blueprint uses a proxy to the service, and evaluated at start
> time (grace period). So, I’m pretty sure it works if you restart the
> blueprint bundle, correct ?
>
> I’m not sure it could consider as a bug. I guess you are using directly
> bundle (stop/start), not feature, so the resolver is not involved and can’t
> automatically restart/refresh the blueprint bundle (you have to do it
> manually). If you add a requirement and use feature, it should work.
>
> Regards
> JB
>
> > Le 11 janv. 2021 à 01:13, Kevin Schmidt  a écrit :
> >
> > Hi,
> >
> > All of the below is done using Karaf 4.2.9.
> >
> > I have a bundle exposing a REST endpoint that is deployed using
> Blueprint that uses a service that is deployed using Declarative Services.
> When both bundles are active, all is well.
> >
> > If I stop the service bundle (DS), it shows as Resolved but the REST
> bundle (BP) shows as Active still, all as expected.
> >
> > When I make a request to the endpoint, it blocks with the BP proxy doing
> its damping as expected.  Also, the REST bundle (BP) state changes to
> Waiting at this point.  Is this correct and expected?
> >
> > I then start the service bundle (DS) and it goes back to Active and the
> execution completes and the REST endpoint returns.  However, the REST
> bundle remains in the Waiting state.  This isn't correct is it?
> >
> > Note that requests to the REST endpoint do work in this state, but it is
> a bit disconcerting to have the REST endpoint bundle not Active.
> >
> > Also, FWIW, I just tried the above with 4.3.0 as well and it behaves the
> same.
> >
> > Is this a bug?  Should I open a Jira?
> >
> > Thanks,
> >
> > Kevin
>
>

Re: JDK version for Karaf 4.3.0

[Jean-Baptiste Onofre]

Hi Oleg,

JDK 11 works fine with Karaf 4.3.0.

I’m testing JDK14/JDK15 now.

Regards
JB

> Le 11 janv. 2021 à 13:47, Oleg Cohen  a écrit :
> 
> Greetings,
> 
> Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.
> 
> I am now using 11. Would love to move to a later one.
> 
> Thank you!
> Oleg
> 
> -- 
> Oleg Cohen  |  Principal  |  A S S U R E B R I D G E
> Office: +1 617 564 0737 <>  |  Mobile: +1 617 455 7927 <>  |  Fax: +1 888 409 
> 6995 <>
> Email: oleg.co...@assurebridge.com   |  
> www.assurebridge.com 

JDK version for Karaf 4.3.0

[Oleg Cohen]

Greetings,

Wanted to confirm the latest JDK that is supported by Karaf 4.3.0.

I am now using 11. Would love to move to a later one.

Thank you!
Oleg

-- 
*Oleg Cohen  |  Principal  |  **A S S U R E B R I D G E*
*Office: +1 617 564 0737  |  Mobile: +1 617 455 7927  |  Fax: +1 888 409
6995*
*Email: oleg.co...@assurebridge.com   **|
 www.assurebridge.com *