Camel 3.16.0 on Karaf 4.4.0 - missing dependency org.apache.camel.camel-management-api

[Oleg Cohen]

Greetings,

I am running Karaf 4.4.0 with JDK 17.0.2

When I try installing camel-core I get the following error:

karaf@root()> feature:install camel-core
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
missing requirement [root] osgi.identity; osgi.identity=camel-core; 
type=karaf.feature; version="[3.16.0,3.16.0]"; 
filter:="(&(osgi.identity=camel-core)(type=karaf.feature)(version>=3.16.0)(version<=3.16.0))"
 [caused by: Unable to resolve camel-core/3.16.0: missing requirement 
[camel-core/3.16.0] osgi.identity; 
osgi.identity=org.apache.camel.camel-management-api; type=osgi.bundle; 
version="[3.16.0,3.16.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.camel.camel-management-api/3.16.0: missing requirement 
[org.apache.camel.camel-management-api/3.16.0] osgi.ee; 
filter:="(&(osgi.ee=JavaSE)(version=11))"]]
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
at 
org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:433)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:420)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:374)
at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:256)
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:399)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1069)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:1004)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
camel-core/3.16.0: missing requirement [camel-core/3.16.0] osgi.identity; 
osgi.identity=org.apache.camel.camel-management-api; type=osgi.bundle; 
version="[3.16.0,3.16.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.camel.camel-management-api/3.16.0: missing requirement 
[org.apache.camel.camel-management-api/3.16.0] osgi.ee; 
filter:="(&(osgi.ee=JavaSE)(version=11))"]
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
org.apache.camel.camel-management-api/3.16.0: missing requirement 
[org.apache.camel.camel-management-api/3.16.0] osgi.ee; 
filter:="(&(osgi.ee=JavaSE)(version=11))"
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 13 more
Error executing command: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=camel-core; type=karaf.feature; 
version="[3.16.0,3.16.0]"; 
filter:="(&(osgi.identity=camel-core)(type=karaf.feature)(version>=3.16.0)(version<=3.16.0))"
 [caused by: Unable to resolve camel-core/3.16.0: missing requirement 
[camel-core/3.16.0] osgi.identity; 
osgi.identity=org.apache.camel.camel-management-api; type=osgi.bundle; 
version="[3.16.0,3.16.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.camel.camel-management-api/3.16.0: missing requirement 
[org.apache.camel.camel-management-api/3.16.0] osgi.ee; 
filter:="(&(osgi.ee=JavaSE)(version=11))”]]


There seems to be a missing dependency: org.apache.camel.camel-management-api

Wonder if anybody ran into the issue and if there is a fix or a workaround?

Thank you!
Oleg

Re: Karaf and SpringBoot

[Oleg Cohen]

Hi JB,

Thank you for the info!

So, the best course of action is to wait for K5? There is an early
release available right?

Best
Oleg

Sent from my iPhone

> On Jan 18, 2022, at 2:25 PM, Jean-Baptiste Onofré  wrote:
>
> Hi Oleg,
>
> Yes, it's always possible to wrap spring-boot app as a uber bundle and
> use the controller from K5.
>
> Before starting K5, I added a spring-boot deployer doing that.
>
> Not sure it makes sense to have it in K4 while K5 is coming.
>
> Regards
> JB
>
>> On 18/01/2022 19:24, Oleg Cohen wrote:
>> Greetings,
>>
>> I have a general question. I know that Karaf 5 is coming with a
>> capability to host SpringBoot based services. Are there any capabilities
>> to deploy such services exist in Karaf 4?
>>
>> 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
>> <mailto:oleg.co...@assurebridge.com>_ **| www.assurebridge.com
>> <http://www.assurebridge.com>*

Karaf and SpringBoot

[Oleg Cohen]

Greetings,

I have a general question. I know that Karaf 5 is coming with a capability
to host SpringBoot based services. Are there any capabilities to deploy
such services exist in Karaf 4?

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 <http://www.assurebridge.com>*

Re: Karaf 4.3.x "Apache Log4j Remote Code Execution Vulnerability" mitigation?

[Oleg Cohen]

Thank  you!

On Dec 12, 2021, at 10:13 AM, Jean-Baptiste Onofre  wrote:

log4j2.formatMsgNoLookups=true in etc/system.properties should do the trick.

Regards
JB

Le 12 déc. 2021 à 18:10, Oleg Cohen  a écrit :

Hi JB,

Thank you for the info.

Do you have an example of how this can be dome in system.properties?

Best,
Oleg

On Dec 12, 2021, at 10:08 AM, JB Onofré  wrote:

You can use system.properties to set the msg format on existing version.

Else Karaf 4.3.4 will include fix by default.

Le 12 déc. 2021 à 17:54, Paul Spencer  a écrit :

For users of Karaf 4.3.x, what is the recommended mitigation for "Apache
Log4j Remote Code Execution Vulnerability", CVE-2021-44228?

Paul Spencer

Re: Karaf 4.3.x "Apache Log4j Remote Code Execution Vulnerability" mitigation?

[Oleg Cohen]

Hi JB,

Thank you for the info.

Do you have an example of how this can be dome in system.properties?

Best,
Oleg

> On Dec 12, 2021, at 10:08 AM, JB Onofré  wrote:
> 
> You can use system.properties to set the msg format on existing version. 
> 
> Else Karaf 4.3.4 will include fix by default. 
> 
>> Le 12 déc. 2021 à 17:54, Paul Spencer  a écrit :
>> 
>> For users of Karaf 4.3.x, what is the recommended mitigation for "Apache 
>> Log4j Remote Code Execution Vulnerability", CVE-2021-44228?
>> 
>> Paul Spencer
>> 
> 

Re: Weird sshd-SshServer SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after messages

[Oleg Cohen]

Hi JB,

Definitely my problem :-) Was able to figure it out. Wrong port for the POD 
monitoring.

Thank you!
Oleg

> On May 6, 2021, at 10:24 AM, Oleg Cohen  wrote:
> 
> Hi JB,
> 
> I didn’t install anything specific. No Decanter. Is there a way to trace and 
> see where the SSH requests are coming from?
> 
> Thank you!
> Oleg
> 
>> On May 6, 2021, at 10:10 AM, Jean-Baptiste Onofre  wrote:
>> 
>> Hi Oleg,
>> 
>> Maybe you have a monitoring solution (as Decanter) that pull the MBean, and 
>> so perform ssh connection when listing the instances in the InstanceMBean.
>> 
>> It seems that something tries a ssh connect ;)
>> 
>> Regards
>> JB
>> 
>>> Le 6 mai 2021 à 15:53, Oleg Cohen  a écrit :
>>> 
>>> Greetings,
>>> 
>>> I started a new karat instance in a Kubernetes pod from a custom distro.
>>> 
>>> I am seeing the following set of messages in the log every few seconds. 
>>> 
>>> 2021-05-06T13:49:30,946 | INFO  | 
>>> sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl  
>>>   | 309 - org.apache.sshd.osgi - 2.5.1 | 
>>> Disconnecting(ServerSessionImpl[null@/169.254.175.250:49648]): 
>>> SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after 120034/12 
>>> ms.
>>> 2021-05-06T13:49:30,946 | WARN  | 
>>> sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl  
>>>   | 309 - org.apache.sshd.osgi - 2.5.1 | 
>>> disconnect(ServerSessionImpl[null@/169.254.175.250:49648]) operation failed 
>>> (IOException) for reason=SSH2_DISCONNECT_PROTOCOL_ERROR [Detected 
>>> AuthTimeout after 120034/12 ms.]: Broken pipe
>>> 2021-05-06T13:49:30,946 | WARN  | 
>>> sshd-SshServer[7467ccad](port=8101)-nio2-thread-2 | ServerSessionImpl   
>>>  | 309 - org.apache.sshd.osgi - 2.5.1 | 
>>> exceptionCaught(ServerSessionImpl[null@/169.254.175.250:49648])[state=Opened]
>>>  IOException: Broken pipe
>>> 
>>> The pod is completely isolated.
>>> 
>>> Wonder if anybody has encountered this behavior before?
>>> 
>>> Thank you!
>>> Oleg
>> 
> 

Re: Weird sshd-SshServer SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after messages

[Oleg Cohen]

Hi JB,

I didn’t install anything specific. No Decanter. Is there a way to trace and 
see where the SSH requests are coming from?

Thank you!
Oleg

> On May 6, 2021, at 10:10 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> Maybe you have a monitoring solution (as Decanter) that pull the MBean, and 
> so perform ssh connection when listing the instances in the InstanceMBean.
> 
> It seems that something tries a ssh connect ;)
> 
> Regards
> JB
> 
>> Le 6 mai 2021 à 15:53, Oleg Cohen  a écrit :
>> 
>> Greetings,
>> 
>> I started a new karat instance in a Kubernetes pod from a custom distro.
>> 
>> I am seeing the following set of messages in the log every few seconds. 
>> 
>> 2021-05-06T13:49:30,946 | INFO  | 
>> sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl   
>>  | 309 - org.apache.sshd.osgi - 2.5.1 | 
>> Disconnecting(ServerSessionImpl[null@/169.254.175.250:49648]): 
>> SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after 120034/12 ms.
>> 2021-05-06T13:49:30,946 | WARN  | 
>> sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl   
>>  | 309 - org.apache.sshd.osgi - 2.5.1 | 
>> disconnect(ServerSessionImpl[null@/169.254.175.250:49648]) operation failed 
>> (IOException) for reason=SSH2_DISCONNECT_PROTOCOL_ERROR [Detected 
>> AuthTimeout after 120034/12 ms.]: Broken pipe
>> 2021-05-06T13:49:30,946 | WARN  | 
>> sshd-SshServer[7467ccad](port=8101)-nio2-thread-2 | ServerSessionImpl
>> | 309 - org.apache.sshd.osgi - 2.5.1 | 
>> exceptionCaught(ServerSessionImpl[null@/169.254.175.250:49648])[state=Opened]
>>  IOException: Broken pipe
>> 
>> The pod is completely isolated.
>> 
>> Wonder if anybody has encountered this behavior before?
>> 
>> Thank you!
>> Oleg
> 

Weird sshd-SshServer SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after messages

[Oleg Cohen]

Greetings,

I started a new karat instance in a Kubernetes pod from a custom distro.

I am seeing the following set of messages in the log every few seconds. 

2021-05-06T13:49:30,946 | INFO  | 
sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl  
  | 309 - org.apache.sshd.osgi - 2.5.1 | 
Disconnecting(ServerSessionImpl[null@/169.254.175.250:49648]): 
SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after 120034/12 ms.
2021-05-06T13:49:30,946 | WARN  | 
sshd-SshServer[7467ccad](port=8101)-timer-thread-1 | ServerSessionImpl  
  | 309 - org.apache.sshd.osgi - 2.5.1 | 
disconnect(ServerSessionImpl[null@/169.254.175.250:49648]) operation failed 
(IOException) for reason=SSH2_DISCONNECT_PROTOCOL_ERROR [Detected AuthTimeout 
after 120034/12 ms.]: Broken pipe
2021-05-06T13:49:30,946 | WARN  | 
sshd-SshServer[7467ccad](port=8101)-nio2-thread-2 | ServerSessionImpl   
 | 309 - org.apache.sshd.osgi - 2.5.1 | 
exceptionCaught(ServerSessionImpl[null@/169.254.175.250:49648])[state=Opened] 
IOException: Broken pipe

The pod is completely isolated.

Wonder if anybody has encountered this behavior before?

Thank you!
Oleg

Re: Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

Thank you, JB!!!

> On Apr 1, 2021, at 11:57 PM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> I didn’t take a look yet.
> 
> I have "user support" planned today (Paul asked for help as well), so I’m 
> completing 4.3.1 release and I will switch to "support" ;)
> 
> Regards
> JB
> 
>> Le 2 avr. 2021 à 04:08, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Hi JB,
>> 
>> I wonder if you have any ideas on how to resolve it? Is there any way I can 
>> provide a list of repositories explicitly?
>> 
>> Would really appreciate help on resolving this issue!
>> 
>> Best regards,
>> Oleg 
>> 
>> Sent from my iPhone
>> 
>>> On Mar 30, 2021, at 7:16 AM, Oleg Cohen >> <mailto:oleg.co...@assurebridge.com>> wrote:
>>> 
>>> Hi JB,
>>> 
>>> Here it is:
>>> 
>>> http://maven.apache.org/POM/4.0.0 
>>> <http://maven.apache.org/POM/4.0.0>"
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance 
>>> <http://www.w3.org/2001/XMLSchema-instance>"
>>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
>>> <http://maven.apache.org/POM/4.0.0> 
>>> http://maven.apache.org/xsd/maven-4.0.0.xsd 
>>> <http://maven.apache.org/xsd/maven-4.0.0.xsd>">
>>> 
>>> 4.0.0
>>> 
>>> acme
>>> test
>>> 
>>> 1.0.1-SNAPSHOT
>>> 
>>> karaf-assembly
>>> 
>>> 
>>> 4.3.0
>>> 1.7.30
>>> 
>>> 
>>> 
>>> 
>>> 
>>> org.apache.karaf.tooling
>>> karaf-maven-plugin
>>> true
>>> 
>>> 
>>> ${project.artifactId}
>>> 
>>> wrap
>>> bundle
>>> config
>>> system
>>> feature
>>> package
>>> log
>>> ssh
>>> instance
>>> shell
>>> management
>>> service
>>> jaas
>>> deployer
>>> diagnostic
>>> scr
>>> http
>>> war
>>> 
>>> 
>>> 
>>> 
>>> eventadmin
>>> 
>>> false
>>> false
>>> 
>>> ${project.build.directory}/assembly/karaf
>>> empower
>>> true
>>> 
>>> 
>>> 
>>> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
>>>   
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> org.eclipse.m2e
>>> 
>>> lifecycle-mapping
>>> 1.0.0
>>> 
&g

Re: Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

Hi JB,

I wonder if you have any ideas on how to resolve it? Is there any way I can
provide a list of repositories explicitly?

Would really appreciate help on resolving this issue!

Best regards,
Oleg

Sent from my iPhone

On Mar 30, 2021, at 7:16 AM, Oleg Cohen  wrote:

Hi JB,

Here it is:

http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0>"*
xmlns:xsi=*"http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>"*
xsi:schemaLocation=*"http://maven.apache.org/POM/4.0.0
<http://maven.apache.org/POM/4.0.0>
http://maven.apache.org/xsd/maven-4.0.0.xsd
<http://maven.apache.org/xsd/maven-4.0.0.xsd>"*>

4.0.0

acme
test

1.0.1-SNAPSHOT

karaf-assembly


4.3.0
1.7.30






org.apache.karaf.tooling
karaf-maven-plugin
true

${project.artifactId}

wrap
bundle
config
system
feature
package
log
ssh
instance
shell
management
service
jaas
deployer
diagnostic
scr
http
war




eventadmin

false
false
${project.build.directory}/assembly/karaf
empower
true



mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features










org.eclipse.m2e
lifecycle-mapping
1.0.0






org.apache.karaf.tooling


karaf-maven-plugin


[4.3.0,)


assembly


















org.apache.karaf.features
framework
${karaf.runtime.version}
kar




org.apache.karaf.features
framework
${karaf.runtime.version}
features
xml
runtime




org.apache.karaf.features
standard
${karaf.runtime.version}
features
xml




org.slf4j
slf4j-api
${slf4j.version}
provided



org.apache.camel.karaf
apache-camel
3.8.0
features
xml



io.hawt
hawtio-karaf
2.13.1
features
xml



org.ops4j.pax.cdi
pax-cdi-features
1.1.4
features
xml






Thank you!
Oleg

On Mar 30, 2021, at 12:12 AM, Jean-Baptiste Onofre  wrote:

Hi,

The range comes from as  in another feature I guess.

The warning is "normal" as Karaf plugin won’t scan all possible versions.
However, it should resolve a version.

What’s your pom xml ?

Regards
JB

Le 29 mars 2021 à 18:12, Oleg Cohen  a écrit :

Thank you! I was able to blacklist 1.0.0 as below, but [1,2) isn’t working
and I get this error: [WARNING] Matched URI can't use version ranges:
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features

Where is it coming from and how can I override the entry list?




mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features




On Mar 29, 2021, at 11:41 AM, Jean-Baptiste Onofre  wrote:

1.1.4 is the last and clean (it should ;) )

Regards
JB

Le 29 mars 2021 à 16:33, Oleg Cohen  a écrit :

Hi JB,

It is a proxy. I have the artifact there, but I think the error is that the
artifact is too old. Which one is the right one to use?

Thank you!
Oleg

On Mar 29, 2021, at 10:23 AM, Jean-Baptiste Onofre  wrote:

Hi Oleg,

It seems that it can’t
download mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features resolved
based on the range.

I guess your Nexus repository is a proxy right ?

Regards
JB

Le 29 mars 2021 à 15:49, Oleg Cohen  a écrit :

Greetings,

I am getting the following error when trying to build a custom distribution
for Karaf v4.3.0 pointing to my own Nexus 3 repository. This works when I
use Maven Central.

Not sure what is causing the issue. Below is the error message. Is there a
way to specify v1.1.3 or v1.1.4 of pax-cdi-features to be used?

Would appreciate help on resolving this issue!

Best,
Oleg



*[WARNING] Error resolving artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find
metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local
(/Users/ocohen/.m2/repository), Could not transfer metadata
org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus
(https://nexus3.assurebridge.com/content/groups/public
<https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat May
30 06:48:38 EDT 2020, Could not transfer metadata
org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus
(https://nexus3.assurebridge.com/content/groups/public/
<https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat
May 30 06:48:38 EDT 2020]java.io.IOException: Error resolving artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find
metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local
(/Users/ocohen/.m2/repository), Could not transfer metadata
org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus
(https://nexus3.assurebridge.com/content/groups/public
<https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat May
30 06:48:38 EDT 2020, Could not transfer metadata
org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus
(https://nexus3.assurebridge.com/content/groups/public/
<https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat
May 30 06:48:38 EDT 2020]*
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException
(AetherBas

Re: Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

ntime.version}
kar



org.apache.karaf.features
framework
${karaf.runtime.version}
features
xml
runtime



org.apache.karaf.features
standard
${karaf.runtime.version}
features
xml



org.slf4j
slf4j-api
${slf4j.version}
provided



org.apache.camel.karaf
apache-camel
3.8.0
features
xml



io.hawt
hawtio-karaf
2.13.1
features
xml



org.ops4j.pax.cdi
pax-cdi-features
1.1.4
features
xml





Thank you!
Oleg

> On Mar 30, 2021, at 12:12 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi,
> 
> The range comes from as  in another feature I guess.
> 
> The warning is "normal" as Karaf plugin won’t scan all possible versions.
> However, it should resolve a version.
> 
> What’s your pom xml ?
> 
> Regards
> JB
> 
>> Le 29 mars 2021 à 18:12, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Thank you! I was able to blacklist 1.0.0 as below, but [1,2) isn’t working 
>> and I get this error: [WARNING] Matched URI can't use version ranges: 
>> mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features
>> 
>> Where is it coming from and how can I override the entry list?
>> 
>> 
>> 
>>  
>>  
>> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
>>   
>>  
>> mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features
>>   
>>  
>> 
>> 
>> 
>>> On Mar 29, 2021, at 11:41 AM, Jean-Baptiste Onofre >> <mailto:j...@nanthrax.net>> wrote:
>>> 
>>> 1.1.4 is the last and clean (it should ;) )
>>> 
>>> Regards
>>> JB
>>> 
>>>> Le 29 mars 2021 à 16:33, Oleg Cohen >>> <mailto:oleg.co...@assurebridge.com>> a écrit :
>>>> 
>>>> Hi JB,
>>>> 
>>>> It is a proxy. I have the artifact there, but I think the error is that 
>>>> the artifact is too old. Which one is the right one to use?
>>>> 
>>>> Thank you!
>>>> Oleg
>>>> 
>>>>> On Mar 29, 2021, at 10:23 AM, Jean-Baptiste Onofre >>>> <mailto:j...@nanthrax.net>> wrote:
>>>>> 
>>>>> Hi Oleg,
>>>>> 
>>>>> It seems that it can’t download 
>>>>> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features resolved based 
>>>>> on the range.
>>>>> 
>>>>> I guess your Nexus repository is a proxy right ?
>>>>> 
>>>>> Regards
>>>>> JB
>>>>> 
>>>>>> Le 29 mars 2021 à 15:49, Oleg Cohen >>>>> <mailto:oleg.co...@assurebridge.com>> a écrit :
>>>>>> 
>>>>>> Greetings,
>>>>>> 
>>>>>> I am getting the following error when trying to build a custom 
>>>>>> distribution for Karaf v4.3.0 pointing to my own Nexus 3 repository. 
>>>>>> This works when I use Maven Central.
>>>>>> 
>>>>>> Not sure what is causing the issue. Below is the error message. Is there 
>>>>>> a way to specify v1.1.3 or v1.1.4 of pax-cdi-features to be used?
>>>>>> 
>>>>>> Would appreciate help on resolving this issue!
>>>>>> 
>>>>>> Best,
>>>>>> Oleg
>>>>>> 
>>>>>> 
>>>>>> [WARNING] Error resolving artifact 
>>>>>> org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find 
>

Re: Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

Thank you! I was able to blacklist 1.0.0 as below, but [1,2) isn’t working and 
I get this error: [WARNING] Matched URI can't use version ranges: 
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features

Where is it coming from and how can I override the entry list?





mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
  

mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features
  




> On Mar 29, 2021, at 11:41 AM, Jean-Baptiste Onofre  wrote:
> 
> 1.1.4 is the last and clean (it should ;) )
> 
> Regards
> JB
> 
>> Le 29 mars 2021 à 16:33, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Hi JB,
>> 
>> It is a proxy. I have the artifact there, but I think the error is that the 
>> artifact is too old. Which one is the right one to use?
>> 
>> Thank you!
>> Oleg
>> 
>>> On Mar 29, 2021, at 10:23 AM, Jean-Baptiste Onofre >> <mailto:j...@nanthrax.net>> wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> It seems that it can’t download 
>>> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features resolved based on 
>>> the range.
>>> 
>>> I guess your Nexus repository is a proxy right ?
>>> 
>>> Regards
>>> JB
>>> 
>>>> Le 29 mars 2021 à 15:49, Oleg Cohen >>> <mailto:oleg.co...@assurebridge.com>> a écrit :
>>>> 
>>>> Greetings,
>>>> 
>>>> I am getting the following error when trying to build a custom 
>>>> distribution for Karaf v4.3.0 pointing to my own Nexus 3 repository. This 
>>>> works when I use Maven Central.
>>>> 
>>>> Not sure what is causing the issue. Below is the error message. Is there a 
>>>> way to specify v1.1.3 or v1.1.4 of pax-cdi-features to be used?
>>>> 
>>>> Would appreciate help on resolving this issue!
>>>> 
>>>> Best,
>>>> Oleg
>>>> 
>>>> 
>>>> [WARNING] Error resolving artifact 
>>>> org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find 
>>>> metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local 
>>>> (/Users/ocohen/.m2/repository), Could not transfer metadata 
>>>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>>>> (https://nexus3.assurebridge.com/content/groups/public 
>>>> <https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat 
>>>> May 30 06:48:38 EDT 2020, Could not transfer metadata 
>>>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>>>> (https://nexus3.assurebridge.com/content/groups/public/ 
>>>> <https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat 
>>>> May 30 06:48:38 EDT 2020]
>>>> java.io.IOException: Error resolving artifact 
>>>> org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find 
>>>> metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local 
>>>> (/Users/ocohen/.m2/repository), Could not transfer metadata 
>>>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>>>> (https://nexus3.assurebridge.com/content/groups/public 
>>>> <https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat 
>>>> May 30 06:48:38 EDT 2020, Could not transfer metadata 
>>>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>>>> (https://nexus3.assurebridge.com/content/groups/public/ 
>>>> <https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat 
>>>> May 30 06:48:38 EDT 2020]
>>>> at 
>>>> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException 
>>>> (AetherBasedResolver.java:803)
>>>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>>>> (AetherBasedResolver.java:780)
>>>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>>>> (AetherBasedResolver.java:657)
>>>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>>>> (AetherBasedResolver.java:598)
>>>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>>>> (AetherBasedResolver.java:565)
>>>> at org.apache.karaf.tooling.u

Re: Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

Hi JB,

It is a proxy. I have the artifact there, but I think the error is that the 
artifact is too old. Which one is the right one to use?

Thank you!
Oleg

> On Mar 29, 2021, at 10:23 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> It seems that it can’t download 
> mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features resolved based on 
> the range.
> 
> I guess your Nexus repository is a proxy right ?
> 
> Regards
> JB
> 
>> Le 29 mars 2021 à 15:49, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> I am getting the following error when trying to build a custom distribution 
>> for Karaf v4.3.0 pointing to my own Nexus 3 repository. This works when I 
>> use Maven Central.
>> 
>> Not sure what is causing the issue. Below is the error message. Is there a 
>> way to specify v1.1.3 or v1.1.4 of pax-cdi-features to be used?
>> 
>> Would appreciate help on resolving this issue!
>> 
>> Best,
>> Oleg
>> 
>> 
>> [WARNING] Error resolving artifact 
>> org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find 
>> metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local 
>> (/Users/ocohen/.m2/repository), Could not transfer metadata 
>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>> (https://nexus3.assurebridge.com/content/groups/public 
>> <https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat May 
>> 30 06:48:38 EDT 2020, Could not transfer metadata 
>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>> (https://nexus3.assurebridge.com/content/groups/public/ 
>> <https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat May 
>> 30 06:48:38 EDT 2020]
>> java.io.IOException: Error resolving artifact 
>> org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2): [Could not find 
>> metadata org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml in local 
>> (/Users/ocohen/.m2/repository), Could not transfer metadata 
>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>> (https://nexus3.assurebridge.com/content/groups/public 
>> <https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat May 
>> 30 06:48:38 EDT 2020, Could not transfer metadata 
>> org.ops4j.pax.cdi:pax-cdi-features/maven-metadata.xml from/to nexus 
>> (https://nexus3.assurebridge.com/content/groups/public/ 
>> <https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat May 
>> 30 06:48:38 EDT 2020]
>> at 
>> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException 
>> (AetherBasedResolver.java:803)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:780)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:657)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:598)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:565)
>> at org.apache.karaf.tooling.utils.ReactorMavenResolver.resolve 
>> (ReactorMavenResolver.java:63)
>> at 
>> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download 
>> (MavenDownloadTask.java:49)
>> at 
>> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run
>>  (AbstractRetryableDownloadTask.java:60)
>> at java.util.concurrent.Executors$RunnableAdapter.call 
>> (Executors.java:515)
>> at java.util.concurrent.FutureTask.run (FutureTask.java:264)
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run 
>> (ScheduledThreadPoolExecutor.java:304)
>> 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:834)
>> Caused by: 
>> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: Error 
>> resolving artifact org.ops4j.pax.cdi:pax-cdi-features:xml:features:[1,2)
>> at 
>> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange 
>> (AetherBasedResolver.java:1068)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:765)
>> at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve 
>> (AetherBasedResolver.java:657)
>> 

Issue with building custom 4.3.0 distribution against my own Nexus 3

[Oleg Cohen]

0, Could not transfer artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:1.0.0 from/to nexus
(https://nexus3.assurebridge.com/content/groups/public/
<https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat
May 30 06:48:38 EDT 2020]java.io.IOException: Error resolving artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:1.0.0: [Could not transfer
artifact org.ops4j.pax.cdi:pax-cdi-features:xml:features:1.0.0 from/to
nexus (https://nexus3.assurebridge.com/content/groups/public
<https://nexus3.assurebridge.com/content/groups/public>): NotAfter: Sat May
30 06:48:38 EDT 2020, Could not transfer artifact
org.ops4j.pax.cdi:pax-cdi-features:xml:features:1.0.0 from/to nexus
(https://nexus3.assurebridge.com/content/groups/public/
<https://nexus3.assurebridge.com/content/groups/public/>): NotAfter: Sat
May 30 06:48:38 EDT 2020]*
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException
(AetherBasedResolver.java:803)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:774)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:657)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:598)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:565)
at org.apache.karaf.tooling.utils.ReactorMavenResolver.resolve
(ReactorMavenResolver.java:63)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download
(MavenDownloadTask.java:49)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run
(AbstractRetryableDownloadTask.java:60)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run
(ScheduledThreadPoolExecutor.java:304)
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:834)
Caused by:
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Error
resolving artifact org.ops4j.pax.cdi:pax-cdi-features:xml:features:1.0.0
at
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve
(DefaultArtifactResolver.java:413)
at
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts
(DefaultArtifactResolver.java:215)
at
shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact
(DefaultArtifactResolver.java:192)
at
shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact
(DefaultRepositorySystem.java:247)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:767)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:657)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:598)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve
(AetherBasedResolver.java:565)
at org.apache.karaf.tooling.utils.ReactorMavenResolver.resolve
(ReactorMavenResolver.java:63)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download
(MavenDownloadTask.java:49)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run
(AbstractRetryableDownloadTask.java:60)
at java.util.concurrent.Executors$RunnableAdapter.call
(Executors.java:515)
at java.util.concurrent.FutureTask.run (FutureTask.java:264)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run
(ScheduledThreadPoolExecutor.java:304)
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:834)




*[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.3.0:assembly
(default-assembly) on project clearvault: Unable to build assembly:
Error:[ERROR] Error downloading
mvn:org.ops4j.pax.cdi/pax-cdi-features/[1,2)/xml/features[ERROR] Error
downloading mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features*


*-- *
*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 <http://www.assurebridge.com>*

Re: Error installing a feature

[Oleg Cohen]

Hi JB,

Thank you for the info. It seems to be the order of doing installs. Let me try 
to come up with a small generic example and send you the info.

Best,
Oleg

> On Mar 9, 2021, at 4:55 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> It seems you have the same as 
> https://issues.apache.org/jira/browse/KARAF-6916 
> <https://issues.apache.org/jira/browse/KARAF-6916>
> 
> So, I guess you also have a refresh, right ?
> 
> I never saw such issue, but if you can produce a test case to reproduce it, I 
> will investigate.
> 
> Thanks,
> Regards
> JB
> 
>> Le 9 mars 2021 à 10:49, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> When installing a feature I am getting the following exception, which seems 
>> pretty fundamental:
>> 
>> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
>> missing requirement [root] osgi.identity; osgi.identity=bundle; 
>> type=karaf.feature; version="[4.3.0,4.3.0]"; 
>> filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
>>  [caused by: Unable to resolve bundle/4.3.0: missing requirement 
>> [bundle/4.3.0] osgi.identity; osgi.identity=org.apache.karaf.bundle.core; 
>> type=osgi.bundle; version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: 
>> Unable to resolve org.apache.karaf.bundle.core/4.3.0: missing requirement 
>> [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=javax.management)"]]
>>  at 
>> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
>>  at 
>> org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:434)
>>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:421)
>>  at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
>>  at 
>> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
>>  at 
>> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:392)
>>  at 
>> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
>>  at 
>> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
>>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>>  at 
>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
>>  at 
>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
>>  at java.base/java.lang.Thread.run(Thread.java:832)
>> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to 
>> resolve bundle/4.3.0: missing requirement [bundle/4.3.0] osgi.identity; 
>> osgi.identity=org.apache.karaf.bundle.core; type=osgi.bundle; 
>> version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: Unable to resolve 
>> org.apache.karaf.bundle.core/4.3.0: missing requirement 
>> [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=javax.management)"]
>>  at 
>> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
>>  ... 12 more
>> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to 
>> resolve org.apache.karaf.bundle.core/4.3.0: missing requirement 
>> [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=javax.management)"
>>  at 
>> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
>>  ... 13 more
>> Error executing command: Unable to resolve root: missing requirement [root] 
>> osgi.identity; osgi.identity=bundle; type=karaf.feature; 
>> version="[4.3.0,4.3.0]"; 
>> filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
>>  [caused by: Unable to resolve bundle/4.3.0: missing requirement 
>> [bundle/4.3.0] osgi.identity; osgi.identity=org.apache.karaf.bundle.core; 
>> type=osgi.bundle; version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: 
>> Unable to resolve org.apache.karaf.bundle.core/4.3.0: missing requirement 
>> [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=javax.management)”]]
>> 
>> 
>> I did check that the javax.management pa

Error installing a feature

[Oleg Cohen]

Greetings,

When installing a feature I am getting the following exception, which seems 
pretty fundamental:

org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: 
missing requirement [root] osgi.identity; osgi.identity=bundle; 
type=karaf.feature; version="[4.3.0,4.3.0]"; 
filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
 [caused by: Unable to resolve bundle/4.3.0: missing requirement [bundle/4.3.0] 
osgi.identity; osgi.identity=org.apache.karaf.bundle.core; type=osgi.bundle; 
version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.karaf.bundle.core/4.3.0: missing requirement 
[org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
filter:="(osgi.wiring.package=javax.management)"]]
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
at 
org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:434)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:421)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
at 
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
at 
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:392)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
bundle/4.3.0: missing requirement [bundle/4.3.0] osgi.identity; 
osgi.identity=org.apache.karaf.bundle.core; type=osgi.bundle; 
version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.karaf.bundle.core/4.3.0: missing requirement 
[org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
filter:="(osgi.wiring.package=javax.management)"]
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
org.apache.karaf.bundle.core/4.3.0: missing requirement 
[org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
filter:="(osgi.wiring.package=javax.management)"
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 13 more
Error executing command: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=bundle; type=karaf.feature; 
version="[4.3.0,4.3.0]"; 
filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
 [caused by: Unable to resolve bundle/4.3.0: missing requirement [bundle/4.3.0] 
osgi.identity; osgi.identity=org.apache.karaf.bundle.core; type=osgi.bundle; 
version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.karaf.bundle.core/4.3.0: missing requirement 
[org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
filter:="(osgi.wiring.package=javax.management)”]]


I did check that the javax.management package is available:

karaf@root()> package:exports | grep javax.management
javax.management.loading
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.modelmbean 
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.monitor
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.openmbean  
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.relation   
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.remote.rmi 
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.remote 
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management.timer  
   | 0.0.0  | 0   | org.apache.felix.framework
javax.management

Re: feature:install hangs, how to troubleshoot??

[Oleg Cohen]

I did’t change any logging levels. How do I set the features service logging to 
DEBUG?

Thank you!
Oleg

> On Mar 3, 2021, at 11:44 PM, Jean-Baptiste Onofre  wrote:
> 
> Nothing is the log as well setting features service in DEBUG ?
> 
> Regards
> JB
> 
>> Le 3 mars 2021 à 19:04, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Hi JB,
>> 
>> Ran with -t -v and the behavior was the same. Feels like some kind of 
>> infinite loop, but all was very quiet.
>> 
>> Thank you,
>> Oleg
>> 
>>> On Mar 3, 2021, at 12:05 AM, Jean-Baptiste Onofre >> <mailto:j...@nanthrax.net>> wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> Did you try feature:install -t -v (to do a "simulate") ?
>>> 
>>> You might have message from the resolver in the log.
>>> 
>>> Regards
>>> JB
>>> 
>>>> Le 2 mars 2021 à 20:30, Oleg Cohen >>> <mailto:oleg.co...@assurebridge.com>> a écrit :
>>>> 
>>>> Greetings,
>>>> 
>>>> I am using version 4.3.0. I have a top-level feature that depends on other 
>>>> features.
>>>> 
>>>> When I run feature:install -r -v FEATURE, it sits there for a long while 
>>>> and then blows up with an OutOfMemory exception. Is there any way to get 
>>>> logging for what is taking place? Would appreciate any idea on how to 
>>>> troubleshoot the issue.
>>>> 
>>>> 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 <mailto:oleg.co...@assurebridge.com>  | 
>>>>  www.assurebridge.com <http://www.assurebridge.com/>
>> 
> 

Re: Strange error when re-installing a feature on 4.3.0

[Oleg Cohen]

Hi JB,

Yes, just doing install for the previously and successfully installed feature. 
I think before the behavior was to perform an update/upgrade.

Thank you!
Oleg

> On Mar 3, 2021, at 12:09 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> Does it mean you do feature:install while the feature is already installed ? 
> So, you might have some refresh happening.
> 
> It remembers me a Jira we have (related to Felix Framework) about the 
> "system/JDK" packages (let me looking for the Jira).
> 
> Regards
> JB
> 
>> Le 3 mars 2021 à 01:05, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> I am getting the following error when I run feature:install for the feature 
>> that was previously installed. It also happens when I run install on a 
>> feature that lists the previously installed feature as its dependency.
>> 
>> Error executing command: Unable to resolve root: missing requirement [root] 
>> osgi.identity; osgi.identity=bundle; type=karaf.feature; 
>> version="[4.3.0,4.3.0]"; 
>> filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
>>  [caused by: Unable to resolve bundle/4.3.0: missing requirement 
>> [bundle/4.3.0] osgi.identity; osgi.identity=org.apache.karaf.bundle.core; 
>> type=osgi.bundle; version="[4.3.0,4.3.0]"; resolution:=mandatory [caused by: 
>> Unable to resolve org.apache.karaf.bundle.core/4.3.0: missing requirement 
>> [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=javax.management)"]]
>> 
>> 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 <mailto:oleg.co...@assurebridge.com>  |  
>> www.assurebridge.com <http://www.assurebridge.com/>

Re: feature:install hangs, how to troubleshoot??

[Oleg Cohen]

Hi JB,

Ran with -t -v and the behavior was the same. Feels like some kind of infinite 
loop, but all was very quiet.

Thank you,
Oleg

> On Mar 3, 2021, at 12:05 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> Did you try feature:install -t -v (to do a "simulate") ?
> 
> You might have message from the resolver in the log.
> 
> Regards
> JB
> 
>> Le 2 mars 2021 à 20:30, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> I am using version 4.3.0. I have a top-level feature that depends on other 
>> features.
>> 
>> When I run feature:install -r -v FEATURE, it sits there for a long while and 
>> then blows up with an OutOfMemory exception. Is there any way to get logging 
>> for what is taking place? Would appreciate any idea on how to troubleshoot 
>> the issue.
>> 
>> 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 <mailto:oleg.co...@assurebridge.com>  |  
>> www.assurebridge.com <http://www.assurebridge.com/>

Strange error when re-installing a feature on 4.3.0

[Oleg Cohen]

Greetings,

I am getting the following error when I run feature:install for the feature
that was previously installed. It also happens when I run install on a
feature that lists the previously installed feature as its dependency.

Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=bundle; type=karaf.feature;
version="[4.3.0,4.3.0]";
filter:="(&(osgi.identity=bundle)(type=karaf.feature)(version>=4.3.0)(version<=4.3.0))"
[caused by: Unable to resolve bundle/4.3.0: missing requirement
[bundle/4.3.0] osgi.identity; osgi.identity=org.apache.karaf.bundle.core;
type=osgi.bundle; version="[4.3.0,4.3.0]"; resolution:=mandatory [caused
by: Unable to resolve org.apache.karaf.bundle.core/4.3.0: missing
requirement [org.apache.karaf.bundle.core/4.3.0] osgi.wiring.package;
filter:="(osgi.wiring.package=javax.management)"]]

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 <http://www.assurebridge.com>*

feature:install hangs, how to troubleshoot??

[Oleg Cohen]

Greetings,

I am using version 4.3.0. I have a top-level feature that depends on other
features.

When I run feature:install -r -v FEATURE, it sits there for a long while
and then blows up with an OutOfMemory exception. Is there any way to get
logging for what is taking place? Would appreciate any idea on how to
troubleshoot the issue.

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 <http://www.assurebridge.com>*

Re: Configuring MDC logging karaf 4 camel 3.7.0

[Oleg Cohen]

Thank you, JB!

Is it possible now? If yes, is there an example.

Best,
Oleg

> On Jan 22, 2021, at 9:01 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> The file name ${ctx:camel.contextId}.log is "normal" as it’s created before 
> the first camel context is created.
> 
> We can set additivity false or exclude "no context" in the sift appender.
> 
> Regards
> JB
> 
>> Le 22 janv. 2021 à 14:54, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Hi JB,
>> 
>> I am also interested in this functionality and I have tried the same on a 
>> Mac. All worked good for me, but I see a file created 
>> camel-context-${ctx:camel.contextId}.log in the data/log folder that 
>> contains the entire duplicate log. Same as karaf.log. Have you observed the 
>> same?
>> 
>> Than you,
>> Oleg
>> 
>> On Fri, Jan 22, 2021 at 12:09 AM Jean-Baptiste Onofre > <mailto:j...@nanthrax.net>> wrote:
>> Hi Michael,
>> 
>> I’ve resumed my test about Camel MDC.
>> 
>> So, I created a simple route like this:
>> 
>> 
>> http://www.osgi.org/xmlns/blueprint/v1.0.0 
>> <http://www.osgi.org/xmlns/blueprint/v1.0.0>">
>> 
>>   http://camel.apache.org/schema/blueprint 
>> <http://camel.apache.org/schema/blueprint>" useMDCLogging="true">
>> 
>>   
>>   Hello World
>>   
>> 
>>   
>> 
>> 
>> 
>> Then, in etc/org.ops4j.pax.logging.cfg, I added:
>> 
>> log4j2.rootLogger.appenderRef.Sift.ref = Routing
>> 
>> …
>> 
>> log4j2.appender.routing.type = Routing
>> log4j2.appender.routing.name <http://log4j2.appender.routing.name/> = Routing
>> log4j2.appender.routing.routes.type = Routes
>> log4j2.appender.routing.routes.pattern = \$\$\\\{ctx:bundle.name 
>> <http://bundle.name/>\}
>> log4j2.appender.routing.routes.bundle.type = Route
>> log4j2.appender.routing.routes.bundle.appender.type = RollingRandomAccessFile
>> log4j2.appender.routing.routes.bundle.appender.name 
>> <http://log4j2.appender.routing.routes.bundle.appender.name/> = 
>> Bundle-\$\\\{ctx:bundle.name <http://bundle.name/>\}
>> log4j2.appender.routing.routes.bundle.appender.fileName = 
>> ${karaf.log}/camel-context-\$\\\{ctx:camel.contextId\}.log
>> log4j2.appender.routing.routes.bundle.appender.filePattern = 
>> ${karaf.log}/bundle-\$\\\{ctx:bundle.name <http://bundle.name/>\}.log.%i
>> log4j2.appender.routing.routes.bundle.appender.append = true
>> log4j2.appender.routing.routes.bundle.appender.layout.type = PatternLayout
>> log4j2.appender.routing.routes.bundle.appender.layout.pattern = 
>> ${log4j2.pattern}
>> log4j2.appender.routing.routes.bundle.appender.policies.type = Policies
>> log4j2.appender.routing.routes.bundle.appender.policies.size.type = 
>> SizeBasedTriggeringPolicy
>> log4j2.appender.routing.routes.bundle.appender.policies.size.size = 8MB
>> 
>> You can see the fileName containing camel.contextId.
>> 
>> In data/log, I can see the log file created for my Camel Context: 
>> camel-context-camel-1.log containing:
>> 
>> 2021-01-22T06:07:28,801 | INFO  | Blueprint Event Dispatcher: 1 | 
>> JmxManagementStrategy| 88 - org.apache.camel.camel-management - 
>> 3.7.0 | JMX is enabled
>> 2021-01-22T06:07:28,890 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Apache Camel 3.7.0 (camel-1) is starting
>> 2021-01-22T06:07:28,892 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | MDC logging is enabled on CamelContext: camel-1
>> 2021-01-22T06:07:28,968 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | StreamCaching is not in use. If using streams then it's recommended 
>> to enable stream caching. See more details at 
>> http://camel.apache.org/stream-caching.html 
>> <http://camel.apache.org/stream-caching.html>
>> 2021-01-22T06:07:28,998 | INFO  | Blueprint Event Dispatcher: 1 | 
>> InternalRouteStartupManager  | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 | Route: test started and consuming from: timer://fire <>
>> 2021-01-22T06:07:29,003 | INFO  | Blueprint Event Dispatcher: 1 | 
>> AbstractCamelContext | 65 - org.apache.camel.camel-base-engine - 
>> 3.7.0 |

Re: Configuring MDC logging karaf 4 camel 3.7.0

[Oleg Cohen]

ssFileManager$RollingRandomAccessFileManagerFactory@26d9daed]
> unable to create manager for
> [D:\karaf\apache-karaf-4.3.0\data/log/sift-camel-${ctx:camel.contextId}.log]
> with data
> [org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager$FactoryData@34bd66be
> ]
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to invoke
> factory method in class
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender for
> element RollingRandomAccessFile: java.lang.IllegalStateException: No
> factory method found for class
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to create
> Appender of type RollingRandomAccessFile
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Cannot access
> RandomAccessFile java.io.IOException: La syntaxe du nom de fichier, de
> répertoire ou de volume est incorrecte
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Could not create
> plugin of type class
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender for
> element RollingRandomAccessFile: java.lang.IllegalStateException:
> ManagerFactory
> [org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager$RollingRandomAccessFileManagerFactory@26d9daed]
> unable to create manager for
> [D:\karaf\apache-karaf-4.3.0\data/log/sift-camel-${ctx:camel.contextId}.log]
> with data
> [org.apache.logging.log4j.core.appender.rolling.RollingRandomAccessFileManager$FactoryData@19f28b4
> ]
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to invoke
> factory method in class
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender for
> element RollingRandomAccessFile: java.lang.IllegalStateException: No
> factory method found for class
> org.apache.logging.log4j.core.appender.RollingRandomAccessFileAppender
> org.ops4j.pax.logging.pax-logging-log4j2 [log4j2] ERROR : Unable to create
> Appender of type RollingRandomAccessFile
>
> There is updated documentation about how to configure ?
>
> Michael.
>
>
>

-- 
*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 <http://www.assurebridge.com>*

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: 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 ]

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 <http://www.assurebridge.com>*

Re: Camel 3.7.0 and Karaf 4.3.0

[Oleg Cohen]

Thank you, JB, it is great!

When is 4.3.1 targeted for?

Best,
Oleg

On Tue, Dec 29, 2020 at 9:52 AM Jean-Baptiste Onofre 
wrote:

> Hi Oleg,
>
> Thanks and it confirms what I said in my previous email:
> - for camel-jetty, missing jetty feature, fixed in Karaf 4.3.1
> - for camel-paxlogging, import range should be extended (I will fix that
> in Camel Karaf).
>
> Regards
> JB
>
> Le 29 déc. 2020 à 10:36, Oleg Cohen  a écrit
> :
>
> Thank you for looking into these, JB!
>
> Yes, below are the errors I got when trying to install these two features.
>
> Best regards,
> Oleg
>
> karaf@root()> feature:install camel-jetty
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jetty;
> type=karaf.feature; version="[3.7.0,3.7.0]";
> filter:="(&(osgi.identity=camel-jetty)(type=karaf.feature)(version>=3.7.0)(version<=3.7.0))"
> [caused by: Unable to resolve camel-jetty/3.7.0: missing requirement
> [camel-jetty/3.7.0] osgi.identity; osgi.identity=jetty; type=karaf.feature]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:434)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:421)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:392)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
> resolve camel-jetty/3.7.0: missing requirement [camel-jetty/3.7.0]
> osgi.identity; osgi.identity=jetty; type=karaf.feature
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
> ... 12 more
> *Error executing command: Unable to resolve root: missing requirement
> [root] osgi.identity; osgi.identity=camel-jetty; type=karaf.feature;
> version="[3.7.0,3.7.0]";
> filter:="(&(osgi.identity=camel-jetty)(type=karaf.feature)(version>=3.7.0)(version<=3.7.0))"
> [caused by: Unable to resolve camel-jetty/3.7.0: missing requirement
> [camel-jetty/3.7.0] osgi.identity; osgi.identity=jetty; type=karaf.feature]*
>
>
> and
>
> karaf@root()> feature:install camel-paxlogging
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-paxlogging;
> type=karaf.feature; version="[3.7.0,3.7.0]";
> filter:="(&(osgi.identity=camel-paxlogging)(type=karaf.feature)(version>=3.7.0)(version<=3.7.0))"
> [caused by: Unable to resolve camel-paxlogging/3.7.0: missing requirement
> [camel-paxlogging/3.7.0] osgi.identity;
> osgi.identity=org.apache.camel.karaf.camel-paxlogging; type=osgi.bundle;
> version="[3.7.0,3.7.0]"; resolution:=mandatory [caused by: Unable to
> resolve org.apache.camel.karaf.camel-paxlogging/3.7.0: missing requirement
> [org.apache.camel.karaf.camel-paxlogging/3.7.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:434)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:421)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:375)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:392)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/j

Re: Camel 3.7.0 and Karaf 4.3.0

[Oleg Cohen]

irement [org.apache.camel.karaf.camel-paxlogging/3.7.0] 
osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"]
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to resolve 
org.apache.camel.karaf.camel-paxlogging/3.7.0: missing requirement 
[org.apache.camel.karaf.camel-paxlogging/3.7.0] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"
at 
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 13 more
Error executing command: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=camel-paxlogging; type=karaf.feature; 
version="[3.7.0,3.7.0]"; 
filter:="(&(osgi.identity=camel-paxlogging)(type=karaf.feature)(version>=3.7.0)(version<=3.7.0))"
 [caused by: Unable to resolve camel-paxlogging/3.7.0: missing requirement 
[camel-paxlogging/3.7.0] osgi.identity; 
osgi.identity=org.apache.camel.karaf.camel-paxlogging; type=osgi.bundle; 
version="[3.7.0,3.7.0]"; resolution:=mandatory [caused by: Unable to resolve 
org.apache.camel.karaf.camel-paxlogging/3.7.0: missing requirement 
[org.apache.camel.karaf.camel-paxlogging/3.7.0] osgi.wiring.package; 
filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"]]



> On Dec 29, 2020, at 1:01 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> Do you have the error ?
> 
> For camel-jetty, I think it’s related to the jetty feature (it should be 
> fixed with Karaf 4.3.1): jetty feature was removed to use pax-jetty, but 
> Camel still reference jetty. For transition purpose, I added a jetty "meta" 
> in coming Karaf 4.3.1.
> 
> For camel-paxlogging, I’m suspecting the import range: camel-paxlogging 
> reference paxlogging 1.11.2, with import range like [1,2). Whereas Karaf 
> 4.3.x uses pax logging 2.x. So, at least camel-paxlogging should extend the 
> range to [1,3) to work. I will create the Jira and do this change.
> 
> Regards
> JB
> 
>> Le 28 déc. 2020 à 16:44, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> Happy Holidays!
>> 
>> I have a question. I just migrated to Karaf 4.3.0 and Camel 3.7.0. It went 
>> well, however, I had to remove two features that I previously had installed:
>> 
>> camel-jetty
>> camel-paxlogging
>> 
>> There were a number of errors/dependency issues and I simply ended up 
>> removing these two. 
>> 
>> I am wondering what those were for and what, if any, capabilities have I 
>> lost.
>> 
>> Would appreciate any insight!
>> 
>> Cheers,
>> 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 <mailto:oleg.co...@assurebridge.com>  |  
>> www.assurebridge.com <http://www.assurebridge.com/>

Camel 3.7.0 and Karaf 4.3.0

[Oleg Cohen]

Greetings,

Happy Holidays!

I have a question. I just migrated to Karaf 4.3.0 and Camel 3.7.0. It went
well, however, I had to remove two features that I previously had installed:

*camel-jetty*
*camel-paxlogging*

There were a number of errors/dependency issues and I simply ended up
removing these two.

I am wondering what those were for and what, if any, capabilities have I
lost.

Would appreciate any insight!

Cheers,
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 <http://www.assurebridge.com>*

Re: Happy Christmas

[Oleg Cohen]

Merry Christmas and Happy New Year to all!!!

> On Dec 24, 2020, at 12:28 PM, Jean-Baptiste Onofre  wrote:
>
> Hi Karafers,
>
> On behalf of the Karaf team, I wish you a very happy Christmas.
>
> I think we all deserve good time with friends and family (obviously in 
> respect of Covid related directives).
>
> I will send a longer email during the week end with a Karaf gift and a 
> summary of this past year for Karaf community ;)
>
> So, again, have great time and happy Christmas.
>
> Regards
> JB

Re: [X-Mas Gift] Panel discussion about Karaf 5

[Oleg Cohen]

Hi JB,

Great news! This is awesome. I would love to join.

Best regards,
Oleg

Sent from my iPhone

> On Dec 15, 2020, at 12:32 PM, Jean-Baptiste Onofre  wrote:
>
> Hi guys,
>
> Maybe some of you know that I started to work on Karaf 5.
>
> I have something that it’s almost "usable".
>
> Before sending a global discussion thread on the mailing list, I would like 
> to evaluate the ideas & big changes I did.
>
> I would like to know if some of you would be interested by a panel discussion 
> call to introduce Karaf 5 (limited audience at first step).
>
> The agenda of this call would be:
> 1. Pros/Cons about Karaf as it is today
> 2. Concepts in Karaf 5 (module, extension, …)
> 3. Building & running
> 4. Live demo
>
> It could be recorded/webinar style (not necessary live call) for about 20 
> people at first step (both Karaf developers and users).
> The purpose is to evaluate the direction.
>
> Thoughts ?
> Who would be interested ?
>
> Thanks,
> Regards
> JB

Issues with installing camel-jetty and camel-paxlogging features on 4.3.0

[Oleg Cohen]

;=1.11.0)(!(version>=2.0.0)))"]
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 12 more
Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to
resolve org.apache.camel.karaf.camel-paxlogging/3.6.0: missing requirement
[org.apache.camel.karaf.camel-paxlogging/3.6.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"
at
org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1341)
... 13 more
Error executing command: Unable to resolve root: missing requirement [root]
osgi.identity; osgi.identity=camel-paxlogging; type=karaf.feature;
version="[3.6.0,3.6.0]";
filter:="(&(osgi.identity=camel-paxlogging)(type=karaf.feature)(version>=3.6.0)(version<=3.6.0))"
[caused by: Unable to resolve camel-paxlogging/3.6.0: missing requirement
[camel-paxlogging/3.6.0] osgi.identity;
osgi.identity=org.apache.camel.karaf.camel-paxlogging; type=osgi.bundle;
version="[3.6.0,3.6.0]"; resolution:=mandatory [caused by: Unable to
resolve org.apache.camel.karaf.camel-paxlogging/3.6.0: missing requirement
[org.apache.camel.karaf.camel-paxlogging/3.6.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=org.ops4j.pax.logging.spi)(version>=1.11.0)(!(version>=2.0.0)))"]]

Wondering if anybody else ran into the same issues and if there are any
workarounds?

There are a number of other camel features that installed with no problems.

Here is my full list:

camel-core

camel-blueprint

camel-stream

camel-mail

camel-servlet

camel-jackson

camel-jacksonxml

camel-jaxb

camel-rest-openapi

camel-rest-swagger

*camel-jetty*

camel-quartz

*camel-paxlogging*

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 <http://www.assurebridge.com>*

Re: org.apache.karaf.features.xml and repo blacklisting in 4.3.0

[Oleg Cohen]

Never mind :-) 

Sorry, it is working.

Thank you again!

> On Oct 31, 2020, at 6:41 AM, Oleg Cohen  wrote:
> 
> Hi JB,
> 
> Thank you for clarifying! 
> 
> I added the file, but the blacklisting isn’t kicking in. I still see the 
> repos in the list.
> 
> Regards,
> Oleg
> 
>> On Oct 31, 2020, at 6:40 AM, Jean-Baptiste Onofré > <mailto:j...@nanthrax.net>> wrote:
>> 
>> Hi
>> 
>> You can add the file yourself. The reason of the presence in 4.2.x is to 
>> avoid to get features from 4.3 in 4.2. 
>> 
>> Regards 
>> JB
>> 
>> Le sam. 31 oct. 2020 ? 11:36, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a ?crit :
>> Greetings, 
>> 
>> I am trying the new 4.3.0. 
>> 
>> I noticed that org.apache.karaf.features.xml file is not in the 
>> distribution. When I added one I had in 4.2.10, blacklisting is not going in 
>> effect. 
>> 
>> Is there perhaps a new mechanism for managing blacklisting of repos? 
>> 
>> Thank you! 
>> Oleg
> 

Re: org.apache.karaf.features.xml and repo blacklisting in 4.3.0

[Oleg Cohen]

Hi JB,

Thank you for clarifying! 

I added the file, but the blacklisting isn’t kicking in. I still see the repos 
in the list.

Regards,
Oleg

> On Oct 31, 2020, at 6:40 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi
> 
> You can add the file yourself. The reason of the presence in 4.2.x is to 
> avoid to get features from 4.3 in 4.2. 
> 
> Regards 
> JB
> 
> Le sam. 31 oct. 2020 ? 11:36, Oleg Cohen  a 
> ?crit :
> Greetings, 
> 
> I am trying the new 4.3.0. 
> 
> I noticed that org.apache.karaf.features.xml file is not in the distribution. 
> When I added one I had in 4.2.10, blacklisting is not going in effect. 
> 
> Is there perhaps a new mechanism for managing blacklisting of repos? 
> 
> Thank you! 
> Oleg

org.apache.karaf.features.xml and repo blacklisting in 4.3.0

[Oleg Cohen]

Greetings,

I am trying the new 4.3.0.

I noticed that org.apache.karaf.features.xml file is not in the distribution. 
When I added one I had in 4.2.10, blacklisting is not going in effect.

Is there perhaps a new mechanism for managing blacklisting of repos?

Thank you!
Oleg

Re: Issue running v4.2.10 with JDK 14.0.2 (Unsupported class file major version 58)

[Oleg Cohen]

Thank you, JB!

I compiled my code with 11.0.7 and Karaf ran with 14.0.2

Best,
Oleg


> On Oct 29, 2020, at 1:49 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi,
> 
> I have to check the JDK used to compile spifly. Not sure it’s compatible with 
> JDK14.
> 
> When you say you compile with JDK 14, is it Karaf or your application ?
> 
> Regards
> JB
> 
>> Le 29 oct. 2020 à 02:37, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> 
>> Greetings,
>> 
>> I was wondering if anyone else ran into the same issue. All runs well for me 
>> on JDK 11.0.7
>> 
>> When I do a new clean install on JDK 14.0.2, I get the following error when 
>> installing bundles:
>> 
>> java.lang.IllegalArgumentException: Unsupported class file major version 58
>> 
>> A rather long stack trace is below. I am trying to figure how to identify 
>> the culprit is and resolve the issue.
>> 
>> ASM version I have is 8.0.1
>> 
>> Thank you!
>> Oleg
>> 
>> 
>> 
>> 2020-10-28T21:26:17,875 | ERROR | FelixDispatchQueue | FrameworkEvent
>>| 123 - org.apache.aries.spifly.dynamic.bundle - 1.2.0 | 
>> FrameworkEvent ERROR
>> java.lang.IllegalArgumentException: Unsupported class file major version 58
>>  at org.objectweb.asm.ClassReader.(ClassReader.java:184) ~[?:?]
>>  at org.objectweb.asm.ClassReader.(ClassReader.java:166) ~[?:?]
>>  at org.objectweb.asm.ClassReader.(ClassReader.java:152) ~[?:?]
>>  at org.objectweb.asm.ClassReader.(ClassReader.java:273) ~[?:?]
>>  at 
>> org.apache.aries.spifly.dynamic.OSGiFriendlyClassWriter.getCommonSuperClass(OSGiFriendlyClassWriter.java:81)
>>  ~[?:?]
>>  at org.objectweb.asm.SymbolTable.addMergedType(SymbolTable.java:1198) 
>> ~[?:?]
>>  at org.objectweb.asm.Frame.merge(Frame.java:1294) ~[?:?]
>>  at org.objectweb.asm.Frame.merge(Frame.java:1175) ~[?:?]
>>  at 
>> org.objectweb.asm.MethodWriter.computeAllFrames(MethodWriter.java:1617) 
>> ~[?:?]
>>  at org.objectweb.asm.MethodWriter.visitMaxs(MethodWriter.java:1553) 
>> ~[?:?]
>>  at org.objectweb.asm.MethodVisitor.visitMaxs(MethodVisitor.java:768) 
>> ~[?:?]
>>  at 
>> org.objectweb.asm.commons.LocalVariablesSorter.visitMaxs(LocalVariablesSorter.java:147)
>>  ~[?:?]
>>  at org.objectweb.asm.ClassReader.readCode(ClassReader.java:2426) ~[?:?]
>>  at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1275) 
>> ~[?:?]
>>  at org.objectweb.asm.ClassReader.accept(ClassReader.java:679) ~[?:?]
>>  at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) ~[?:?]
>>  at 
>> org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:60)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>>  ~[?:?]
>>  at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1414)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1660)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1590)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
>>  ~[?:?]
>>  at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
>>  at java.lang.Class.getDeclaredConstructors0(Native Method) ~[?:?]
>>  at java.lang.Class.privateGetDeclaredConstructors(Class.java:3215) 
>> ~[?:?]
>>  at java.lang.Class.getConstructor0(Class.

Re: No component with id 'blueprintBundle' could be found when stopping/restarting a bundle with Camel

[Oleg Cohen]

Thank you, JB!

> On Oct 29, 2020, at 1:51 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi,
> 
> blueprintBundle is a implicite blueprint bean containing the bundle context.
> 
> This bean is used in the camel blueprint. It seems that the bean is destroyed 
> before camel context, causing this issue.
> It’s an improvement to do on camel blueprint to manage the cycle.
> I will create a Jira and fix that at Camel.
> 
> Regards
> JB
> 
>> Le 29 oct. 2020 à 03:45, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> Looking for help with this error. I have a bundle that has a camel route. 
>> Every time I stop/restart the bundle I see the following error:
>> 
>> org.osgi.service.blueprint.container.NoSuchComponentException: No component 
>> with id 'blueprintBundle' could be found
>> 
>> This route is very small and it is initialized via a custom builder like 
>> this:
>> 
>> 
>> 
>> A full stack trace is below.
>> 
>> Would appreciate any help/insight on this!
>> 
>> Thank you,
>> Oleg
>> 
>> 
>> 2020-10-28T22:40:14,531 | INFO  | pipe-restart infocus.core.demo | 
>> DefaultShutdownStrategy  | 126 - org.apache.camel.camel-base - 3.6.0 
>> | Graceful shutdown of 1 routes completed in 0 seconds
>> 2020-10-28T22:40:14,536 | INFO  | pipe-restart infocus.core.demo | 
>> CoreTypeConverterRegistry| 126 - org.apache.camel.camel-base - 3.6.0 
>> | TypeConverterRegistry utilization[noop=0, attempts=2, hits=2, misses=0, 
>> failures=0] mappings[total=216, misses=0]
>> 2020-10-28T22:40:14,536 | WARN  | pipe-restart infocus.core.demo | 
>> AbstractCamelContext | 126 - org.apache.camel.camel-base - 3.6.0 
>> | Error occurred while stopping lifecycle strategies. This exception will be 
>> ignored.
>> org.osgi.service.blueprint.container.NoSuchComponentException: No component 
>> with id 'blueprintBundle' could be found
>>  at 
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.getComponentInstance(BlueprintContainerImpl.java:805)
>>  ~[?:?]
>>  at 
>> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:104)
>>  ~[?:?]
>>  at 
>> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:100)
>>  ~[?:?]
>>  at 
>> org.apache.camel.blueprint.BlueprintContainerBeanRepository.findByType(BlueprintContainerBeanRepository.java:94)
>>  ~[?:?]
>>  at 
>> org.apache.camel.support.DefaultRegistry.findByType(DefaultRegistry.java:203)
>>  ~[!/:3.6.0]
>>  at 
>> org.apache.camel.impl.engine.OnCamelContextLifecycleStrategy.onContextStopped(OnCamelContextLifecycleStrategy.java:125)
>>  ~[!/:3.6.0]
>>  at 
>> org.apache.camel.impl.engine.AbstractCamelContext.doStop(AbstractCamelContext.java:2941)
>>  [!/:3.6.0]
>>  at 
>> org.apache.camel.support.service.BaseService.stop(BaseService.java:156) 
>> [!/:3.6.0]
>>  at 
>> org.apache.camel.impl.engine.AbstractCamelContext.stop(AbstractCamelContext.java:2453)
>>  [!/:3.6.0]
>>  at 
>> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:145)
>>  [!/:3.6.0]
>>  at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
>> ~[?:?]
>>  at 
>> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>  ~[?:?]
>>  at 
>> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  ~[?:?]
>>  at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>>  at 
>> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:337)
>>  [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:835) 
>> [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:742) 
>> [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:434)
>>  [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:778)
>>  [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:987)
>>  [!/:1.10.2]
>>  at 
>> org.apache.aries.blueprint.container.B

Re: Strange 4.2.9/4.2.10 mixup when adding camel repos

[Oleg Cohen]

I fixed it by blacklisting repos in etc/org.apache.karaf.features.xml


mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features

mvn:org.ops4j.pax.web/pax-web-features/7.2.16/xml/features

mvn:org.apache.karaf.features/spring-legacy/4.2.9/xml/features

mvn:org.apache.karaf.features/standard/4.2.9/xml/features


mvn:org.apache.karaf.features/standard/[4,5)/xml/features

This removed the issues.

> On Oct 29, 2020, at 5:47 AM, John Taylor  wrote:
> 
> Hi,
> I also see this with camel 3.4.4.
> 
> Both camel 3.6.0 and 3.4.4 features.xml [1] have spring-legacy/4.2.9 
> 
>
>mvn:org.apache.karaf.features/spring-legacy/4.2.9/xml/features
>
> 
> So I guess that would be why?
> -John
> 
> [1] 
> https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.4.4/apache-camel-3.4.4-features.xml
>  
> <https://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/3.4.4/apache-camel-3.4.4-features.xml>
> On Thu, Oct 29, 2020 at 5:47 AM Jean-Baptiste Onofre  <mailto:j...@nanthrax.net>> wrote:
> Hi,
> 
> Let me try. AFAIR, Camel uses a range, so it should be fine.
> 
> Regards
> JB
> 
>> Le 28 oct. 2020 à 12:04, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> I am migrating to Karaf v4.2.10. Starting from a clean container.
>> 
>> If I install feature war all works fine.
>> 
>> After I add two camel repos:
>> 
>>  feature:repo-add 
>> mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features   
>>  feature:repo-add 
>> mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
>> 
>> I see a number of errors when installing war (or any other feature). I 
>> noticed that there are commands to install 
>> org.apache.karaf.scr.management/4.2.9 along with 4.2.10
>> 
>> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | CommandExtension 
>> | 37 - org.apache.karaf.shell.core - 4.2.10 | Registering 
>> commands for bundle org.apache.karaf.scr.state/4.2.10
>> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | FeaturesServiceImpl  
>> | 11 - org.apache.karaf.features.core - 4.2.10 |   
>> org.apache.karaf.scr.management/4.2.9
>> 2020-10-28T06:59:33,772 | INFO  | features-3-thread-1 | 
>> ServiceComponentRuntimeMBeanImpl | 59 - org.apache.karaf.scr.management - 
>> 4.2.9 | Activating the Apache Karaf ServiceComponentRuntime MBean
>> 2020-10-28T06:59:33,773 | INFO  | features-3-thread-1 | FeaturesServiceImpl  
>> | 11 - org.apache.karaf.features.core - 4.2.10 |   
>> org.apache.karaf.scr.management/4.2.10
>> 
>> The errors are JMX based:
>> 
>> 2020-10-28T06:59:33,779 | INFO  | features-3-thread-1 | 
>> ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
>> 4.2.10 | Activating the Apache Karaf ServiceComponentRuntime MBean
>> 2020-10-28T06:59:33,780 | ERROR | features-3-thread-1 | 
>> ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
>> 4.2.10 | Exception registering the SCR Management MBean: 
>> org.apache.karaf:type=scr,name=root
>> javax.management.InstanceAlreadyExistsException: 
>> org.apache.karaf:type=scr,name=root
>> 
>> Would appreciate help on resolving this!
>> 
>> Best,
>> Oleg
> 

Re: No component with id 'blueprintBundle' could be found when stopping/restarting a bundle with Camel

[Oleg Cohen]

BTW, I asked this before. I saw someone else asking. This is on 4.2.10.

> On Oct 28, 2020, at 10:45 PM, Oleg Cohen  wrote:
> 
> Greetings,
> 
> Looking for help with this error. I have a bundle that has a camel route. 
> Every time I stop/restart the bundle I see the following error:
> 
> org.osgi.service.blueprint.container.NoSuchComponentException: No component 
> with id 'blueprintBundle' could be found
> 
> This route is very small and it is initialized via a custom builder like this:
> 
> 
> 
> A full stack trace is below.
> 
> Would appreciate any help/insight on this!
> 
> Thank you,
> Oleg
> 
> 
> 2020-10-28T22:40:14,531 | INFO  | pipe-restart infocus.core.demo | 
> DefaultShutdownStrategy  | 126 - org.apache.camel.camel-base - 3.6.0 
> | Graceful shutdown of 1 routes completed in 0 seconds
> 2020-10-28T22:40:14,536 | INFO  | pipe-restart infocus.core.demo | 
> CoreTypeConverterRegistry| 126 - org.apache.camel.camel-base - 3.6.0 
> | TypeConverterRegistry utilization[noop=0, attempts=2, hits=2, misses=0, 
> failures=0] mappings[total=216, misses=0]
> 2020-10-28T22:40:14,536 | WARN  | pipe-restart infocus.core.demo | 
> AbstractCamelContext | 126 - org.apache.camel.camel-base - 3.6.0 
> | Error occurred while stopping lifecycle strategies. This exception will be 
> ignored.
> org.osgi.service.blueprint.container.NoSuchComponentException: No component 
> with id 'blueprintBundle' could be found
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.getComponentInstance(BlueprintContainerImpl.java:805)
>  ~[?:?]
>   at 
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:104)
>  ~[?:?]
>   at 
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:100)
>  ~[?:?]
>   at 
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.findByType(BlueprintContainerBeanRepository.java:94)
>  ~[?:?]
>   at 
> org.apache.camel.support.DefaultRegistry.findByType(DefaultRegistry.java:203) 
> ~[!/:3.6.0]
>   at 
> org.apache.camel.impl.engine.OnCamelContextLifecycleStrategy.onContextStopped(OnCamelContextLifecycleStrategy.java:125)
>  ~[!/:3.6.0]
>   at 
> org.apache.camel.impl.engine.AbstractCamelContext.doStop(AbstractCamelContext.java:2941)
>  [!/:3.6.0]
>   at 
> org.apache.camel.support.service.BaseService.stop(BaseService.java:156) 
> [!/:3.6.0]
>   at 
> org.apache.camel.impl.engine.AbstractCamelContext.stop(AbstractCamelContext.java:2453)
>  [!/:3.6.0]
>   at 
> org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:145)
>  [!/:3.6.0]
>   at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:?]
>   at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  ~[?:?]
>   at 
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:?]
>   at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>   at 
> org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:337)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:835) 
> [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:742) 
> [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:434)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:778)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:987)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:923)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender$3.run(BlueprintExtender.java:336)
>  [!/:1.10.2]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.destroyContainer(BlueprintExtender.java:357)
>  [!/:1.10.2]
>   at 
> org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:249)
>  [!/:1.10.2]
>   at 
> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBun

No component with id 'blueprintBundle' could be found when stopping/restarting a bundle with Camel

[Oleg Cohen]

Greetings,

Looking for help with this error. I have a bundle that has a camel route. Every 
time I stop/restart the bundle I see the following error:

org.osgi.service.blueprint.container.NoSuchComponentException: No component 
with id 'blueprintBundle' could be found

This route is very small and it is initialized via a custom builder like this:



A full stack trace is below.

Would appreciate any help/insight on this!

Thank you,
Oleg


2020-10-28T22:40:14,531 | INFO  | pipe-restart infocus.core.demo | 
DefaultShutdownStrategy  | 126 - org.apache.camel.camel-base - 3.6.0 | 
Graceful shutdown of 1 routes completed in 0 seconds
2020-10-28T22:40:14,536 | INFO  | pipe-restart infocus.core.demo | 
CoreTypeConverterRegistry| 126 - org.apache.camel.camel-base - 3.6.0 | 
TypeConverterRegistry utilization[noop=0, attempts=2, hits=2, misses=0, 
failures=0] mappings[total=216, misses=0]
2020-10-28T22:40:14,536 | WARN  | pipe-restart infocus.core.demo | 
AbstractCamelContext | 126 - org.apache.camel.camel-base - 3.6.0 | 
Error occurred while stopping lifecycle strategies. This exception will be 
ignored.
org.osgi.service.blueprint.container.NoSuchComponentException: No component 
with id 'blueprintBundle' could be found
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.getComponentInstance(BlueprintContainerImpl.java:805)
 ~[?:?]
at 
org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:104)
 ~[?:?]
at 
org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:100)
 ~[?:?]
at 
org.apache.camel.blueprint.BlueprintContainerBeanRepository.findByType(BlueprintContainerBeanRepository.java:94)
 ~[?:?]
at 
org.apache.camel.support.DefaultRegistry.findByType(DefaultRegistry.java:203) 
~[!/:3.6.0]
at 
org.apache.camel.impl.engine.OnCamelContextLifecycleStrategy.onContextStopped(OnCamelContextLifecycleStrategy.java:125)
 ~[!/:3.6.0]
at 
org.apache.camel.impl.engine.AbstractCamelContext.doStop(AbstractCamelContext.java:2941)
 [!/:3.6.0]
at 
org.apache.camel.support.service.BaseService.stop(BaseService.java:156) 
[!/:3.6.0]
at 
org.apache.camel.impl.engine.AbstractCamelContext.stop(AbstractCamelContext.java:2453)
 [!/:3.6.0]
at 
org.apache.camel.blueprint.BlueprintCamelContext.destroy(BlueprintCamelContext.java:145)
 [!/:3.6.0]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
~[?:?]
at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 ~[?:?]
at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
at 
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:337)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:835) 
[!/:1.10.2]
at 
org.apache.aries.blueprint.container.BeanRecipe.destroy(BeanRecipe.java:742) 
[!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintRepository.destroy(BlueprintRepository.java:434)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroyComponents(BlueprintContainerImpl.java:778)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.tidyupComponents(BlueprintContainerImpl.java:987)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.destroy(BlueprintContainerImpl.java:923)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender$3.run(BlueprintExtender.java:336)
 [!/:1.10.2]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at 
org.apache.aries.blueprint.container.BlueprintExtender.destroyContainer(BlueprintExtender.java:357)
 [!/:1.10.2]
at 
org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:249)
 [!/:1.10.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500)
 [!/:1.10.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433)
 [!/:1.10.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725)
 [!/:1.10.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463)
 [!/:1.10.2]
at 
org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422)
 [!/:1.10.2]
at 

Issue running v4.2.10 with JDK 14.0.2 (Unsupported class file major version 58)

[Oleg Cohen]

Greetings,

I was wondering if anyone else ran into the same issue. All runs well for me on 
JDK 11.0.7

When I do a new clean install on JDK 14.0.2, I get the following error when 
installing bundles:

java.lang.IllegalArgumentException: Unsupported class file major version 58

A rather long stack trace is below. I am trying to figure how to identify the 
culprit is and resolve the issue.

ASM version I have is 8.0.1

Thank you!
Oleg



2020-10-28T21:26:17,875 | ERROR | FelixDispatchQueue | FrameworkEvent   
| 123 - org.apache.aries.spifly.dynamic.bundle - 1.2.0 | FrameworkEvent 
ERROR
java.lang.IllegalArgumentException: Unsupported class file major version 58
at org.objectweb.asm.ClassReader.(ClassReader.java:184) ~[?:?]
at org.objectweb.asm.ClassReader.(ClassReader.java:166) ~[?:?]
at org.objectweb.asm.ClassReader.(ClassReader.java:152) ~[?:?]
at org.objectweb.asm.ClassReader.(ClassReader.java:273) ~[?:?]
at 
org.apache.aries.spifly.dynamic.OSGiFriendlyClassWriter.getCommonSuperClass(OSGiFriendlyClassWriter.java:81)
 ~[?:?]
at org.objectweb.asm.SymbolTable.addMergedType(SymbolTable.java:1198) 
~[?:?]
at org.objectweb.asm.Frame.merge(Frame.java:1294) ~[?:?]
at org.objectweb.asm.Frame.merge(Frame.java:1175) ~[?:?]
at 
org.objectweb.asm.MethodWriter.computeAllFrames(MethodWriter.java:1617) ~[?:?]
at org.objectweb.asm.MethodWriter.visitMaxs(MethodWriter.java:1553) 
~[?:?]
at org.objectweb.asm.MethodVisitor.visitMaxs(MethodVisitor.java:768) 
~[?:?]
at 
org.objectweb.asm.commons.LocalVariablesSorter.visitMaxs(LocalVariablesSorter.java:147)
 ~[?:?]
at org.objectweb.asm.ClassReader.readCode(ClassReader.java:2426) ~[?:?]
at org.objectweb.asm.ClassReader.readMethod(ClassReader.java:1275) 
~[?:?]
at org.objectweb.asm.ClassReader.accept(ClassReader.java:679) ~[?:?]
at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) ~[?:?]
at 
org.apache.aries.spifly.dynamic.ClientWeavingHook.weave(ClientWeavingHook.java:60)
 ~[?:?]
at 
org.apache.felix.framework.util.SecureAction.invokeWeavingHook(SecureAction.java:1203)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.transformClass(BundleWiringImpl.java:2465)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2152)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1607)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
 ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1414)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1660)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1590)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
 ~[?:?]
at 
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
 ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:522) ~[?:?]
at java.lang.Class.getDeclaredConstructors0(Native Method) ~[?:?]
at java.lang.Class.privateGetDeclaredConstructors(Class.java:3215) 
~[?:?]
at java.lang.Class.getConstructor0(Class.java:3420) ~[?:?]
at java.lang.Class.getConstructor(Class.java:2165) ~[?:?]
at java.util.ServiceLoader$1.run(ServiceLoader.java:662) ~[?:?]
at java.util.ServiceLoader$1.run(ServiceLoader.java:659) ~[?:?]
at 
java.security.AccessController.doPrivileged(AccessController.java:554) ~[?:?]
at java.util.ServiceLoader.getConstructor(ServiceLoader.java:670) ~[?:?]
at 
java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1234)
 ~[?:?]
at 
java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1266)
 ~[?:?]
at java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1301) ~[?:?]
at java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1386) ~[?:?]
at 
org.eclipse.jetty.websocket.api.extensions.ExtensionFactory.(ExtensionFactory.java:41)
 ~[?:?]
at 
org.eclipse.jetty.websocket.common.extensions.WebSocketExtensionFactory.(WebSocketExtensionFactory.java:53)
 ~[?:?]
at 
org.eclipse.jetty.websocket.server.WebSocketServerFactory.(WebSocketServerFactory.java:164)
 ~[?:?]
at 
org.eclipse.jetty.websocket.server.WebSocketServerFactory.(WebSocketServerFactory.java:138)
 ~[?:?]
at 

Re: Strange 4.2.9/4.2.10 mixup when adding camel repos

[Oleg Cohen]

Some more info as I keep looking at what transpires here.

Before I add the camel repo:

karaf@root()> feature:repo-list
Repository│ URL
──┼─
spring-4.2.10 │ 
mvn:org.apache.karaf.features/spring/4.2.10/xml/features
standard-4.2.10   │ 
mvn:org.apache.karaf.features/standard/4.2.10/xml/features
hibernate-validator-osgi-features │ 
mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.1.5.Final/xml/features
enterprise-4.2.10 │ 
mvn:org.apache.karaf.features/enterprise/4.2.10/xml/features
openjpa-3.1.1 │ 
mvn:org.apache.openjpa/openjpa-features/3.1.1/xml/features
org.ops4j.pax.jdbc-1.4.4  │ 
mvn:org.ops4j.pax.jdbc/pax-jdbc-features/1.4.4/xml/features
aries-jpa-2.7.2   │ 
mvn:org.apache.aries.jpa/jpa-features/2.7.2/xml/features
org.ops4j.pax.cdi-1.1.3   │ 
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.1.3/xml/features
pax-jms-1.0.7 │ 
mvn:org.ops4j.pax.jms/pax-jms-features/1.0.7/xml/features
pax-transx-0.4.4  │ 
mvn:org.ops4j.pax.transx/pax-transx-features/0.4.4/xml/features
framework-4.2.10  │ 
mvn:org.apache.karaf.features/framework/4.2.10/xml/features
org.ops4j.pax.web-7.2.19  │ 
mvn:org.ops4j.pax.web/pax-web-features/7.2.19/xml/features


After I add the camel repo:

karaf@root()> feature:repo-list
Repository│ URL
──┼─
standard-4.2.10   │ 
mvn:org.apache.karaf.features/standard/4.2.10/xml/features
hibernate-validator-osgi-features │ 
mvn:org.hibernate.validator/hibernate-validator-osgi-karaf-features/6.1.5.Final/xml/features
standard-4.2.9│ 
mvn:org.apache.karaf.features/standard/4.2.9/xml/features
org.ops4j.pax.web-7.2.16  │ 
mvn:org.ops4j.pax.web/pax-web-features/7.2.16/xml/features
spring-legacy-4.2.9   │ 
mvn:org.apache.karaf.features/spring-legacy/4.2.9/xml/features
aries-jpa-2.7.2   │ 
mvn:org.apache.aries.jpa/jpa-features/2.7.2/xml/features
pax-transx-0.4.4  │ 
mvn:org.ops4j.pax.transx/pax-transx-features/0.4.4/xml/features
framework-4.2.10  │ 
mvn:org.apache.karaf.features/framework/4.2.10/xml/features
spring-4.2.10 │ 
mvn:org.apache.karaf.features/spring/4.2.10/xml/features
enterprise-4.2.10 │ 
mvn:org.apache.karaf.features/enterprise/4.2.10/xml/features
camel-3.6.0   │ 
mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
org.ops4j.pax.cdi-1.0.0   │ 
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.0.0/xml/features
openjpa-3.1.1 │ 
mvn:org.apache.openjpa/openjpa-features/3.1.1/xml/features
org.ops4j.pax.jdbc-1.4.4  │ 
mvn:org.ops4j.pax.jdbc/pax-jdbc-features/1.4.4/xml/features
cxf-3.4.0 │ 
mvn:org.apache.cxf.karaf/apache-cxf/3.4.0/xml/features
jclouds-2.1.2 │ 
mvn:org.apache.jclouds.karaf/jclouds-karaf/2.1.2/xml/features
org.ops4j.pax.cdi-1.1.3   │ 
mvn:org.ops4j.pax.cdi/pax-cdi-features/1.1.3/xml/features
pax-jms-1.0.7 │ 
mvn:org.ops4j.pax.jms/pax-jms-features/1.0.7/xml/features
org.ops4j.pax.web-7.2.19  │ 
mvn:org.ops4j.pax.web/pax-web-features/7.2.19/xml/features



> On Oct 28, 2020, at 7:07 AM, Oleg Cohen  wrote:
> 
> To add, it is actually enough to reproduce the error by calling
> 
> feature:repo-add camel
> 
> before installing a feature like war 
> 
> Thanks!
> Oleg
> 
>> On Oct 28, 2020, at 7:04 AM, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> wrote:
>> 
>> Greetings,
>> 
>> I am migrating to Karaf v4.2.10. Starting from a clean container.
>> 
>> If I install feature war all works fine.
>> 
>> After I add two camel repos:
>> 
>>  feature:repo-add 
>> mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features   
>>  feature:repo-add 
>> mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
>> 
>> I see a number of errors when installing war (or any other feature). I 
>> noticed that there are commands to install 
>> org.apache.karaf.scr.management/4.2.9 along with 4.2.10
>> 
>> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | CommandExtension 
>> | 37 - org.apache.karaf.shell.core - 4.2.10 | Registering 
>> commands for bundle org.apache.karaf.scr.state/4.2.10
>> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | FeaturesServiceImpl  
>> | 11 - org.apache.karaf.features.core - 4.2.

Re: Strange 4.2.9/4.2.10 mixup when adding camel repos

[Oleg Cohen]

To add, it is actually enough to reproduce the error by calling

feature:repo-add camel

before installing a feature like war 

Thanks!
Oleg

> On Oct 28, 2020, at 7:04 AM, Oleg Cohen  wrote:
> 
> Greetings,
> 
> I am migrating to Karaf v4.2.10. Starting from a clean container.
> 
> If I install feature war all works fine.
> 
> After I add two camel repos:
> 
>   feature:repo-add 
> mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features   
>   feature:repo-add 
> mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
> 
> I see a number of errors when installing war (or any other feature). I 
> noticed that there are commands to install 
> org.apache.karaf.scr.management/4.2.9 along with 4.2.10
> 
> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | CommandExtension  
>| 37 - org.apache.karaf.shell.core - 4.2.10 | Registering commands 
> for bundle org.apache.karaf.scr.state/4.2.10
> 2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | FeaturesServiceImpl   
>| 11 - org.apache.karaf.features.core - 4.2.10 |   
> org.apache.karaf.scr.management/4.2.9
> 2020-10-28T06:59:33,772 | INFO  | features-3-thread-1 | 
> ServiceComponentRuntimeMBeanImpl | 59 - org.apache.karaf.scr.management - 
> 4.2.9 | Activating the Apache Karaf ServiceComponentRuntime MBean
> 2020-10-28T06:59:33,773 | INFO  | features-3-thread-1 | FeaturesServiceImpl   
>| 11 - org.apache.karaf.features.core - 4.2.10 |   
> org.apache.karaf.scr.management/4.2.10
> 
> The errors are JMX based:
> 
> 2020-10-28T06:59:33,779 | INFO  | features-3-thread-1 | 
> ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
> 4.2.10 | Activating the Apache Karaf ServiceComponentRuntime MBean
> 2020-10-28T06:59:33,780 | ERROR | features-3-thread-1 | 
> ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
> 4.2.10 | Exception registering the SCR Management MBean: 
> org.apache.karaf:type=scr,name=root
> javax.management.InstanceAlreadyExistsException: 
> org.apache.karaf:type=scr,name=root
> 
> Would appreciate help on resolving this!
> 
> Best,
> Oleg

Strange 4.2.9/4.2.10 mixup when adding camel repos

[Oleg Cohen]

Greetings,

I am migrating to Karaf v4.2.10. Starting from a clean container.

If I install feature war all works fine.

After I add two camel repos:

feature:repo-add 
mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features   
feature:repo-add 
mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features

I see a number of errors when installing war (or any other feature). I noticed 
that there are commands to install org.apache.karaf.scr.management/4.2.9 along 
with 4.2.10

2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | CommandExtension
 | 37 - org.apache.karaf.shell.core - 4.2.10 | Registering commands for 
bundle org.apache.karaf.scr.state/4.2.10
2020-10-28T06:59:33,762 | INFO  | features-3-thread-1 | FeaturesServiceImpl 
 | 11 - org.apache.karaf.features.core - 4.2.10 |   
org.apache.karaf.scr.management/4.2.9
2020-10-28T06:59:33,772 | INFO  | features-3-thread-1 | 
ServiceComponentRuntimeMBeanImpl | 59 - org.apache.karaf.scr.management - 4.2.9 
| Activating the Apache Karaf ServiceComponentRuntime MBean
2020-10-28T06:59:33,773 | INFO  | features-3-thread-1 | FeaturesServiceImpl 
 | 11 - org.apache.karaf.features.core - 4.2.10 |   
org.apache.karaf.scr.management/4.2.10

The errors are JMX based:

2020-10-28T06:59:33,779 | INFO  | features-3-thread-1 | 
ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
4.2.10 | Activating the Apache Karaf ServiceComponentRuntime MBean
2020-10-28T06:59:33,780 | ERROR | features-3-thread-1 | 
ServiceComponentRuntimeMBeanImpl | 60 - org.apache.karaf.scr.management - 
4.2.10 | Exception registering the SCR Management MBean: 
org.apache.karaf:type=scr,name=root
javax.management.InstanceAlreadyExistsException: 
org.apache.karaf:type=scr,name=root

Would appreciate help on resolving this!

Best,
Oleg

Re: Missing jdk.net dependency

[Oleg Cohen]

Thank you, JB! It worked.

> On Oct 28, 2020, at 2:28 AM, Jean-Baptiste Onofre  wrote:
> 
> Hi Oleg,
> 
> It should be optional for mongodb.
> 
> Anyway, depending of the JDK you use, it’s provided by the JDK. So you can 
> add in etc/jre.properties.
> 
> Regards
> JB
> 
>> Le 27 oct. 2020 à 18:08, Oleg Cohen > <mailto:oleg.co...@assurebridge.com>> a écrit :
>> 
>> Greetings,
>> 
>> I ran into an issue when trying to use a new mongo driver. There seems to be 
>> a missing dependency on jdk.net <http://jdk.net/>
>> 
>> missing requirement [org.mongodb.driver-core/4.1.1] osgi.wiring.package; 
>> filter:="(osgi.wiring.package=jdk.net <http://jdk.net/>)”]]
>> 
>> Is there any way I can add it to the bootstrap?
>> 
>> Thank you!
>> Oleg
> 

Missing jdk.net dependency

[Oleg Cohen]

Greetings,

I ran into an issue when trying to use a new mongo driver. There seems to be a 
missing dependency on jdk.net

missing requirement [org.mongodb.driver-core/4.1.1] osgi.wiring.package; 
filter:="(osgi.wiring.package=jdk.net)”]]

Is there any way I can add it to the bootstrap?

Thank you!
Oleg

Re: OAuth2.0 does anyone doing on Karaf?

[Oleg Cohen]

Hi JB,

I would love to see that example too!

I have been using Spring Security and Spring OAuth 2.4.x. It is now
deprecated and the new version 5.3 no longer supports the Provider/Auth
Server. How did you solve that migration?

Best,
Oleg

On Tue, Jun 30, 2020 at 3:27 AM Jean-Baptiste Onofre 
wrote:

> Hi Davi,
>
> Two things:
>
> 1. You can use oauth2 without spring, pretty easily directly
> programmatically in a OSGi service. I can add an example about that. It’s
> very simple and works smoothly.
> 2. I’m working on spring-boot artifacts support in Karaf (I’m working on
> the PoC and I will send proposal with details soon).
>
> Regards
> JB
>
> Le 30 juin 2020 à 01:54, Davi Baldin Tavares  a
> écrit :
>
> Hi Karafers,
>
> I'm still working on securing my HTTP context deployed on Karaf and most
> of the oauth2.0 implementation references are being addressed by Spring
> boot. I've found 4.2.9 has Spring Security Feature 5.3.x.
>
> Do I either go Spring boot approach (example
> https://stackoverflow.com/questions/30881786/can-spring-boot-be-used-with-osgi-if-not-any-plans-to-have-an-osgi-spring-boot)
> or I have OSGi centric better option (better is simple, standard and clear)?
>
> Cheers,
>
> Davi
>
>
>

-- 
*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 <http://www.assurebridge.com>*

Re: ERROR: No component with id 'blueprintBundle' could be found

[Oleg Cohen]

Yes, the route works. The error is only seen on restart/update and when the
bundle starts all is good.

On Mon, Jun 29, 2020 at 5:35 AM Jean-Baptiste Onofre 
wrote:

> Does it work if you actually configure a simple route like:
>
> from("direct:foo").log("hello")
>
> ?
>
> Regards
> JB
>
> Le 29 juin 2020 à 11:32, Oleg Cohen  a écrit
> :
>
> Hi JB,
>
> No, nothing in my own code.
>
> This is a plain vanilla out-o-f-the-box example. No logic added yet.
>
> Here is my blueprint.xml file
>
> 
>
> http://www.osgi.org/xmlns/blueprint/v1.0.0
> <http://www.osgi.org/xmlns/blueprint/v1.0.0>"*
>
> xmlns:xsi=*"http://www.w3.org/2001/XMLSchema-instance
> <http://www.w3.org/2001/XMLSchema-instance>"*
> xmlns:cm=*"http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>"*
> xmlns:ext=*"http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>"*
>
> xmlns:camel=*"http://camel.apache.org/schema/blueprint
> <http://camel.apache.org/schema/blueprint>"*
>
> xsi:schemaLocation=*"*
> * http://www.osgi.org/xmlns/blueprint/v1.0.0
> <http://www.osgi.org/xmlns/blueprint/v1.0.0>
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
> <http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd> *
> *http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>
> http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>*
> *http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>
> http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
> <http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>*
> * http://camel.apache.org/schema/blueprint
> <http://camel.apache.org/schema/blueprint>
> https://camel.apache.org/schema/blueprint/camel-blueprint.xsd
> <https://camel.apache.org/schema/blueprint/camel-blueprint.xsd>"*>
>
>  *"com.ab.infocus.core.demo.xxx.XXXTaxNotificationsRouteBuilder"*>
>
> 
>
>  xmlns=*"http://camel.apache.org/schema/blueprint
> <http://camel.apache.org/schema/blueprint>"*
> typeConverterStatisticsEnabled=*"true"*
> id=*"infocus-demo-services"*
> threadNamePattern=*"Camel-Thread #counter#"*>
>
>   
>
>
>  defaultProfile=*"true"* poolSize=*"5"* keepAliveTime=*"25"*
> maxPoolSize=*"15"* maxQueueSize=*"250"* rejectedPolicy=*"Abort"* />
>
> 
>
>
>
> 
>
> And here is the  taxNotificationsRouteBuilder:
>
> *package* com.ab.infocus.core.demo.xxx;
>
> *import* org.apache.camel.LoggingLevel;
> *import* org.apache.camel.Processor;
> *import* org.apache.camel.builder.RouteBuilder;
> *import* org.apache.logging.log4j.LogManager;
> *import* org.apache.logging.log4j.Logger;
>
> *public* *class* XXXTaxNotificationsRouteBuilder *extends* RouteBuilder {
>
> *private* *static* *final* Logger *logger* = LogManager.*getLogger*
> (XXXTaxNotificationsRouteBuilder.*class*);
>
>
> @Override
> *public* *void* configure() *throws* Exception {
>
>
> }
> }
>
>
>
>
>
>
> On Mon, Jun 29, 2020 at 5:26 AM Jean-Baptiste Onofre 
> wrote:
>
>> Hi,
>>
>> It sounds like a race condition where you destroy the blueprint container
>> and after you are destroying the beans in the blueprint container.
>>
>> I guess you are doing this by your own code right ?
>>
>> Regards
>> JB
>>
>> Le 29 juin 2020 à 11:23, Oleg Cohen  a
>> écrit :
>>
>> Greetings,
>>
>> I am seeing this error when restarting a bunde with a CamelContex.
>>
>> *No component with id 'blueprintBundle' could be found*
>>
>> The stacktrace is below. I wonder if I am doing something wrong.
>>
>> Thank you!
>> Oleg
>>
>>
>> 2020-06-29T05:18:56,294 | INFO  | pipe-update infocus.core.demo |
>> BlueprintExtender| 110 - org.apache.aries.blueprint.core -
>> 1.10.2 | Destroying container for blueprint bundle
>> infocus.core.demo/1.0.1.SNAPSHOT
>> 2020-06-29T05:18:56,302 | INFO  | pipe-update infocus.core.demo |
>> AbstractCamelContext | 121 - org.apache.camel.camel-base -
>> 3.4.0 | Apache Camel 3.4.0 (infoc

Re: ERROR: No component with id 'blueprintBundle' could be found

[Oleg Cohen]

Hi JB,

No, nothing in my own code.

This is a plain vanilla out-o-f-the-box example. No logic added yet.

Here is my blueprint.xml file




http://www.osgi.org/xmlns/blueprint/v1.0.0
<http://www.osgi.org/xmlns/blueprint/v1.0.0>"*


xmlns:xsi=*"http://www.w3.org/2001/XMLSchema-instance
<http://www.w3.org/2001/XMLSchema-instance>"*

xmlns:cm=*"http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>"*

xmlns:ext=*"http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>"*


xmlns:camel=*"http://camel.apache.org/schema/blueprint
<http://camel.apache.org/schema/blueprint>"*


xsi:schemaLocation=*"*

* http://www.osgi.org/xmlns/blueprint/v1.0.0
<http://www.osgi.org/xmlns/blueprint/v1.0.0>
http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
<http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd> *

*http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>
http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0>*

*http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0
<http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.1.0>*

* http://camel.apache.org/schema/blueprint
<http://camel.apache.org/schema/blueprint>
https://camel.apache.org/schema/blueprint/camel-blueprint.xsd
<https://camel.apache.org/schema/blueprint/camel-blueprint.xsd>"*>








http://camel.apache.org/schema/blueprint
<http://camel.apache.org/schema/blueprint>"*

typeConverterStatisticsEnabled=*"true"*

id=*"infocus-demo-services"*

threadNamePattern=*"Camel-Thread #counter#"*>


  











And here is the  taxNotificationsRouteBuilder:

*package* com.ab.infocus.core.demo.xxx;


*import* org.apache.camel.LoggingLevel;

*import* org.apache.camel.Processor;

*import* org.apache.camel.builder.RouteBuilder;

*import* org.apache.logging.log4j.LogManager;

*import* org.apache.logging.log4j.Logger;


*public* *class* XXXTaxNotificationsRouteBuilder *extends* RouteBuilder {


*private* *static* *final* Logger *logger* = LogManager.*getLogger*
(XXXTaxNotificationsRouteBuilder.*class*);

@Override

*public* *void* configure() *throws* Exception {

}

}






On Mon, Jun 29, 2020 at 5:26 AM Jean-Baptiste Onofre 
wrote:

> Hi,
>
> It sounds like a race condition where you destroy the blueprint container
> and after you are destroying the beans in the blueprint container.
>
> I guess you are doing this by your own code right ?
>
> Regards
> JB
>
> Le 29 juin 2020 à 11:23, Oleg Cohen  a écrit
> :
>
> Greetings,
>
> I am seeing this error when restarting a bunde with a CamelContex.
>
> *No component with id 'blueprintBundle' could be found*
>
> The stacktrace is below. I wonder if I am doing something wrong.
>
> Thank you!
> Oleg
>
>
> 2020-06-29T05:18:56,294 | INFO  | pipe-update infocus.core.demo |
> BlueprintExtender| 110 - org.apache.aries.blueprint.core -
> 1.10.2 | Destroying container for blueprint bundle
> infocus.core.demo/1.0.1.SNAPSHOT
> 2020-06-29T05:18:56,302 | INFO  | pipe-update infocus.core.demo |
> AbstractCamelContext | 121 - org.apache.camel.camel-base -
> 3.4.0 | Apache Camel 3.4.0 (infocus-demo-services) is shutting down
> 2020-06-29T05:18:56,304 | WARN  | pipe-update infocus.core.demo |
> AbstractCamelContext | 121 - org.apache.camel.camel-base -
> 3.4.0 |
> *Error occurred while stopping lifecycle strategies. This exception will
> be ignored.org.osgi.service.blueprint.container.NoSuchComponentException:
> No component with id 'blueprintBundle' could be found*
> at
> org.apache.aries.blueprint.container.BlueprintContainerImpl.getComponentInstance(BlueprintContainerImpl.java:805)
> ~[?:?]
> at
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:104)
> ~[?:?]
> at
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.lookupByType(BlueprintContainerBeanRepository.java:100)
> ~[?:?]
> at
> org.apache.camel.blueprint.BlueprintContainerBeanRepository.findByType(BlueprintContainerBeanRepository.java:94)
> ~[?:?]
> at
> org.apache.camel.support.DefaultRegistry.findByType(DefaultRegistry.java:203)
> ~[!/:3.4.0]
> at
> org.apache.camel.impl.engine.OnCamelContextLifecycleStrategy.onContextStop(OnCamelContextLifecycleStrategy.java:60)
> ~[!/:3.4.0]
> at
> org.apache.camel.im

ERROR: No component with id 'blueprintBundle' could be found

[Oleg Cohen]

:?]
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018)
[org.apache.felix.framework-5.6.12.jar:?]
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004)
[org.apache.felix.framework-5.6.12.jar:?]
at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) [!/:?]
at
org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:49)
[!/:?]
at
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
[!/:4.2.9]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
[!/:4.2.9]
at
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
[!/:4.2.9]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:599)
[!/:4.2.9]
at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:526)
[!/:4.2.9]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:415)
[!/:4.2.9]
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:416) [!/:4.2.9]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) [!/:4.2.9]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) [!/:4.2.9]
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:834) [?:?]

-- 
*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 <http://www.assurebridge.com>*

Re: Error starting 4.2.9 with JDK 14.0.1 on Mac

[Oleg Cohen]

Thank you! What is the highest that is supported? I am still on JDK 8 and I 
would like to move closer to where things are today.

Best,
Oleg

> On Jun 16, 2020, at 9:47 AM, Christian Lutz  wrote:
> 
> Hello Oleg,
> 
> a few weeks ago JB mentioned that jdk 14 isnt supported, yet. Will be with 
> 4.2.10. 
> 
> kind regards. 
> 
>> Am 16.06.2020 um 13:57 schrieb Oleg Cohen :
>> 
>> 
>> Greetings,
>> 
>> I installed a brand new Karaf 4.2.9 and a JDK 14.0.1.
>> 
>> I get the following error starting ./bin/karaf
>> 
>> tcsh% ./bin/karaf
>> ERROR: Error parsing system bundle export statement: 
>> org.osgi.dto;version="1.0",org.osgi.resource;version="1.0",org.osgi.resource.dto;version="1.0";uses:="org.osgi.dto",org.osgi.framework;version="1.8",org.osgi.framework.dto;version="1.8";uses:="org.osgi.dto",org.osgi.framework.hooks.bundle;version="1.1";uses:="org.osgi.framework",org.osgi.framework.hooks.resolver;version="1.0";uses:="org.osgi.framework.wiring",org.osgi.framework.hooks.service;version="1.1";uses:="org.osgi.framework",org.osgi.framework.hooks.weaving;version="1.1";uses:="org.osgi.framework.wiring",org.osgi.framework.launch;version="1.2";uses:="org.osgi.framework",org.osgi.framework.namespace;version="1.1";uses:="org.osgi.resource",org.osgi.framework.startlevel;version="1.0";uses:="org.osgi.framework",org.osgi.framework.startlevel.dto;version="1.0";uses:="org.osgi.dto",org.osgi.framework.wiring;version="1.2";uses:="org.osgi.framework,org.osgi.resource",org.osgi.framework.wiring.dto;version="1.2";uses:="org.osgi.dto,org.osgi.resource.dto",org.osgi.service.condpermadmin;version="1.1.1";uses:="org.osgi.framework,org.osgi.service.permissionadmin",org.osgi.service.packageadmin;version="1.2";uses:="org.osgi.framework",org.osgi.service.permissionadmin;version="1.2",org.osgi.service.resolver;version="1.0";uses:="org.osgi.resource",org.osgi.service.startlevel;version="1.1";uses:="org.osgi.framework",org.osgi.service.url;version="1.0",org.osgi.util.tracker;version="1.5.1";uses:="org.osgi.framework",org.apache.karaf.version;version="4.2.9",org.apache.karaf.jaas.boot.principal;uses:=javax.security.auth;version="4.2.9",org.apache.karaf.jaas.boot;uses:="javax.security.auth,javax.security.auth.callback,javax.security.auth.login,javax.security.auth.spi,org.osgi.framework";version="4.2.9",org.apache.karaf.info
>>  <http://org.apache.karaf.info/>;version="4.2.9",,org.apache.karaf.branding, 
>> sun.misc, com.sun.jmx.remote.protocol, com.sun.jmx.remote.protocol.jmxmp, 
>> org.apache.karaf.jaas.boot.principal;uses:=javax.security.auth;version=4.2.9,
>>  
>> org.apache.karaf.jaas.boot;uses:="javax.security.auth,javax.security.auth.callback,javax.security.auth.login,javax.security.auth.spi,org.osgi.framework";version=4.2.9,
>>  org.apache.karaf.diagnostic.core;uses:=org.osgi.framework;version=4.2.9, 
>> org.apache.karaf.diagnostic.core.common;uses:=org.apache.karaf.diagnostic.core;version=4.2.9
>> org.osgi.framework.BundleException: Exported package names cannot be zero 
>> length.
>> at 
>> org.apache.felix.framework.util.manifestparser.ManifestParser.normalizeExportClauses(ManifestParser.java:876)
>> at 
>> org.apache.felix.framework.util.manifestparser.ManifestParser.(ManifestParser.java:215)
>> at 
>> org.apache.felix.framework.ExtensionManager.(ExtensionManager.java:261)
>> at org.apache.felix.framework.Felix.(Felix.java:429)
>> at 
>> org.apache.felix.framework.FrameworkFactory.newFramework(FrameworkFactory.java:28)
>> at org.apache.karaf.main.Main.launch(Main.java:256)
>> at org.apache.karaf.main.Main.main(Main.java:178)
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by org.apache.felix.framework.URLHandlers 
>> (file:/Users/ocohen/AppsLocal/Karaf/apache-karaf-4.2.9/system/org/apache/felix/org.apache.felix.framework/5.6.12/org.apache.felix.framework-5.6.12.jar)
>>  to constructor sun.net.www.protocol.file.Handler()
>> WARNING: Please consider reporting this to the maintainers of 
>> org.apache.felix.framework.URLHandlers
>> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future release
>> Error installing bundle listed in startup.properties with url: 
>> mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.9 and 
>> startlevel: 1
>> 
>> 
>> Is there anything I need to do to configure? Is there a problem getting 
>> artifacts?
>> 
>> 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 <mailto:oleg.co...@assurebridge.com>  |  
>> www.assurebridge.com <http://www.assurebridge.com/>

Error starting 4.2.9 with JDK 14.0.1 on Mac

[Oleg Cohen]

Greetings,

I installed a brand new Karaf 4.2.9 and a JDK 14.0.1.

I get the following error starting ./bin/karaf

tcsh% ./bin/karaf
ERROR: Error parsing system bundle export statement:
org.osgi.dto;version="1.0",org.osgi.resource;version="1.0",org.osgi.resource.dto;version="1.0";uses:="org.osgi.dto",org.osgi.framework;version="1.8",org.osgi.framework.dto;version="1.8";uses:="org.osgi.dto",org.osgi.framework.hooks.bundle;version="1.1";uses:="org.osgi.framework",org.osgi.framework.hooks.resolver;version="1.0";uses:="org.osgi.framework.wiring",org.osgi.framework.hooks.service;version="1.1";uses:="org.osgi.framework",org.osgi.framework.hooks.weaving;version="1.1";uses:="org.osgi.framework.wiring",org.osgi.framework.launch;version="1.2";uses:="org.osgi.framework",org.osgi.framework.namespace;version="1.1";uses:="org.osgi.resource",org.osgi.framework.startlevel;version="1.0";uses:="org.osgi.framework",org.osgi.framework.startlevel.dto;version="1.0";uses:="org.osgi.dto",org.osgi.framework.wiring;version="1.2";uses:="org.osgi.framework,org.osgi.resource",org.osgi.framework.wiring.dto;version="1.2";uses:="org.osgi.dto,org.osgi.resource.dto",org.osgi.service.condpermadmin;version="1.1.1";uses:="org.osgi.framework,org.osgi.service.permissionadmin",org.osgi.service.packageadmin;version="1.2";uses:="org.osgi.framework",org.osgi.service.permissionadmin;version="1.2",org.osgi.service.resolver;version="1.0";uses:="org.osgi.resource",org.osgi.service.startlevel;version="1.1";uses:="org.osgi.framework",org.osgi.service.url;version="1.0",org.osgi.util.tracker;version="1.5.1";uses:="org.osgi.framework",org.apache.karaf.version;version="4.2.9",org.apache.karaf.jaas.boot.principal;uses:=javax.security.auth;version="4.2.9",org.apache.karaf.jaas.boot;uses:="javax.security.auth,javax.security.auth.callback,javax.security.auth.login,javax.security.auth.spi,org.osgi.framework";version="4.2.9",
org.apache.karaf.info;version="4.2.9",,org.apache.karaf.branding, sun.misc,
com.sun.jmx.remote.protocol, com.sun.jmx.remote.protocol.jmxmp,
org.apache.karaf.jaas.boot.principal;uses:=javax.security.auth;version=4.2.9,
org.apache.karaf.jaas.boot;uses:="javax.security.auth,javax.security.auth.callback,javax.security.auth.login,javax.security.auth.spi,org.osgi.framework";version=4.2.9,
org.apache.karaf.diagnostic.core;uses:=org.osgi.framework;version=4.2.9,
org.apache.karaf.diagnostic.core.common;uses:=org.apache.karaf.diagnostic.core;version=4.2.9
org.osgi.framework.BundleException: Exported package names cannot be zero
length.
at
org.apache.felix.framework.util.manifestparser.ManifestParser.normalizeExportClauses(ManifestParser.java:876)
at
org.apache.felix.framework.util.manifestparser.ManifestParser.(ManifestParser.java:215)
at
org.apache.felix.framework.ExtensionManager.(ExtensionManager.java:261)
at org.apache.felix.framework.Felix.(Felix.java:429)
at
org.apache.felix.framework.FrameworkFactory.newFramework(FrameworkFactory.java:28)
at org.apache.karaf.main.Main.launch(Main.java:256)
at org.apache.karaf.main.Main.main(Main.java:178)
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.felix.framework.URLHandlers
(file:/Users/ocohen/AppsLocal/Karaf/apache-karaf-4.2.9/system/org/apache/felix/org.apache.felix.framework/5.6.12/org.apache.felix.framework-5.6.12.jar)
to constructor sun.net.www.protocol.file.Handler()
WARNING: Please consider reporting this to the maintainers of
org.apache.felix.framework.URLHandlers
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
Error installing bundle listed in startup.properties with url:
mvn:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.9 and
startlevel: 1


Is there anything I need to do to configure? Is there a problem getting
artifacts?

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 <http://www.assurebridge.com>*

Ignoring servlet [XXX] without valid alias or url patterns property.

[Oleg Cohen]

Greetings,

I am noticing a number of the following INFO messages in my Karaf log:

2020-05-05T05:44:31,551 | INFO  | FelixStartLevel  | ServletWebElement
   | 369 - org.ops4j.pax.web.pax-web-extender-whiteboard - 7.2.14 |
Ignoring servlet [530] without valid alias or url patterns property.

The 530 servlet is this:

530 <http://localhost:8181/system/console/services/530>
[javax.servlet.Servlet]
felix.webconsole.category Status
felix.webconsole.label status-Configurations
felix.webconsole.title Configurations
service.bundleid 218
service.scope bundle
Using Bundles org.ops4j.pax.web.pax-web-extender-whiteboard (369)
<http://localhost:8181/system/console/bundles//369>

Seems harmless, but just wondering what it might mean and if anyone else
noticed these?

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 <http://www.assurebridge.com>*

Re: Camel 3.2.0 install on Karaf 4.2.8

[Oleg Cohen]

Hi JB,

Thank you, it did the trick!

Best,
Oleg

Sent from my iPhone

On Apr 11, 2020, at 1:18 AM, Jean-Baptiste Onofre  wrote:

Hi Oleg,

It’s a known issue in Camel feature.

The artifacts are located in org.apache.camel.karaf now (not directly in
org.apache.camel).

I have a workaround (waiting new Camel feature) in Karaf: you have to add
the following etc/org.apache.karaf.features.xml:

  
   
   

Regards
JB

Le 10 avr. 2020 à 22:39, Oleg Cohen  a écrit :

Greetings,

Not sure if anybody ran into this issue.

I am starting with a brand new instance of Karaf 4.2.8

I added camel and camel-extras repos

feature:repo-add camel
feature:repo-add camel-extras

karaf@root()> feature:repo-list | grep camel
camel-3.2.0   │
mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
camel-extra-2.24.3│
mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
camel-2.24.3  │
mvn:org.apache.camel.karaf/apache-camel/2.24.3/xml/features

When I try to install camel-core I get the following exception:

karaf@root()> feature:install camel
Error executing command: Error:

* Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*
karaf@root()> feature:install camel-core
Error executing command: Error:

* Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*

Seems org.apache.camel/camel-commands-core/3.2.0 is missing.

Would appreciate suggestions!

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 <http://www.assurebridge.com/>*

Re: Camel 3.2.0 install on Karaf 4.2.8

[Oleg Cohen]

Thank you, Freeman!

I missed this one. Looks promising.

Best,
Oleg

Sent from my iPhone

On Apr 10, 2020, at 5:00 PM, Freeman Fang  wrote:


Hi,

This is a known issue caused by karaf related stuff in camel being moved to
camel-karaf sub-project and this already get fixed at camel.

Please take a look at the discussion here
<https://camel.465427.n5.nabble.com/Broken-feature-dependencies-in-3-2-0-td5863188.html>to
get the idea how to workaround this.

Freeman

On Fri, Apr 10, 2020 at 4:40 PM Oleg Cohen 
wrote:

> Greetings,
>
> Not sure if anybody ran into this issue.
>
> I am starting with a brand new instance of Karaf 4.2.8
>
> I added camel and camel-extras repos
>
> feature:repo-add camel
> feature:repo-add camel-extras
>
> karaf@root()> feature:repo-list | grep camel
> camel-3.2.0   │
> mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
> camel-extra-2.24.3│
> mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
> camel-2.24.3  │
> mvn:org.apache.camel.karaf/apache-camel/2.24.3/xml/features
>
> When I try to install camel-core I get the following exception:
>
> karaf@root()> feature:install camel
> Error executing command: Error:
>
> * Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*
> karaf@root()> feature:install camel-core
> Error executing command: Error:
>
> * Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*
>
> Seems org.apache.camel/camel-commands-core/3.2.0 is missing.
>
> Would appreciate suggestions!
>
> 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 <http://www.assurebridge.com>*
>

Camel 3.2.0 install on Karaf 4.2.8

[Oleg Cohen]

Greetings,

Not sure if anybody ran into this issue.

I am starting with a brand new instance of Karaf 4.2.8

I added camel and camel-extras repos

feature:repo-add camel
feature:repo-add camel-extras

karaf@root()> feature:repo-list | grep camel
camel-3.2.0   │
mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
camel-extra-2.24.3│
mvn:org.apache-extras.camel-extra.karaf/camel-extra/RELEASE/xml/features
camel-2.24.3  │
mvn:org.apache.camel.karaf/apache-camel/2.24.3/xml/features

When I try to install camel-core I get the following exception:

karaf@root()> feature:install camel
Error executing command: Error:

* Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*
karaf@root()> feature:install camel-core
Error executing command: Error:

* Error downloading mvn:org.apache.camel/camel-commands-core/3.2.0*

Seems org.apache.camel/camel-commands-core/3.2.0 is missing.

Would appreciate suggestions!

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 <http://www.assurebridge.com>*

Re: paste broken on client console

[Oleg Cohen]

Thank you for the update, JB!

> On Feb 10, 2020, at 2:59 PM, Jean-Baptiste Onofré  wrote:
> 
> Hi
> 
> I already have a fix and I?m looking for a workaround. Anyway a new jline 
> release is required. 
> 
> Regards 
> JB
> 
> Le lun. 10 f?vr. 2020 ? 20:17, Oleg Cohen  a 
> ?crit :
> Hi JB, 
> 
> Sorry to bug on this :-) Is there any idea when you might fix this issue? 
> 
> Thank you! 
> Oleg 
> 
> > On Feb 3, 2020, at 12:23 AM, Jean-Baptiste Onofr?  
> > wrote: 
> > 
> > Hi, 
> > 
> > I found the commit causing issue in jline: 
> > 
> > commit fea903cc9e78da64d66422f07db1b7890cf18b89 
> > Author: Guillaume Nodet  
> > Date: Mon Nov 25 20:45:30 2019 +0100 
> > 
> > Improve performances when pasting huge strings, fixes #479 
> > 
> > I will fix that and cut a new jline release. 
> > 
> > Regards 
> > JB 
> > 
> > On 02/02/2020 11:24, Markus Rathgeb wrote: 
> >> Hi JB, 
> >> 
> >> thanks for keeping us up to date. 
> >> I subscribed to the jline release notification, so I can update my 
> >> custom distributions to jline 3.13.4 if released. 
> >> 
> >> Thanks! 
> >> 
> >> Best regards, 
> >> Markus 
> >> 
> > 
> > -- 
> > Jean-Baptiste Onofr? 
> > jbono...@apache.org 
> > http://blog.nanthrax.net 
> > Talend - http://www.talend.com 
> 

Re: paste broken on client console

[Oleg Cohen]

Hi JB,

Sorry to bug on this :-) Is there any idea when you might fix this issue?

Thank you!
Oleg

> On Feb 3, 2020, at 12:23 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi,
> 
> I found the commit causing issue in jline:
> 
> commit fea903cc9e78da64d66422f07db1b7890cf18b89
> Author: Guillaume Nodet 
> Date:   Mon Nov 25 20:45:30 2019 +0100
> 
>Improve performances when pasting huge strings, fixes #479
> 
> I will fix that and cut a new jline release.
> 
> Regards
> JB
> 
> On 02/02/2020 11:24, Markus Rathgeb wrote:
>> Hi JB,
>> 
>> thanks for keeping us up to date.
>> I subscribed to the jline release notification, so I can update my
>> custom distributions to jline 3.13.4 if released.
>> 
>> Thanks!
>> 
>> Best regards,
>> Markus
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: paste broken on client console

[Oleg Cohen]

Hi guys,

I noticed the same issue with 4.2.8 (works fine in 4.2.7 and prior). I am on a 
Mac. ITerm2 v3.3.7. My $TERM = xterm.

Thank you,
Oleg

> On Jan 31, 2020, at 5:01 AM, Markus Rathgeb  wrote:
> 
> Hi,
> 
> I updated targets running a custom distribution to Karaf 4.2.8.
> Now while maintaining that systems I realized a very annoying problem.
> The copy and paste (to be precise, the "paste") is not working using
> "bin/client" correctly.
> 
> The problem can be reproduced using the upstream Karaf distribution, too.
> I am using a Linux system (host machine + target machines).
> 
> To reproduce:
> * unpack Karaf 4.2.8
> * start the Karaf process by "bin/karaf"
> * open another terminal and connect to the instance using "bin/client"
> * copy a text and paste it into the terminal running "bin/client"
> 
> Result:
> * the text will not appear
> * on enter no new line will be visible
> * to escape the situation paste again or press ctrl+C
> 
> Using the pasted text does not work for me correctly.
> 
> That's a little bit annoying, because I cannot connect to the running
> instance and paste commands and arguments... I need to type all the
> long arguments list manually.
> 
> Can I set a special environment variable to a special value (e.g. TERM
> or LC_COLORS) that works around the problem?
> 
> Best regads,
> Markus

Re: A 'Matched URI can't use version ranges:' warning with 4.2.8

[Oleg Cohen]

Hi JB,

Thank you for a quick response!

Best,
Oleg

> On Jan 24, 2020, at 7:09 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi Oleg,
> 
> That's just a warning saying that the URI will take the first version
> found (which is not maybe what you want in the range).
> I'm working on an improvement about this, but don't worry, most of the
> time it works.
> 
> I just know that this kind of range cause a stack overflow exception on
> Windows platform (working on a fix about that).
> 
> Regards
> JB
> 
> On 24/01/2020 13:01, Oleg Cohen wrote:
>> Greetings!
>> 
>> I am trying the newly released 4.2.8 and I noticed the following warning
>> in my Karaf log:
>> 
>> 2020-01-24T06:57:08,591 | WARN  | activator-1-thread-2 | LocationPattern
>>  | 11 - org.apache.karaf.features.core - 4.2.8 |
>> *Matched URI can't use version ranges:
>> mvn:org.apache.karaf.features/standard/[4,5)/xml/features*
>> *
>> *
>> I am wondering what it means and if there is anything wrong with my setup?
>> 
>> Thank you,
>> Oleg
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

A 'Matched URI can't use version ranges:' warning with 4.2.8

[Oleg Cohen]

Greetings!

I am trying the newly released 4.2.8 and I noticed the following warning in my 
Karaf log:

2020-01-24T06:57:08,591 | WARN  | activator-1-thread-2 | LocationPattern
  | 11 - org.apache.karaf.features.core - 4.2.8 | Matched URI can't use 
version ranges: mvn:org.apache.karaf.features/standard/[4,5)/xml/features

I am wondering what it means and if there is anything wrong with my setup?

Thank you,
Oleg

Re: Aries jax-rs whiteboard

[Oleg Cohen]

Hi Matthias,

I was in the same situation. Here is what I ended up doing. Perhaps it will 
work for you.

Here is my code:

import java.util.HashSet;
import java.util.Set;

import javax.ws.rs.core.Application;

import org.apache.logging.log4j.Logger;
import org.osgi.service.component.annotations.Activate;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.jaxrs.whiteboard.propertytypes.JaxrsApplicationBase;
import org.osgi.service.jaxrs.whiteboard.propertytypes.JaxrsName;

import com.fasterxml.jackson.annotation.JsonInclude.Include;
import com.fasterxml.jackson.databind.DeserializationFeature;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.fasterxml.jackson.databind.SerializationFeature;
import com.fasterxml.jackson.jaxrs.json.JacksonJsonProvider;

@Component(service = Application.class)
@JaxrsApplicationBase(“my-app")
@JaxrsName(“MyApplication")
public class MyApplication extends Application {

private static final Logger logger = 
org.apache.logging.log4j.LogManager.getLogger(MyApplication.class);

private JacksonJsonProvider jsonProvider;

@Activate
private void activate() {

logger.info(“MyApplication.activate(): Entry ...");

ObjectMapper objectMapper = new ObjectMapper();

objectMapper = new ObjectMapper();

objectMapper.setSerializationInclusion(Include.NON_NULL);


objectMapper.configure(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS, false);


objectMapper.configure(DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE,
 false);

jsonProvider = new JacksonJsonProvider(objectMapper);

logger.info(“MyApplication.activate(): jsonProvider = " + 
jsonProvider);
}

@Override
public Set getSingletons() {

Set singletons = new HashSet<>();

singletons.add(jsonProvider);

return singletons;
}
}


> On Nov 15, 2019, at 10:26 AM, Matthias Leinweber  
> wrote:
> 
> Ok that is something i already tried. But i don't want to use a own 
> MessageWriter/Reader. I just want to use the one provided by aries-http 
> whiteboard:
> [javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter]
> --
>  jackson.jaxb.version = 2.9.6
>  jackson.jaxrs.json.version = 2.9.6
>  osgi.jaxrs.extension = true
>  osgi.jaxrs.media.type = application/json
>  osgi.jaxrs.name  = jaxb-json
>  service.bundleid = 46
>  service.id  = 170
>  service.ranking = -2147483648
>  service.scope = prototype
> Provided by : 
>  Apache Aries JAX-RS JAX-RS Jackson (46)
> Used by: 
>  Apache Aries JAX-RS Whiteboard (47)
> 
> But something is wrong...
> 
> My components are configured this way...
> 
> @Component(
> service = Application.class,
> property = {
>   "osgi.jaxrs.name =MyApp",
>   "osgi.jaxrs.application.base=/app",
>   
> "osgi.jaxrs.whiteboard.target=(service.pid=org.apache.aries.jax.rs.whiteboard.default)",
>   //"osgi.jaxrs.extension.select=(osgi.jaxrs.name 
> =jaxb-json)" <- i tried it also here
> })
> public class MyApp extends Application {}
> 
> @Path("/service")
> @Component(
> service = MyService.class,
> property = {
>   "osgi.jaxrs.resource=true",
>   "osgi.jaxrs.application.select=(osgi.jaxrs.name 
> =MyApp)",
>   "osgi.jaxrs.extension.select=(osgi.jaxrs.name 
> =jaxb-json)" <- with this line the complete karaf 
> installation is not responding
> })
> public class MyService ...
> 
> Am Fr., 15. Nov. 2019 um 11:47 Uhr schrieb Tim Ward  >:
> Hi Matthias,
> 
> So it sounds as though you’re in the following situation:
> Providing a custom Application to the whiteboard
> The application service has the property osgi.jaxrs.name 
>  = MyApp set on the service registration
> Your application needs, but does not contain, JSON serialisation support
> You want to use an external MessageBodyReader and MessageBodyWriter service 
> to extend your application
> 
> Assuming that these are correct then:
> 
> Your Application needs to tell the whiteboard that it is missing some 
> required extensions. This will prevent it being deployed until the extension 
> is available. See the details of the osgi.jaxrs.extension.select 
> 
>  property which will need to match service properties on your whiteboard 
> extension
> Your external MessageBodyReader and MessageBodyWriter will need to be 
> registered with
> The service has the property 

Re: Create my own Whiteboard/Application with extensions

[Oleg Cohen]

Hi JB,

Thank you for replying! Yes, there is an example of whiteboard, but the
resource is using the default one. Unless I missed something.

Best,
Oleg

On Wed, Oct 30, 2019 at 5:10 AM  wrote:

> Hi
>
> There's also an example in the karaf-rest-example.
>
> Regards
> JB
>
> Le 30 oct. 2019 08:36, Christian Schneider  a
> écrit :
>
> I created an example of an application that uses jax-rs-whiteboard.
>
>
> https://github.com/cschneider/osgi-best-practices/blob/master/backend/src/main/java/net/lr/tasklist/resource/TaskResource.java
>
> It uses the jackson extension. As you see the only thing you need in your
> code is this:
> @Component(service = TaskResource.class)
> @JaxrsResource
> @Produces(MediaType.APPLICATION_JSON)
> @JSONRequired
> @Path("tasks")
>
> Alternatively you can also publish a jax-rs Application as an OSGi service
> but I did not try this.
>
> Christian
>
> Am Mi., 30. Okt. 2019 um 01:36 Uhr schrieb Oleg Cohen <
> oleg.co...@assurebridge.com>:
>
> Greetings,
>
> I am using Aries HTTP Whiteboard in Karaf 4.2.7. All is working fine with
> the default Whiteboard instance. I would like to create my own Jax-RS
> Application with the same extensions that are configured in the default
> Whiteboard, for example jaxb-json one. Is there a convenient way to clone
> the default Whiteboard or create a fully-featured Application?
>
> I would appreciate any guidance in this!
>
> Thank you,
> Oleg
>
>
>
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>
>
>

-- 
*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 <http://www.assurebridge.com>*

Create my own Whiteboard/Application with extensions

[Oleg Cohen]

Greetings,

I am using Aries HTTP Whiteboard in Karaf 4.2.7. All is working fine with
the default Whiteboard instance. I would like to create my own Jax-RS
Application with the same extensions that are configured in the default
Whiteboard, for example jaxb-json one. Is there a convenient way to clone
the default Whiteboard or create a fully-featured Application?

I would appreciate any guidance in this!

Thank you,
Oleg

Re: Hazelcast and Spring 5

[Oleg Cohen]

I have tried ... I think the issue is that even the latest version of
hazelcast (3.11.2) still only imports up to Spring 4

org.springframework.security.core.session;resolution:=optional;version="[3.2,4)"

On Wed, Apr 3, 2019 at 4:15 AM Oleg Cohen 
wrote:

> Where can I see what is included in the hazelcast feature? I can try to
> load/wrap the bundles in my own feature, but I think cellar would still
> pull 3.9.1 as a dependency.
>
> On Wed, Apr 3, 2019 at 4:12 AM Jean-Baptiste Onofré 
> wrote:
>
>> By the way, you can try a wrap on hazelcast to change the import, that
>> could work.
>>
>> Regards
>> JB
>>
>> On 03/04/2019 10:06, Oleg Cohen wrote:
>> > Greetings,
>> >
>> > I am using Hazelcast for HTTP session clustering. As I use Spring
>> > Security I need to use com.hazelcast.web.spring.SpringAwareWebFilter
>> > instead of com.hazelcast.web.WebFilter.
>> >
>> > The spring-aware filter needs the
>> > org.springframework.security.web.session package. I am using Spring
>> > Security 5, but the current hazelcast bundle (3.9.1) doesn't go above
>> > version 4
>> >
>> (org.springframework.security.web.session;resolution:=optional;version="[3.2,4)")
>> >
>> > Is there any way to get a revised one that would work with Spring and
>> > Spring Security 5?
>> >
>> > Thank you!
>> > Oleg
>> >
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
> --
> *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 <http://www.assurebridge.com>*
>


-- 
*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 <http://www.assurebridge.com>*

Re: Hazelcast and Spring 5

[Oleg Cohen]

Where can I see what is included in the hazelcast feature? I can try to
load/wrap the bundles in my own feature, but I think cellar would still
pull 3.9.1 as a dependency.

On Wed, Apr 3, 2019 at 4:12 AM Jean-Baptiste Onofré  wrote:

> By the way, you can try a wrap on hazelcast to change the import, that
> could work.
>
> Regards
> JB
>
> On 03/04/2019 10:06, Oleg Cohen wrote:
> > Greetings,
> >
> > I am using Hazelcast for HTTP session clustering. As I use Spring
> > Security I need to use com.hazelcast.web.spring.SpringAwareWebFilter
> > instead of com.hazelcast.web.WebFilter.
> >
> > The spring-aware filter needs the
> > org.springframework.security.web.session package. I am using Spring
> > Security 5, but the current hazelcast bundle (3.9.1) doesn't go above
> > version 4
> >
> (org.springframework.security.web.session;resolution:=optional;version="[3.2,4)")
> >
> > Is there any way to get a revised one that would work with Spring and
> > Spring Security 5?
> >
> > Thank you!
> > Oleg
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>


-- 
*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 <http://www.assurebridge.com>*

Re: Hazelcast and Spring 5

[Oleg Cohen]

Thank you, JB!

On Wed, Apr 3, 2019 at 4:11 AM Jean-Baptiste Onofré  wrote:

> Hi Oleg,
>
> I will extend the range and test it (that's part of Cellar).
>
> Regards
> JB
>
> On 03/04/2019 10:06, Oleg Cohen wrote:
> > Greetings,
> >
> > I am using Hazelcast for HTTP session clustering. As I use Spring
> > Security I need to use com.hazelcast.web.spring.SpringAwareWebFilter
> > instead of com.hazelcast.web.WebFilter.
> >
> > The spring-aware filter needs the
> > org.springframework.security.web.session package. I am using Spring
> > Security 5, but the current hazelcast bundle (3.9.1) doesn't go above
> > version 4
> >
> (org.springframework.security.web.session;resolution:=optional;version="[3.2,4)")
> >
> > Is there any way to get a revised one that would work with Spring and
> > Spring Security 5?
> >
> > Thank you!
> > Oleg
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>


-- 
*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 <http://www.assurebridge.com>*

Hazelcast and Spring 5

[Oleg Cohen]

Greetings,

I am using Hazelcast for HTTP session clustering. As I use Spring Security
I need to use com.hazelcast.web.spring.SpringAwareWebFilter instead
of com.hazelcast.web.WebFilter.

The spring-aware filter needs the org.springframework.security.web.session
package. I am using Spring Security 5, but the current hazelcast bundle
(3.9.1) doesn't go above version 4
(org.springframework.security.web.session;resolution:=optional;version="[3.2,4)")

Is there any way to get a revised one that would work with Spring and
Spring Security 5?

Thank you!
Oleg

Re: HTTP Session Clustering

[Oleg Cohen]

Another quick update:

Adding this to my pom.xml:

*

solved the issue. So, I am missing an import, just not sure which one.

Here are my imports:


org.apache.logging.log4j;version='[2.8.0,3.0.0)';provider=paxlogging,

org.apache.logging.log4j.message;version='[2.8.0,3.0.0)';provider=paxlogging,

org.apache.logging.log4j.spi;version='[2.8.0,3.0.0)';provider=paxlogging,

org.apache.logging.log4j.util;version='[2.8.0,3.0.0)';provider=paxlogging,


org.slf4j;version='[1.7.0,1.8.0)';provider=paxlogging,


javax.servlet;version='[2.5,3.2)',

javax.servlet.http;version='[2.5,3.2)',
javax.servlet.jsp,

javax.servlet.jsp.tagext,

com.hazelcast.web


Thank you,
Oleg

> On Apr 2, 2019, at 6:02 AM, Oleg Cohen  wrote:
> 
> Hi JB,
> 
> Wanted to provide a quick update. My ultimate environment is pretty complex 
> with a lot of bundles and XML-related components. To eliminate these 
> dependencies I started with a plain vanilla karaf, installed cellar, and 
> built a very simple WAB.
> 
> The behavior is different, it looks better, but I have a different issue now. 
> When the application start and session clustering is initialized I get the 
> following exception that persists and keeps being thrown:
> 
> 2019-04-02T05:59:49,475 | ERROR | hz._hzInstance_1_cellar.IO.thread-in-1 | 
> NodeEngine   | 111 - com.hazelcast - 3.9.1 | 
> [127.0.0.1]:5702 [cellar] [3.9.1] Failed to process:Packet{partitionId=-1, 
> conn=Connection[id=2, /127.0.0.1:5702->/127.0.0.1:64100, endpoint=null, 
> alive=true, type=MEMBER], rawFlags=10, isUrgent=false, packetType=BIND, 
> typeSpecificFlags=}
> com.hazelcast.nio.serialization.HazelcastSerializationException: No 
> DataSerializerFactory registered for namespace: 0
>   at 
> com.hazelcast.internal.serialization.impl.DataSerializableSerializer.readInternal(DataSerializableSerializer.java:137)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.serialization.impl.DataSerializableSerializer.read(DataSerializableSerializer.java:105)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.serialization.impl.DataSerializableSerializer.read(DataSerializableSerializer.java:50)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.serialization.impl.StreamSerializerAdapter.read(StreamSerializerAdapter.java:48)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.serialization.impl.AbstractSerializationService.toObject(AbstractSerializationService.java:185)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.nio.tcp.TcpIpConnectionManager.handle(TcpIpConnectionManager.java:213)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.spi.impl.NodeEngineImpl$ConnectionManagerPacketHandler.handle(NodeEngineImpl.java:199)
>  ~[111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.spi.impl.PacketDispatcher.handle(PacketDispatcher.java:73) 
> [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.nio.tcp.MemberChannelInboundHandler.handlePacket(MemberChannelInboundHandler.java:71)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.nio.tcp.MemberChannelInboundHandler.onRead(MemberChannelInboundHandler.java:54)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.networking.nio.NioChannelReader.handle(NioChannelReader.java:138)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.networking.nio.NioThread.handleSelectionKey(NioThread.java:401)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.networking.nio.NioThread.handleSelectionKeys(NioThread.java:386)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:293)
>  [111:com.hazelcast:3.9.1]
>   at 
> com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:248) 
> [111:com.hazelcast:3.9.1]
> 
> Let me know if you have any thoughts on what is happening.
> 
> I will investigate separately on what in my bundles might have been cuasing 
> the original exception.
> 
> Thank you,
> Oleg
> 
>> On Apr 1, 2019, at 9:57 AM, Jean-Baptiste Onofré > <mailto:j...@nanthrax.net>> wrote:
>> 
>> Thanks 

Re: HTTP Session Clustering

[Oleg Cohen]

Hi JB,

Wanted to provide a quick update. My ultimate environment is pretty complex 
with a lot of bundles and XML-related components. To eliminate these 
dependencies I started with a plain vanilla karaf, installed cellar, and built 
a very simple WAB.

The behavior is different, it looks better, but I have a different issue now. 
When the application start and session clustering is initialized I get the 
following exception that persists and keeps being thrown:

2019-04-02T05:59:49,475 | ERROR | hz._hzInstance_1_cellar.IO.thread-in-1 | 
NodeEngine   | 111 - com.hazelcast - 3.9.1 | 
[127.0.0.1]:5702 [cellar] [3.9.1] Failed to process:Packet{partitionId=-1, 
conn=Connection[id=2, /127.0.0.1:5702->/127.0.0.1:64100, endpoint=null, 
alive=true, type=MEMBER], rawFlags=10, isUrgent=false, packetType=BIND, 
typeSpecificFlags=}
com.hazelcast.nio.serialization.HazelcastSerializationException: No 
DataSerializerFactory registered for namespace: 0
at 
com.hazelcast.internal.serialization.impl.DataSerializableSerializer.readInternal(DataSerializableSerializer.java:137)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.serialization.impl.DataSerializableSerializer.read(DataSerializableSerializer.java:105)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.serialization.impl.DataSerializableSerializer.read(DataSerializableSerializer.java:50)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.serialization.impl.StreamSerializerAdapter.read(StreamSerializerAdapter.java:48)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.serialization.impl.AbstractSerializationService.toObject(AbstractSerializationService.java:185)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.nio.tcp.TcpIpConnectionManager.handle(TcpIpConnectionManager.java:213)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.spi.impl.NodeEngineImpl$ConnectionManagerPacketHandler.handle(NodeEngineImpl.java:199)
 ~[111:com.hazelcast:3.9.1]
at 
com.hazelcast.spi.impl.PacketDispatcher.handle(PacketDispatcher.java:73) 
[111:com.hazelcast:3.9.1]
at 
com.hazelcast.nio.tcp.MemberChannelInboundHandler.handlePacket(MemberChannelInboundHandler.java:71)
 [111:com.hazelcast:3.9.1]
at 
com.hazelcast.nio.tcp.MemberChannelInboundHandler.onRead(MemberChannelInboundHandler.java:54)
 [111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.networking.nio.NioChannelReader.handle(NioChannelReader.java:138)
 [111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.networking.nio.NioThread.handleSelectionKey(NioThread.java:401)
 [111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.networking.nio.NioThread.handleSelectionKeys(NioThread.java:386)
 [111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.networking.nio.NioThread.selectLoop(NioThread.java:293) 
[111:com.hazelcast:3.9.1]
at 
com.hazelcast.internal.networking.nio.NioThread.run(NioThread.java:248) 
[111:com.hazelcast:3.9.1]

Let me know if you have any thoughts on what is happening.

I will investigate separately on what in my bundles might have been cuasing the 
original exception.

Thank you,
Oleg

> On Apr 1, 2019, at 9:57 AM, Jean-Baptiste Onofré  wrote:
> 
> Thanks for the update.
> 
> It could be related to the karaf xml spec we added in lib/endorsed.
> 
> Let me check and try to reproduce.
> 
> Regards
> JB
> 
> On 01/04/2019 15:47, Oleg Cohen wrote:
>> Hi JB,
>> 
>> Thank you for replying!
>> 
>> Karaf: 4.2.4
>> JDK: 8u202
>> 
>> Standard distribution. I have a feature that has the required features
>> in the doc listed as dependencies:
>> 
>> 
>> http
>> http-whiteboard
>> 
>> cellar
>> 
>> Thank you,
>> Oleg
>> 
>> 
>> 
>> 
>>> On Apr 1, 2019, at 9:40 AM, Jean-Baptiste Onofré >> <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>>> wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> Is cellar feature installed correctly (providing the hazelcast instance) ?
>>> 
>>> What Karaf version are you using ? Is it a custom distro ?
>>> 
>>> Regards
>>> JB
>>> 
>>> On 01/04/2019 15:37, Oleg Cohen wrote:
>>>> Greetings,
>>>> 
>>>> I wonder if anybody ran into a similar issue. I followed the setup
>>>> instructions
>>>> here: 
>>>> https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication
>>>> 
>>>> Now that Karaf runs I am seeing this exception:
>>>> 
>>>> 2019-04-01T09:31:09,489 | INFO  | .hazelcast-wm.ensureInstance |
>>>> ClusteredSessionService  | 68 - com.hazelcast - 3.9.1 | Retrying
>>>> the connection!!
>>>> 

Re: HTTP Session Clustering

[Oleg Cohen]

Hi JB,

Thank you for replying!

Karaf: 4.2.4
JDK: 8u202

Standard distribution. I have a feature that has the required features in the 
doc listed as dependencies:


http
http-whiteboard

cellar

Thank you,
Oleg




> On Apr 1, 2019, at 9:40 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi Oleg,
> 
> Is cellar feature installed correctly (providing the hazelcast instance) ?
> 
> What Karaf version are you using ? Is it a custom distro ?
> 
> Regards
> JB
> 
> On 01/04/2019 15:37, Oleg Cohen wrote:
>> Greetings,
>> 
>> I wonder if anybody ran into a similar issue. I followed the setup
>> instructions
>> here: 
>> https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication
>> 
>> Now that Karaf runs I am seeing this exception:
>> 
>> 2019-04-01T09:31:09,489 | INFO  | .hazelcast-wm.ensureInstance |
>> ClusteredSessionService  | 68 - com.hazelcast - 3.9.1 | Retrying
>> the connection!!
>> 2019-04-01T09:31:09,490 | INFO  | .hazelcast-wm.ensureInstance |
>> HazelcastInstanceLoader  | 68 - com.hazelcast - 3.9.1 | Creating
>> a new HazelcastInstance for session replication
>> 2019-04-01T09:31:09,492 | WARN  | .hazelcast-wm.ensureInstance |
>> ClusteredSessionService  | 68 - com.hazelcast - 3.9.1 | Cannot
>> connect to Hazelcast server: XPathFactory#newInstance() failed to create
>> an XPathFactory for the default object model:
>> http://java.sun.com/jaxp/xpath/dom with the
>> XPathFactoryConfigurationException: java.util.ServiceConfigurationError:
>> javax.xml.xpath.XPathFactory: Provider
>> org.apache.xpath.jaxp.XPathFactoryImpl not found
>> 
>> I would appreciate suggestions on how to fix this.
>> 
>> Thank you,
>> Oleg
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

HTTP Session Clustering

[Oleg Cohen]

Greetings,

I wonder if anybody ran into a similar issue. I followed the setup instructions 
here: 
https://karaf.apache.org/manual/cellar/latest-4/#_enable_cluster_http_session_replication
 


Now that Karaf runs I am seeing this exception:

2019-04-01T09:31:09,489 | INFO  | .hazelcast-wm.ensureInstance | 
ClusteredSessionService  | 68 - com.hazelcast - 3.9.1 | Retrying the 
connection!!
2019-04-01T09:31:09,490 | INFO  | .hazelcast-wm.ensureInstance | 
HazelcastInstanceLoader  | 68 - com.hazelcast - 3.9.1 | Creating a new 
HazelcastInstance for session replication
2019-04-01T09:31:09,492 | WARN  | .hazelcast-wm.ensureInstance | 
ClusteredSessionService  | 68 - com.hazelcast - 3.9.1 | Cannot connect 
to Hazelcast server: XPathFactory#newInstance() failed to create an 
XPathFactory for the default object model: http://java.sun.com/jaxp/xpath/dom 
with the XPathFactoryConfigurationException: 
java.util.ServiceConfigurationError: javax.xml.xpath.XPathFactory: Provider 
org.apache.xpath.jaxp.XPathFactoryImpl not found

I would appreciate suggestions on how to fix this.

Thank you,
Oleg

Interactive Console/Shell Command

[Oleg Cohen]

Hello,

I was wondering if anybody successfully developed and ran an interactive Karaf 
shell command, i.e. one that prompts the user for input.

I tried to use java.util.Scanner and when it prompts not all characters I type 
are input and when I hit enter it seems the submission happens twice and I get 
Command not found: [my input string]

I would appreciate suggestions!

Regards,
Oleg

Re: Startup timing Windows vs. Mac

[Oleg Cohen]

Hi JB,

Thank you for the clarification. I think the bundle load time on Windows was 
affected by a large number of services in the component. I don’t know exactly 
the reason, but how the OSGi container processes the bundle on startup was much 
slower on Windows because I had a large number of services. I reworked my 
architecture to reduce the number of service components and the startup time 
went down quite a bit.

Thank you,
Oleg 

> On Nov 20, 2018, at 11:55 PM, Jean-Baptiste Onofré  wrote:
> 
> Hi Oleg,
> 
> bundle:update is roughly equivalent to bundle:stop, bundle:uninstall,
> bundle:install, bundle:start. It gets the "new" bundle version from the
> bundle location (that you can see with bundle:list -l).
> 
> Nothing suspicious in the bundle activator that could explain it takes
> time to stop/start on windows ?
> 
> Regards
> JB
> 
> On 21/11/2018 04:36, Oleg Cohen wrote:
>> Hi JB,
>> 
>> I don’t think the antivirus is an issue in my case.
>> 
>> I did disable Windows Defender. My test case is with a single bundle
>> that is installed via this command:
>> 
>> install reference:file://$eclipse_projects/sample.bundle.a 
>> 
>> > >
>> 
>> The location $eclipse_projects points to the local file system where
>> Eclipse projects for bundles reside.
>> 
>> From Active state I run command *update sample.bundle.a*
>> 
>> I see that the entire bundle start part of the update consists of two
>> parts. Right after the activation process starts I see a delay. No
>> logging occurs, even with the log level set to TRACE. Then log output
>> starts showing initialization of my bundle’s components/services.
>> 
>> The latter part runs quick on both Windows and Mac and take about 1 sec.
>> However, the former part that is silent and takes about 5 sec on Mac and
>> 20 sec on Windows. So, 4 times slower on Windows. 
>> 
>> What happens with the bundle at the start? Are files copied? I do
>> suspect it has something to do with the file IO.
>> 
>> Thank you,
>> Oleg
>> 
>> 
>>> On Nov 20, 2018, at 10:57 AM, Jean-Baptiste Onofré >> <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>>> wrote:
>>> 
>>> Yes, first, please try with the antivirus disabled.
>>> 
>>> Regards
>>> JB
>>> 
>>> On 20/11/2018 16:26, Oleg Cohen wrote:
>>>> Hi JB,
>>>> 
>>>> Yes, it is Windows. It is exactly the same set of bundles and the
>>>> same Maven repository. Yes, there is Antivirus. I can try testing
>>>> with disabling it temporarily.
>>>> 
>>>> How can I see what is being resolved/checked/updated/downloaded? I do
>>>> notice that Karaf has these long pauses. I am sure I can run pretty
>>>> much against the local repo.
>>>> 
>>>> I would appreciate any pointers on how to speed up the startup!
>>>> 
>>>> Best regards,
>>>> Oleg
>>>> 
>>>>> On Nov 20, 2018, at 12:12 AM, Jean-Baptiste Onofré >>>> <mailto:j...@nanthrax.net>
>>>>> <mailto:j...@nanthrax.net <mailto:j...@nanthrax.net>>> wrote:
>>>>> 
>>>>> Hi Oleg,
>>>>> 
>>>>> So Windows is longer than Mac (not surprising ;)).
>>>>> 
>>>>> Did you check in term of bundles resolution ? Do the two systems use the
>>>>> same Maven repository and network to resolve the artifacts.
>>>>> 
>>>>> I already saw such issue due to the Windows antivirus: it verified any
>>>>> artifacts downloaded by Karaf and it takes time.
>>>>> 
>>>>> Do you have antivirus on the Windows system ?
>>>>> 
>>>>> Regards
>>>>> JB
>>>>> 
>>>>> On 19/11/2018 21:12, Oleg Cohen wrote:
>>>>>> Greetings,
>>>>>> 
>>>>>> I have two systems: one Mac and one Windows. I have noticed that
>>>>>> exactly the same application with a number of bundles, both 3rd
>>>>>> party and my own, take significantly longer (1.5 vs 6 mins) on
>>>>>> Windows compared to Mac. Both systems are pretty powerful and have
>>>>>> similar resources. I was wondering if anybody has noticed the same.
>>>>>> What would be the best way to analyze the startup performance and
>>>>>> identify bottlenecks?
>>>>>> 
>>>>>> Thank you,
>>>>>> Oleg
>>>>>> 
>>>>> 
>>>>> -- 
>>>>> Jean-Baptiste Onofré
>>>>> jbono...@apache.org <mailto:jbono...@apache.org> 
>>>>> <mailto:jbono...@apache.org <mailto:jbono...@apache.org>>
>>>>> http://blog.nanthrax.net <http://blog.nanthrax.net/>
>>>>> Talend - http://www.talend.com <http://www.talend.com/>
>>>> 
>>> 
>>> -- 
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org <mailto:jbono...@apache.org> 
>>> <mailto:jbono...@apache.org <mailto:jbono...@apache.org>>
>>> http://blog.nanthrax.net <http://blog.nanthrax.net/>
>>> Talend - http://www.talend.com <http://www.talend.com/>
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org <mailto:jbono...@apache.org>
> http://blog.nanthrax.net <http://blog.nanthrax.net/>
> Talend - http://www.talend.com <http://www.talend.com/>

Re: Startup timing Windows vs. Mac

[Oleg Cohen]

I’d like to add that this bundle has many classes and a large number of 
services.

> On Nov 20, 2018, at 10:36 PM, Oleg Cohen  wrote:
> 
> Hi JB,
> 
> I don’t think the antivirus is an issue in my case.
> 
> I did disable Windows Defender. My test case is with a single bundle that is 
> installed via this command:
> 
> install reference:file://$eclipse_projects/sample.bundle.a 
> 
> 
> The location $eclipse_projects points to the local file system where Eclipse 
> projects for bundles reside.
> 
> From Active state I run command update sample.bundle.a
> 
> I see that the entire bundle start part of the update consists of two parts. 
> Right after the activation process starts I see a delay. No logging occurs, 
> even with the log level set to TRACE. Then log output starts showing 
> initialization of my bundle’s components/services.
> 
> The latter part runs quick on both Windows and Mac and take about 1 sec. 
> However, the former part that is silent and takes about 5 sec on Mac and 20 
> sec on Windows. So, 4 times slower on Windows. 
> 
> What happens with the bundle at the start? Are files copied? I do suspect it 
> has something to do with the file IO.
> 
> Thank you,
> Oleg
> 
> 
>> On Nov 20, 2018, at 10:57 AM, Jean-Baptiste Onofré > <mailto:j...@nanthrax.net>> wrote:
>> 
>> Yes, first, please try with the antivirus disabled.
>> 
>> Regards
>> JB
>> 
>> On 20/11/2018 16:26, Oleg Cohen wrote:
>>> Hi JB,
>>> 
>>> Yes, it is Windows. It is exactly the same set of bundles and the same 
>>> Maven repository. Yes, there is Antivirus. I can try testing with disabling 
>>> it temporarily. 
>>> 
>>> How can I see what is being resolved/checked/updated/downloaded? I do 
>>> notice that Karaf has these long pauses. I am sure I can run pretty much 
>>> against the local repo.
>>> 
>>> I would appreciate any pointers on how to speed up the startup!
>>> 
>>> Best regards,
>>> Oleg
>>> 
>>>> On Nov 20, 2018, at 12:12 AM, Jean-Baptiste Onofré >>> <mailto:j...@nanthrax.net>> wrote:
>>>> 
>>>> Hi Oleg,
>>>> 
>>>> So Windows is longer than Mac (not surprising ;)).
>>>> 
>>>> Did you check in term of bundles resolution ? Do the two systems use the
>>>> same Maven repository and network to resolve the artifacts.
>>>> 
>>>> I already saw such issue due to the Windows antivirus: it verified any
>>>> artifacts downloaded by Karaf and it takes time.
>>>> 
>>>> Do you have antivirus on the Windows system ?
>>>> 
>>>> Regards
>>>> JB
>>>> 
>>>> On 19/11/2018 21:12, Oleg Cohen wrote:
>>>>> Greetings,
>>>>> 
>>>>> I have two systems: one Mac and one Windows. I have noticed that exactly 
>>>>> the same application with a number of bundles, both 3rd party and my own, 
>>>>> take significantly longer (1.5 vs 6 mins) on Windows compared to Mac. 
>>>>> Both systems are pretty powerful and have similar resources. I was 
>>>>> wondering if anybody has noticed the same. What would be the best way to 
>>>>> analyze the startup performance and identify bottlenecks?
>>>>> 
>>>>> Thank you,
>>>>> Oleg
>>>>> 
>>>> 
>>>> -- 
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org <mailto:jbono...@apache.org>
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>> 
>> 
>> -- 
>> Jean-Baptiste Onofré
>> jbono...@apache.org <mailto:jbono...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
> 

Re: Startup timing Windows vs. Mac

[Oleg Cohen]

Hi JB,

I don’t think the antivirus is an issue in my case.

I did disable Windows Defender. My test case is with a single bundle that is 
installed via this command:

install reference:file://$eclipse_projects/sample.bundle.a 


The location $eclipse_projects points to the local file system where Eclipse 
projects for bundles reside.

From Active state I run command update sample.bundle.a

I see that the entire bundle start part of the update consists of two parts. 
Right after the activation process starts I see a delay. No logging occurs, 
even with the log level set to TRACE. Then log output starts showing 
initialization of my bundle’s components/services.

The latter part runs quick on both Windows and Mac and take about 1 sec. 
However, the former part that is silent and takes about 5 sec on Mac and 20 sec 
on Windows. So, 4 times slower on Windows. 

What happens with the bundle at the start? Are files copied? I do suspect it 
has something to do with the file IO.

Thank you,
Oleg


> On Nov 20, 2018, at 10:57 AM, Jean-Baptiste Onofré  wrote:
> 
> Yes, first, please try with the antivirus disabled.
> 
> Regards
> JB
> 
> On 20/11/2018 16:26, Oleg Cohen wrote:
>> Hi JB,
>> 
>> Yes, it is Windows. It is exactly the same set of bundles and the same Maven 
>> repository. Yes, there is Antivirus. I can try testing with disabling it 
>> temporarily. 
>> 
>> How can I see what is being resolved/checked/updated/downloaded? I do notice 
>> that Karaf has these long pauses. I am sure I can run pretty much against 
>> the local repo.
>> 
>> I would appreciate any pointers on how to speed up the startup!
>> 
>> Best regards,
>> Oleg
>> 
>>> On Nov 20, 2018, at 12:12 AM, Jean-Baptiste Onofré  
>>> wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> So Windows is longer than Mac (not surprising ;)).
>>> 
>>> Did you check in term of bundles resolution ? Do the two systems use the
>>> same Maven repository and network to resolve the artifacts.
>>> 
>>> I already saw such issue due to the Windows antivirus: it verified any
>>> artifacts downloaded by Karaf and it takes time.
>>> 
>>> Do you have antivirus on the Windows system ?
>>> 
>>> Regards
>>> JB
>>> 
>>> On 19/11/2018 21:12, Oleg Cohen wrote:
>>>> Greetings,
>>>> 
>>>> I have two systems: one Mac and one Windows. I have noticed that exactly 
>>>> the same application with a number of bundles, both 3rd party and my own, 
>>>> take significantly longer (1.5 vs 6 mins) on Windows compared to Mac. Both 
>>>> systems are pretty powerful and have similar resources. I was wondering if 
>>>> anybody has noticed the same. What would be the best way to analyze the 
>>>> startup performance and identify bottlenecks?
>>>> 
>>>> Thank you,
>>>> Oleg
>>>> 
>>> 
>>> -- 
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: Startup timing Windows vs. Mac

[Oleg Cohen]

Hi JB,

Yes, it is Windows. It is exactly the same set of bundles and the same Maven 
repository. Yes, there is Antivirus. I can try testing with disabling it 
temporarily. 

How can I see what is being resolved/checked/updated/downloaded? I do notice 
that Karaf has these long pauses. I am sure I can run pretty much against the 
local repo.

I would appreciate any pointers on how to speed up the startup!

Best regards,
Oleg

> On Nov 20, 2018, at 12:12 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi Oleg,
> 
> So Windows is longer than Mac (not surprising ;)).
> 
> Did you check in term of bundles resolution ? Do the two systems use the
> same Maven repository and network to resolve the artifacts.
> 
> I already saw such issue due to the Windows antivirus: it verified any
> artifacts downloaded by Karaf and it takes time.
> 
> Do you have antivirus on the Windows system ?
> 
> Regards
> JB
> 
> On 19/11/2018 21:12, Oleg Cohen wrote:
>> Greetings,
>> 
>> I have two systems: one Mac and one Windows. I have noticed that exactly the 
>> same application with a number of bundles, both 3rd party and my own, take 
>> significantly longer (1.5 vs 6 mins) on Windows compared to Mac. Both 
>> systems are pretty powerful and have similar resources. I was wondering if 
>> anybody has noticed the same. What would be the best way to analyze the 
>> startup performance and identify bottlenecks?
>> 
>> Thank you,
>> Oleg
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Startup timing Windows vs. Mac

[Oleg Cohen]

Greetings,

I have two systems: one Mac and one Windows. I have noticed that exactly the 
same application with a number of bundles, both 3rd party and my own, take 
significantly longer (1.5 vs 6 mins) on Windows compared to Mac. Both systems 
are pretty powerful and have similar resources. I was wondering if anybody has 
noticed the same. What would be the best way to analyze the startup performance 
and identify bottlenecks?

Thank you,
Oleg

Re: Karaf SSH invalid encoding

[Oleg Cohen]

Got it, thank you!

On Tue, Nov 13, 2018 at 9:42 AM Jean-Baptiste Onofré 
wrote:

> Hi Oleg,
>
> The SNAPSHOT are available on Apache repository:
>
>
> https://repository.apache.org/content/groups/snapshots/org/apache/karaf/apache-karaf/4.2.2-SNAPSHOT/
>
> Regards
> JB
>
> On 13/11/2018 15:40, Oleg Cohen wrote:
> > Hi JB,
> >
> > Having the same issue on Windows under a bash shell window. What is the
> best way to get/install 4.2.2-SNAPSHOT?
> >
> > Thank you!
> > Oleg
> >
> >> On Nov 13, 2018, at 8:08 AM, Jean-Baptiste Onofré 
> wrote:
> >>
> >> Hi,
> >>
> >> Thanks for the update.
> >>
> >> Which Karaf version are you using (especially for the client) ?
> >>
> >> Did you try with 4.2.2-SNAPSHOT as we did a fix around that already ?
> >>
> >> Regards
> >> JB
> >>
> >> On 13/11/2018 12:37, Miroslav Beranič wrote:
> >>> Hi JB,
> >>>
> >>> so I am now back in a mode, that ??? char is printed.
> >>>
> >>> Output is like this:
> >>> karaf@root()> user-list
> >>> #  ? Id  ?
> >>> Email   ? First name   ? MSISDN
> >>>
> ?
> >>> 1  ? bla
> >>> ? ? bla  ?
> >>> 2  ? bla
> >>> ? ? bla  ?
> >>> 3  ? bla ? b...@bla.com
> >>> <mailto:b...@bla.com> ? bla  ?
> >>> 4  ? bla ? b...@bla.com
> >>> <mailto:b...@bla.com> ? bla  ?
> >>>
> >>> Env variables are the same as before:
> >>> karaf@root()> shell:echo
> >>> $LANG
>
>
> >>>
> >>> en_US.UTF-8
> >>> karaf@root()>  shell:echo
> >>> $LC_ALL
>
>
> >>>
> >>> null
> >>> karaf@root()> shell:echo
> >>> $TERM
>
>
> >>>
> >>> xterm-256color
> >>>
> >>>
> >>> Kind Regards,
> >>> Miroslav
> >>>
> >>>
> >>>
> >>>
> >>> V V pon., 12. nov. 2018 ob 10:49 je oseba Miroslav Beranič
> >>> mailto:miroslav.bera...@mibesis.si>>
> napisala:
> >>>
> >>>Hi JB,
> >>>
> >>>I get this ( from Linux shell ):
> >>>
> >>>[mm@mm1 ~]$ echo $LC_ALL
> >>>
> >>>[mm@mm1 ~]$ echo $LANG
> >>>en_US.UTF-8
> >>>[mm@mm1 ~]$ echo $TERM
> >>>xterm-256color
> >>>[mm@mm1 ~]$
> >>>
> >>>From inside Karaf's Shell:
> >>>
> >>>karaf@root()> shell:echo $LANG
> >>>en_US.UTF-8
> >>>karaf@root()> shell:echo $LC_ALL
> >>>null
> >>>karaf@root()> shell:echo $TERM
> >>>xterm-256color
> >>>karaf@root()>
> >>>
> >>>This is when ??? is not present - it is working. I will post back
> >>>when I get/see ??? .
> >>>
> >>>Kind Regards,
> >>>Miroslav
> >>>
> >>>
> >>>
> >>>V V pon., 12. nov. 2018 ob 09:44 je oseba Jean-Baptiste Onofré
> >>>mailto:j...@nanthrax.net>> napisala:
> >>>
> >>>Hi Miroslav,
> >>>
> >>>can you share the LC_ALL, LANG and TERM env variables when you
> >>>have or
> >>>don't have the issue ?
> >>>
> >>>Thanks,
> >>>Regards
> >>>JB
> >>>
> >>>On 12/11/2018 08:33, Miroslav Beranič wrote:
> >>>> Hi all,
> >>>>
> >>>> I have the same issue on Apache Karaf 4.2.2 ( commit
> >>>> da7ae8f76f2db1347200ff6bb4760e4ecbb1b454 ), I get/see ???
> >>>chars ( 95% of
> >>>> the times ) when I redeploy application.
> >>>>
> >>>> Interesting thing is, this is on one instance only running
> >>>RHEL 7.5.
> >>>> Intermediate server environment ( beta server ).
> &g

Re: Karaf SSH invalid encoding

[Oleg Cohen]

Hi JB,

Having the same issue on Windows under a bash shell window. What is the best 
way to get/install 4.2.2-SNAPSHOT?

Thank you!
Oleg

> On Nov 13, 2018, at 8:08 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi,
> 
> Thanks for the update.
> 
> Which Karaf version are you using (especially for the client) ?
> 
> Did you try with 4.2.2-SNAPSHOT as we did a fix around that already ?
> 
> Regards
> JB
> 
> On 13/11/2018 12:37, Miroslav Beranič wrote:
>> Hi JB,
>> 
>> so I am now back in a mode, that ??? char is printed.
>> 
>> Output is like this:
>> karaf@root()> user-list
>> #  ? Id  ?
>> Email   ? First name   ? MSISDN
>> ?
>> 1  ? bla
>> ? ? bla  ?
>> 2  ? bla
>> ? ? bla  ?
>> 3  ? bla ? b...@bla.com
>>  ? bla  ?
>> 4  ? bla ? b...@bla.com
>>  ? bla  ?
>> 
>> Env variables are the same as before:
>> karaf@root()> shell:echo
>> $LANG
>>  
>>
>> 
>> en_US.UTF-8
>> karaf@root()>  shell:echo
>> $LC_ALL  
>>  
>>
>> 
>> null
>> karaf@root()> shell:echo
>> $TERM
>>  
>> 
>> 
>> xterm-256color
>> 
>> 
>> Kind Regards,
>> Miroslav
>> 
>> 
>> 
>> 
>> V V pon., 12. nov. 2018 ob 10:49 je oseba Miroslav Beranič
>> mailto:miroslav.bera...@mibesis.si>> napisala:
>> 
>>Hi JB,
>> 
>>I get this ( from Linux shell ):
>> 
>>[mm@mm1 ~]$ echo $LC_ALL
>> 
>>[mm@mm1 ~]$ echo $LANG
>>en_US.UTF-8
>>[mm@mm1 ~]$ echo $TERM
>>xterm-256color
>>[mm@mm1 ~]$
>> 
>>From inside Karaf's Shell:
>> 
>>karaf@root()> shell:echo $LANG
>>en_US.UTF-8
>>karaf@root()> shell:echo $LC_ALL
>>null
>>karaf@root()> shell:echo $TERM
>>xterm-256color
>>karaf@root()>
>> 
>>This is when ??? is not present - it is working. I will post back
>>when I get/see ??? .
>> 
>>Kind Regards,
>>Miroslav
>> 
>> 
>> 
>>V V pon., 12. nov. 2018 ob 09:44 je oseba Jean-Baptiste Onofré
>>mailto:j...@nanthrax.net>> napisala:
>> 
>>Hi Miroslav,
>> 
>>can you share the LC_ALL, LANG and TERM env variables when you
>>have or
>>don't have the issue ?
>> 
>>Thanks,
>>Regards
>>JB
>> 
>>On 12/11/2018 08:33, Miroslav Beranič wrote:
>>> Hi all,
>>> 
>>> I have the same issue on Apache Karaf 4.2.2 ( commit
>>> da7ae8f76f2db1347200ff6bb4760e4ecbb1b454 ), I get/see ???
>>chars ( 95% of
>>> the times ) when I redeploy application.
>>> 
>>> Interesting thing is, this is on one instance only running
>>RHEL 7.5.
>>> Intermediate server environment ( beta server ).
>>> 
>>> At this time, I solve this with server ( OS ) restart.
>>> 
>>> But if someone has any other observation or hints to fix - I
>>would be
>>> glad to update :)
>>> 
>>> Kind Regards,
>>> Miroslav
>>> 
>>> 
>>> V V pet., 9. nov. 2018 ob 05:42 je oseba Jean-Baptiste Onofré
>>> mailto:j...@nanthrax.net>
>>>> napisala:
>>> 
>>>  Hi Nicolas,
>>> 
>>>  Let me check but AFAIR, null should use the default term
>>encoding of the
>>>  system.
>>> 
>>>  Regards
>>>  JB
>>> 
>>>  On 08/11/2018 14:20, DUTERTRY Nicolas wrote:
>>>  > Hi,
>>>  >
>>>  >  
>>>  >
>>>  > I’m using Karaf 4.2.1 on environments which doesn’t have
>>a UTF-8
>>>  > encoding for instance Windows 10 or AIX with ISO-8859-1
>>encoding.
>>>  >
>>>  > When I open a SSH session with the “client” script or
>>with another SSH
>>>  > client, the non-ascii characters are not displayed
>>correctly.
>>>  >
>>>  > For instance the result of the “bundle:list” command
>>prints “?”
>>>  instead
>>>  > of “|” :
>>>  >
>>>  >  
>>>  >
>>>  > karaf@root()> bundle:list
>>>  >
>>>  > START LEVEL 100 , List Threshold: 50
>>>  >
>>>  > ID ? State  ? Lvl ? Version ? Name
>>>  >
>>>  >
>>>
>> 
>> ?
>>>  >
>>>   

Re: Reload/restart bundle when installed with file://

[Oleg Cohen]

Thank you, JB! This works.

Best,
Oleg

> On Oct 24, 2018, at 11:43 PM, Jean-Baptiste Onofré  wrote:
>
> Hi Oleg,
>
> If the bundle is located in the same location (as I'm assuming as you
> use the eclipse workspace, you can double check with bundle:list -l),
> then simply bundle:update works.
>
> In your case bundle:watch won't work as it's related to maven URL.
>
> So you have to use bundle:update command (generally or with the bundle id).
>
> Regards
> JB
>
>> On 25/10/2018 02:11, Oleg Cohen wrote:
>> Hello,
>>
>> I have a number of bundles that I installed using the following command:
>>
>> install reference:file://$eclipse_worspace_path/bundleA
>> 
>>
>> All works well until I change code and recompile the project in Eclipse.
>> What command should I use to refresh/reload/restart bundleA to pick up
>> the changes?
>>
>> I know there is an option to install by pointing to a JAR file in the
>> maven repo and use bundle:watch, but some of my bundles take a while to
>> be bundled and deploy, especially WAB ones.
>>
>> Thank you,
>> Oleg
>>
>>
>>

Reload/restart bundle when installed with file://

[Oleg Cohen]

Hello,

I have a number of bundles that I installed using the following command:

install reference:file://$eclipse_worspace_path/bundleA 


All works well until I change code and recompile the project in Eclipse. What 
command should I use to refresh/reload/restart bundleA to pick up the changes?

I know there is an option to install by pointing to a JAR file in the maven 
repo and use bundle:watch, but some of my bundles take a while to be bundled 
and deploy, especially WAB ones.

Thank you,
Oleg
 

Re: Command not found: Error in Karaf shell

[Oleg Cohen]

Hi François,

I didn’t notice anything specific, let me try reproduce and grab the log.

Thank you,
Oleg


> On Oct 24, 2018, at 12:25 PM, Francois Papon  
> wrote:
> 
> Hi Oleg,
> 
> Did you have some logs when the error occured ?
> 
> regards,
> 
> François Papon
> fpa...@apache.org
> 
> Le 24/10/2018 à 20:00, Oleg Cohen a écrit :
>> Greetings,
>> 
>> I run Karaf 4.2.1 on Mac in an iTerm2 window from the command line:
>> 
>>> ./bin/karaf debug
>> All works fine, but sometimes, and I can’t determine what leads to it 
>> commands stop working. Name completion works, but when I execute a command, 
>> for example restart 182, I get the following message:
>> 
>> Command not found: restart
>> 
>> I need to stop Karaf and re-launch. I am wondering if anybody ran into a 
>> similar issue and if there is a way to diagnose/troubleshoot the system.
>> 
>> Thank you!
>> Oleg
> 

Command not found: Error in Karaf shell

[Oleg Cohen]

Greetings,

I run Karaf 4.2.1 on Mac in an iTerm2 window from the command line:

> ./bin/karaf debug

All works fine, but sometimes, and I can’t determine what leads to it commands 
stop working. Name completion works, but when I execute a command, for example 
restart 182, I get the following message:

Command not found: restart

I need to stop Karaf and re-launch. I am wondering if anybody ran into a 
similar issue and if there is a way to diagnose/troubleshoot the system.

Thank you!
Oleg

Re: javax.annotation.PostConstruct issue when running with JDK11

[Oleg Cohen]

Thank you, JB!

I got it to work successfully by adding lib/ext jar files to the classpath when 
launching Karaf (-classpath)

Best regards,
Oleg

> On Oct 1, 2018, at 1:42 PM, Jean-Baptiste Onofré  wrote:
> 
> Please let me know if you have any issue.
> 
> By the way, I'm preparing blog post + documentation update about how to
> use Karaf on Java 10/11 and dealing with modules.
> 
> I created a Jira about that:
> 
> https://issues.apache.org/jira/browse/KARAF-5938
> 
> I also plan to add few examples about that (in karaf/examples).
> 
> Regards
> JB
> 
> On 01/10/2018 19:18, Oleg Cohen wrote:
>> Thank you, JB! I will give it a try.
>> 
>> Best
>> Oleg
>> 
>> Sent from my iPhone
>> 
>>> On Oct 1, 2018, at 11:57 AM, Jean-Baptiste Onofré  wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> You can add at Karaf level (in the startup) or via dynamic-import on pax
>>> web.
>>> 
>>> Regards
>>> JB
>>> 
>>>> On 01/10/2018 17:44, Oleg Cohen wrote:
>>>> Thank you, JB!
>>>> 
>>>> In my case it is pax-web that can’t find the class, so I guess I need to 
>>>> add to ext lib. How can I add it? Should I do it at the JDK level or it is 
>>>> a mechanism in Karaf?
>>>> 
>>>> Thank you,
>>>> Oleg
>>>> 
>>>>> On Oct 1, 2018, at 11:33 AM, Jean-Baptiste Onofré  
>>>>> wrote:
>>>>> 
>>>>> Hi Oleg,
>>>>> 
>>>>> Correct, javax.annotation is available up to Java 10 (and even using
>>>>> Java 10, the javax.annotation package has been splitted).
>>>>> 
>>>>> When using Java 11, you have to explicitly install either jsr305 or
>>>>> javax.annotation jar files (it could be as private package of your
>>>>> bundle, or ext lib).
>>>>> 
>>>>> Regards
>>>>> JB
>>>>> 
>>>>>> On 01/10/2018 17:14, Oleg Cohen wrote:
>>>>>> Greetings,
>>>>>> 
>>>>>> I am trying to run my Karaf application under JDK 11. I am getting the 
>>>>>> following exception:
>>>>>> 
>>>>>> Caused by: java.lang.ClassNotFoundException: 
>>>>>> javax.annotation.PostConstruct cannot be found by 
>>>>>> org.ops4j.pax.web.pax-web-jsp_7.2.3
>>>>>> 
>>>>>> It appears that the jigsaw module providing this package is not 
>>>>>> available in JDK 11. The suggestion is to use a dependency.
>>>>>> 
>>>>>> Wondering if anybody ran into this and what a solution/workaround might 
>>>>>> be.
>>>>>> 
>>>>>> Thank you!
>>>>>> Oleg
>>>>>> 
>>>>> 
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbono...@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Re: javax.annotation.PostConstruct issue when running with JDK11

[Oleg Cohen]

Thank you, JB! I will give it a try.

Best
Oleg

Sent from my iPhone

> On Oct 1, 2018, at 11:57 AM, Jean-Baptiste Onofré  wrote:
>
> Hi Oleg,
>
> You can add at Karaf level (in the startup) or via dynamic-import on pax
> web.
>
> Regards
> JB
>
>> On 01/10/2018 17:44, Oleg Cohen wrote:
>> Thank you, JB!
>>
>> In my case it is pax-web that can’t find the class, so I guess I need to add 
>> to ext lib. How can I add it? Should I do it at the JDK level or it is a 
>> mechanism in Karaf?
>>
>> Thank you,
>> Oleg
>>
>>> On Oct 1, 2018, at 11:33 AM, Jean-Baptiste Onofré  wrote:
>>>
>>> Hi Oleg,
>>>
>>> Correct, javax.annotation is available up to Java 10 (and even using
>>> Java 10, the javax.annotation package has been splitted).
>>>
>>> When using Java 11, you have to explicitly install either jsr305 or
>>> javax.annotation jar files (it could be as private package of your
>>> bundle, or ext lib).
>>>
>>> Regards
>>> JB
>>>
>>>> On 01/10/2018 17:14, Oleg Cohen wrote:
>>>> Greetings,
>>>>
>>>> I am trying to run my Karaf application under JDK 11. I am getting the 
>>>> following exception:
>>>>
>>>> Caused by: java.lang.ClassNotFoundException: 
>>>> javax.annotation.PostConstruct cannot be found by 
>>>> org.ops4j.pax.web.pax-web-jsp_7.2.3
>>>>
>>>> It appears that the jigsaw module providing this package is not available 
>>>> in JDK 11. The suggestion is to use a dependency.
>>>>
>>>> Wondering if anybody ran into this and what a solution/workaround might be.
>>>>
>>>> Thank you!
>>>> Oleg
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>

Re: javax.annotation.PostConstruct issue when running with JDK11

[Oleg Cohen]

Thank you, JB!

In my case it is pax-web that can’t find the class, so I guess I need to add to 
ext lib. How can I add it? Should I do it at the JDK level or it is a mechanism 
in Karaf?

Thank you,
Oleg

> On Oct 1, 2018, at 11:33 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi Oleg,
> 
> Correct, javax.annotation is available up to Java 10 (and even using
> Java 10, the javax.annotation package has been splitted).
> 
> When using Java 11, you have to explicitly install either jsr305 or
> javax.annotation jar files (it could be as private package of your
> bundle, or ext lib).
> 
> Regards
> JB
> 
> On 01/10/2018 17:14, Oleg Cohen wrote:
>> Greetings,
>> 
>> I am trying to run my Karaf application under JDK 11. I am getting the 
>> following exception:
>> 
>> Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct 
>> cannot be found by org.ops4j.pax.web.pax-web-jsp_7.2.3
>> 
>> It appears that the jigsaw module providing this package is not available in 
>> JDK 11. The suggestion is to use a dependency.
>> 
>> Wondering if anybody ran into this and what a solution/workaround might be.
>> 
>> Thank you!
>> Oleg 
>> 
> 
> -- 
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

javax.annotation.PostConstruct issue when running with JDK11

[Oleg Cohen]

Greetings,

I am trying to run my Karaf application under JDK 11. I am getting the 
following exception:

Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct 
cannot be found by org.ops4j.pax.web.pax-web-jsp_7.2.3

It appears that the jigsaw module providing this package is not available in 
JDK 11. The suggestion is to use a dependency.

Wondering if anybody ran into this and what a solution/workaround might be.

Thank you!
Oleg 

Re: Sudden NoFileAssignedException during karaf distro build.

[Oleg Cohen]

Hi Erwin,

I ran into the same last night. I guess 3.0.0-M1 is new and has 
issues/incompatibilities with the Karaf plugin. 

The way I fixed it was to define the following in the pluginManagement in the 
pom.xml or a parent pom.xml to force versions 2.5.2 and 2.8.2 for the install 
and deploy plugins respectively:






org.apache.maven.plugins

maven-install-plugin
2.5.2



org.apache.maven.plugins

maven-deploy-plugin
2.8.2



org.apache.karaf.tooling

karaf-maven-plugin

${org.apache.karaf.version}
true





Hope this helps.

Thank you,
Oleg


> On Oct 1, 2018, at 9:49 AM, Erwin Hogeweg  wrote:
> 
> Hi -
> 
> All of a sudden we are getting a maven build this error when building a karaf 
> distribution. This started late yesterday and happens on multiple developer 
> machines but not all. I have nuked my entire .m2 repo and rolled back to a 
> version well before the issue started but I still get the same error.
> 
> We’re kinda scratching our heads here… Has anyone an idea what is going on?
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install 
> (default-install) on project my-distribution: NoFileAssignedException: The 
> packaging plugin for this project did not assign a main file to the project 
> but it has attachments. Change packaging to 'pom'. -> [Help 1]
> 
> Karaf-4.2.0
> Java-1.8.0_92
> Maven-3.5.0
> 
> 
> Thanks,
> 
> Erwin
> 

Re: ***UNCHECKED*** Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

Thank you, JB! Looking forward to trying 4.2.1.

Sent from my iPhone

> On Jul 25, 2018, at 3:15 PM, Jean-Baptiste Onofré  wrote:
>
> Hi Oleg,
>
> that's part of the fix but I also aligned the wrapper conf with the one
> used in  bin/karaf.
>
> Regarding Karaf 4.2.1, it's planned for the end of this week/beginning
> of next week.
>
> Regards
> JB
>
>> On 25/07/2018 19:05, Oleg Cohen wrote:
>> Hi JB,
>>
>> Thank you! For now I actually went into etc/karaf-wrapper.conf and added
>> this one
>>
>> wrapper.java.classpath.3=%KARAF_BASE%/lib/endorsed/*.jar
>>
>> It works good now.
>>
>> BTW, when is the 4.2.1 release scheduled for?
>>
>> Best,
>> Oleg
>>
>>> On Jul 25, 2018, at 10:52 AM, j...@nanthrax.net <mailto:j...@nanthrax.net>
>>> wrote:
>>>
>>> Hi Oleg,
>>>
>>> I fixed on a local branch. Any system using wrapper is impacted (it
>>> doesn't matter if it's Linux or Windows).
>>>
>>> I will create the PR tonight and it will be fixed on master soon.
>>>
>>> Regards
>>> JB
>>>
>>> On Wednesday, July 25, 2018 12:40 CEST, Oleg Cohen
>>> mailto:oleg.co...@assurebridge.com>> wrote:
>>>
>>>>
>>> Same with me on Linux. Only happens with the service wrapper. Is there
>>> a quick fix I can apply aside from copying the jar? I guess I need to
>>> add endorsed libs somehow. JB mentioned it is fixed already. Main branch?
>>>
>>> Thank you,
>>> Oleg
>>>
>>> On Jul 24, 2018, at 3:39 PM, Leschke, Scott >> <mailto:slesc...@medline.com>> wrote:
>>>
>>>> Hi Oleg,
>>>>
>>>>
>>>>
>>>> I’m the person who originally reported the issue that JB is referring
>>>> to.  In my case on Windows, Karaf appears to work fine as well but
>>>> there is that error in the log that only occurs when you start Karaf
>>>> using the service wrapper.
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Scott
>>>>
>>>>
>>>>
>>>> *From:* Oleg Cohen [mailto:oleg.co...@assurebridge.com]
>>>> *Sent:* Tuesday, July 24, 2018 2:01 PM
>>>> *To:* user@karaf.apache.org <mailto:user@karaf.apache.org>
>>>> *Subject:* Re: java.lang.NoClassDefFoundError:
>>>> org/apache/karaf/specs/locator/OsgiLocator when running as Service on
>>>> RedHat 7.5
>>>>
>>>>
>>>>
>>>> Hi JB,
>>>>
>>>>
>>>>
>>>> I am using the wrapper. bin/karaf works fine.
>>>>
>>>>
>>>>
>>>> Thank you!
>>>> Oleg
>>>>
>>>>
>>>> On Jul 24, 2018, at 2:58 PM, Jean-Baptiste Onofré >>> <mailto:j...@nanthrax.net>> wrote:
>>>>
>>>>
>>>>
>>>> Maybe it's related to:
>>>>
>>>> https://issues.apache.org/jira/browse/KARAF-5840 (I already have a fix
>>>> on a local branch)
>>>>
>>>> The problem only occurs when using the wrapper.
>>>>
>>>> @Oleg/Miroslav: do you use wrapper to start Karaf instead of bin/karaf ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 24/07/2018 20:54, Francois Papon wrote:
>>>>
>>>> Hi,
>>>>
>>>> It's weird because I downloaded the binary and after extract it, I can
>>>> see the org.apache.karaf.specs.locator-4.2.0.jar in the lib/endorsed
>>>> directory.
>>>>
>>>> regards,
>>>>
>>>> François Papon
>>>> fpa...@apache.org <mailto:fpa...@apache.org>
>>>>
>>>> Le 24/07/2018 à 22:31, Oleg Cohen a écrit :
>>>>
>>>> Hi Miroslav,
>>>>
>>>> I think I found the issue. You are right a JAR is missing.
>>>>
>>>> I built org.apache.karaf.specs.locator-4.2.0.jar and added it to the
>>>> boot/lib folder and the exception is now gone.
>>>>
>>>> Thank you!
>>>> Oleg
>>>>
>>>>
>>>>
>>>> On Jul 24, 2018, at 11:45 AM, Miroslav Beranič
>>>> >>> <mailto:miroslav.bera...@mibesis.si> <mailto:miroslav.bera...@mibesis.si>>
>>>> wrote:
>>>>
>>>> Hi Oleg,
>>>>
>>>> I've just downloade

Re: Karaf Cellar cluster bundle update propagation

[Oleg Cohen]

Thank you!

Sent from my iPhone

> On Jul 25, 2018, at 3:15 PM, Jean-Baptiste Onofré  wrote:
>
> Thanks for the update, I will test and prepare Cellar 4.1.2 once Karaf
> "Container" 4.2.1 is out.
>
> Regards
> JB
>
>> On 25/07/2018 19:03, Oleg Cohen wrote:
>> Hi JB,
>>
>> Just replied to your previous email.
>>
>> I think the latest versions, Karaf 4.2.0 and Cellar 4.1.1
>>
>> Thank you!
>> Oleg
>>
>>> On Jul 25, 2018, at 10:42 AM, j...@nanthrax.net wrote:
>>>
>>> Hi Oleg,
>>>
>>> which Cellar version are you using (and Karaf version as well) ?
>>>
>>> Bundle update is handled in the Cellar BundleEventHandler:
>>>
>>> (event.getType() == BundleState.UPDATE)
>>>
>>> The problem is then probably located in the BundleSupport#update() method:
>>>
>>> https://github.com/apache/karaf-cellar/blob/master/bundle/src/main/java/org/apache/karaf/cellar/bundle/BundleSupport.java#L130
>>>
>>> Let me try to reproduce. I keep you posted.
>>>
>>> Regards
>>> JB
>>>
>>>> On Wednesday, July 25, 2018 15:57 CEST, Oleg Cohen 
>>>>  wrote:
>>>>
>>>>
>>>> Greetings,
>>>>
>>>> I have a question about how bundle update is handled across a Cellar 
>>>> cluster.
>>>>
>>>> I have three nodes in a Cellar cluster. When I cluster-deploy a bundle on 
>>>> node1 from a Maven repo, it gets correctly and successfully deployed onto 
>>>> node2 and node3.
>>>>
>>>> Later on, I call cluster:bundle-update XXX on node1 and it gets updated 
>>>> correctly on node1, but the update isn’t automatically propagated to nodes 
>>>> 2 and 3. Is this an expected behavior?
>>>>
>>>> Would appreciation clarification/advice!
>>>>
>>>> Best,
>>>> Oleg
>>>>
>>>
>>>
>>>
>>>
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com

***UNCHECKED*** Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

Hi JB,

Thank you! For now I actually went into etc/karaf-wrapper.conf and added this 
one

wrapper.java.classpath.3=%KARAF_BASE%/lib/endorsed/*.jar

It works good now.

BTW, when is the 4.2.1 release scheduled for?

Best,
Oleg

> On Jul 25, 2018, at 10:52 AM, j...@nanthrax.net wrote:
> 
> Hi Oleg,
> 
> I fixed on a local branch. Any system using wrapper is impacted (it doesn't 
> matter if it's Linux or Windows).
> 
> I will create the PR tonight and it will be fixed on master soon.
> 
> Regards
> JB
> 
> On Wednesday, July 25, 2018 12:40 CEST, Oleg Cohen 
>  wrote:
>  
>> 
>>  
> Same with me on Linux. Only happens with the service wrapper. Is there a 
> quick fix I can apply aside from copying the jar? I guess I need to add 
> endorsed libs somehow. JB mentioned it is fixed already. Main branch? 
>  
> Thank you,
> Oleg
> 
> On Jul 24, 2018, at 3:39 PM, Leschke, Scott  <mailto:slesc...@medline.com>> wrote:
>  
>> Hi Oleg,
>>  
>> I’m the person who originally reported the issue that JB is referring to.  
>> In my case on Windows, Karaf appears to work fine as well but there is that 
>> error in the log that only occurs when you start Karaf using the service 
>> wrapper.
>>  
>> Regards,
>> Scott
>>  
>> From: Oleg Cohen [mailto:oleg.co...@assurebridge.com 
>> <mailto:oleg.co...@assurebridge.com>]
>> Sent: Tuesday, July 24, 2018 2:01 PM
>> To: user@karaf.apache.org <mailto:user@karaf.apache.org>
>> Subject: Re: java.lang.NoClassDefFoundError: 
>> org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 
>> 7.5
>>  
>> Hi JB,
>>  
>> I am using the wrapper. bin/karaf works fine.
>>  
>> Thank you!
>> Oleg
>> 
>>  
>> On Jul 24, 2018, at 2:58 PM, Jean-Baptiste Onofré > <mailto:j...@nanthrax.net>> wrote:
>>  
>> Maybe it's related to:
>> 
>> https://issues.apache.org/jira/browse/KARAF-5840 
>> <https://issues.apache.org/jira/browse/KARAF-5840> (I already have a fix
>> on a local branch)
>> 
>> The problem only occurs when using the wrapper.
>> 
>> @Oleg/Miroslav: do you use wrapper to start Karaf instead of bin/karaf ?
>> 
>> Regards
>> JB
>> 
>> On 24/07/2018 20:54, Francois Papon wrote:
>>  
>> Hi,
>> 
>> It's weird because I downloaded the binary and after extract it, I can
>> see the org.apache.karaf.specs.locator-4.2.0.jar in the lib/endorsed
>> directory.
>> 
>> regards,
>> 
>> François Papon
>> fpa...@apache.org <mailto:fpa...@apache.org>
>> 
>> Le 24/07/2018 à 22:31, Oleg Cohen a écrit :
>>  
>> Hi Miroslav,
>> 
>> I think I found the issue. You are right a JAR is missing.
>> 
>> I built org.apache.karaf.specs.locator-4.2.0.jar and added it to the
>> boot/lib folder and the exception is now gone.
>> 
>> Thank you!
>> Oleg
>> 
>> 
>>  
>> On Jul 24, 2018, at 11:45 AM, Miroslav Beranič
>> mailto:miroslav.bera...@mibesis.si> 
>> <mailto:miroslav.bera...@mibesis.si <mailto:miroslav.bera...@mibesis.si>>> 
>> wrote:
>> 
>> Hi Oleg,
>> 
>> I've just downloaded package from:
>> 
>> http://karaf.apache.org/download.html <http://karaf.apache.org/download.html>
>> Binary Distribution : tar.gz [PGP] [SHA512]
>> 
>> I've downloaded to /opt/ folder and unpacked the package.
>> 
>> I am using RHEL 7.5, Oracle Java 8 ( 1.8.0.172 )
>> 
>> Next I've started Karf with:
>> 
>> [root@framework apache-karaf-4.2.0]# ls -al
>> total 424
>> drwxr-xr-x. 9 root root156 jul 24 17:35 .
>> drwxr-xr-x. 4 root root110 jul 24 17:35 ..
>> drwxr-xr-x. 3 root root282 apr  5 06:29 bin
>> drwxr-xr-x. 3 root root 17 apr  5 06:29 data
>> drwxr-xr-x. 9 root root123 apr  5 06:29 demos
>> drwxr-xr-x. 2 root root 20 apr  5 06:29 deploy
>> drwxr-xr-x. 3 root root   4096 apr  5 06:29 etc
>> drwxr-xr-x. 5 root root 59 apr  5 06:29 lib
>> -rw-r--r--. 1 root root  27754 apr  5 06:29 LICENSE
>> -rw-r--r--. 1 root root   1829 apr  5 06:29 NOTICE
>> -rw-r--r--. 1 root root   4025 apr  5 06:29 README
>> -rw-r--r--. 1 root root 390829 apr  5 06:29 RELEASE-NOTES
>> drwxr-xr-x. 3 root root 31 apr  5 06:29 system
>> [root@framework apache-karaf-4.2.0]# JAVA_HOME=/opt/jdk ./bin/karaf debug
>> Listening for transport dt_socket at address: 5005
>> __ __    
>>/ //_/ __ _/ __/ 

Re: Karaf Cellar cluster bundle update propagation

[Oleg Cohen]

Hi JB,

Just replied to your previous email.

I think the latest versions, Karaf 4.2.0 and Cellar 4.1.1

Thank you!
Oleg

> On Jul 25, 2018, at 10:42 AM, j...@nanthrax.net wrote:
> 
> Hi Oleg,
> 
> which Cellar version are you using (and Karaf version as well) ?
> 
> Bundle update is handled in the Cellar BundleEventHandler:
> 
> (event.getType() == BundleState.UPDATE)
> 
> The problem is then probably located in the BundleSupport#update() method:
> 
> https://github.com/apache/karaf-cellar/blob/master/bundle/src/main/java/org/apache/karaf/cellar/bundle/BundleSupport.java#L130
> 
> Let me try to reproduce. I keep you posted.
> 
> Regards
> JB
> 
> On Wednesday, July 25, 2018 15:57 CEST, Oleg Cohen 
>  wrote:
>  
>> 
>> Greetings,
>> 
>> I have a question about how bundle update is handled across a Cellar cluster.
>> 
>> I have three nodes in a Cellar cluster. When I cluster-deploy a bundle on 
>> node1 from a Maven repo, it gets correctly and successfully deployed onto 
>> node2 and node3.
>> 
>> Later on, I call cluster:bundle-update XXX on node1 and it gets updated 
>> correctly on node1, but the update isn’t automatically propagated to nodes 2 
>> and 3. Is this an expected behavior?
>> 
>> Would appreciation clarification/advice!
>> 
>> Best,
>> Oleg
>>  
> 
> 
> 
>  

Re: java.lang.NullPointerException on cluster:bundle-* commands after calling cluster:bundle-update

[Oleg Cohen]

Thank you!

Karaf: 4.2.0
Cellar: 4.1.1

cluster:update didn’t do anything for me

> On Jul 25, 2018, at 11:58 AM, j...@nanthrax.net wrote:
> 
> Hi
> 
> Let me create a Jira and fix that, that's probably a refresh on the event 
> handler.
> 
> By the way, what's the Karaf and Cellar version ?
> Did you try a cluster:sync ?
> 
> Regards
> JB
> 
> On Wednesday, July 25, 2018 16:41 CEST, Oleg Cohen 
>  wrote:
>  
>> 
>> Greetings,
>> 
>> I have a three-node Cellar cluster.
>> 
>> I am on node1 and ran this command
>> 
>> cluster:bundle-update default XXX
>> 
>> The command ran successfully
>> 
>> As I try to subsequently run any cluster:bundle-* command (e.g. 
>> cluster:bundle-list default) I get a java.lang.NullPointerException and the 
>> following in the log on every node:
>> 
>> 2018-07-25T10:34:13,438 | ERROR | Karaf ssh console user karaf | ShellUtil | 
>> 33 - org.apache.karaf.shell.core - 4.2.0 | Exception caught while executing 
>> command
>> java.lang.NullPointerException: null
>> at java.util.regex.Matcher.getTextLength(Matcher.java:1283) ~[?:?]
>> at java.util.regex.Matcher.reset(Matcher.java:309) ~[?:?]
>> at java.util.regex.Matcher.(Matcher.java:229) ~[?:?]
>> at java.util.regex.Pattern.matcher(Pattern.java:1093) ~[?:?]
>> at 
>> org.apache.karaf.cellar.core.CellarSupport.wildCardMatch(CellarSupport.java:212)
>>  ~[?:?]
>> at 
>> org.apache.karaf.cellar.core.CellarSupport.isAllowed(CellarSupport.java:183) 
>> ~[?:?]
>> at 
>> org.apache.karaf.cellar.bundle.shell.ListBundleCommand.doExecute(ListBundleCommand.java:142)
>>  ~[?:?]
>> at 
>> org.apache.karaf.cellar.core.shell.CellarCommandSupport.execute(CellarCommandSupport.java:62)
>>  ~[?:?]
>> at 
>> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>>  ~[?:?]
>> at 
>> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>>  ~[?:?]
>> at 
>> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>>  ~[?:?]
>> at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) ~[?:?]
>> at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
>> ~[?:?]
>> at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) ~[?:?]
>> at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
>> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
>> at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  ~[?:?]
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  ~[?:?]
>> at java.lang.Thread.run(Thread.java:748) [?:?]
>> 
>> 
>> The problem only goes away once all nodes are fully restarted.
>> 
>> I would appreciate an insight into the problem!
>> 
>> Thank you,
>> Oleg
>>  
> 
> 
> 
>  

java.lang.NullPointerException on cluster:bundle-* commands after calling cluster:bundle-update

[Oleg Cohen]

Greetings,

I have a three-node Cellar cluster. 

I am on node1 and ran this command

cluster:bundle-update default XXX

The command ran successfully

As I try to subsequently run any cluster:bundle-* command (e.g. 
cluster:bundle-list default) I get a java.lang.NullPointerException and the 
following in the log on every node:

2018-07-25T10:34:13,438 | ERROR | Karaf ssh console user karaf | ShellUtil  
  | 33 - org.apache.karaf.shell.core - 4.2.0 | Exception caught 
while executing command
java.lang.NullPointerException: null
at java.util.regex.Matcher.getTextLength(Matcher.java:1283) ~[?:?]
at java.util.regex.Matcher.reset(Matcher.java:309) ~[?:?]
at java.util.regex.Matcher.(Matcher.java:229) ~[?:?]
at java.util.regex.Pattern.matcher(Pattern.java:1093) ~[?:?]
at 
org.apache.karaf.cellar.core.CellarSupport.wildCardMatch(CellarSupport.java:212)
 ~[?:?]
at 
org.apache.karaf.cellar.core.CellarSupport.isAllowed(CellarSupport.java:183) 
~[?:?]
at 
org.apache.karaf.cellar.bundle.shell.ListBundleCommand.doExecute(ListBundleCommand.java:142)
 ~[?:?]
at 
org.apache.karaf.cellar.core.shell.CellarCommandSupport.execute(CellarCommandSupport.java:62)
 ~[?:?]
at 
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
 ~[?:?]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
 ~[?:?]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
 ~[?:?]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
~[?:?]
at 
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) ~[?:?]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) 
~[?:?]
at org.apache.felix.gogo.runtime.Pipe.doCall(Pipe.java:417) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:229) ~[?:?]
at org.apache.felix.gogo.runtime.Pipe.call(Pipe.java:59) ~[?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:?]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
~[?:?]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
~[?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]


The problem only goes away once all nodes are fully restarted.

I would appreciate an insight into the problem!

Thank you,
Oleg

Karaf Cellar cluster bundle update propagation

[Oleg Cohen]

Greetings,

I have a question about how bundle update is handled across a Cellar cluster.

I have three nodes in a Cellar cluster. When I cluster-deploy a bundle on node1 
from a Maven repo, it gets correctly and successfully deployed onto node2 and 
node3.

Later on, I call cluster:bundle-update XXX on node1 and it gets updated 
correctly on node1, but the update isn’t automatically propagated to nodes 2 
and 3. Is this an expected behavior?

Would appreciation clarification/advice!

Best,
Oleg

Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

Same with me on Linux. Only happens with the service wrapper. Is there a
quick fix I can apply aside from copying the jar? I guess I need to add
endorsed libs somehow. JB mentioned it is fixed already. Main branch?

Thank you,
Oleg

On Jul 24, 2018, at 3:39 PM, Leschke, Scott  wrote:

Hi Oleg,



I’m the person who originally reported the issue that JB is referring to.
In my case on Windows, Karaf appears to work fine as well but there is that
error in the log that only occurs when you start Karaf using the service
wrapper.



Regards,

Scott



*From:* Oleg Cohen [mailto:oleg.co...@assurebridge.com
]
*Sent:* Tuesday, July 24, 2018 2:01 PM
*To:* user@karaf.apache.org
*Subject:* Re: java.lang.NoClassDefFoundError:
org/apache/karaf/specs/locator/OsgiLocator when running as Service on
RedHat 7.5



Hi JB,



I am using the wrapper. bin/karaf works fine.



Thank you!

Oleg



On Jul 24, 2018, at 2:58 PM, Jean-Baptiste Onofré  wrote:



Maybe it's related to:

https://issues.apache.org/jira/browse/KARAF-5840 (I already have a fix
on a local branch)

The problem only occurs when using the wrapper.

@Oleg/Miroslav: do you use wrapper to start Karaf instead of bin/karaf ?

Regards
JB

On 24/07/2018 20:54, Francois Papon wrote:

Hi,

It's weird because I downloaded the binary and after extract it, I can
see the org.apache.karaf.specs.locator-4.2.0.jar in the lib/endorsed
directory.

regards,

François Papon
fpa...@apache.org

Le 24/07/2018 à 22:31, Oleg Cohen a écrit :

Hi Miroslav,

I think I found the issue. You are right a JAR is missing.

I built org.apache.karaf.specs.locator-4.2.0.jar and added it to the
boot/lib folder and the exception is now gone.

Thank you!
Oleg



On Jul 24, 2018, at 11:45 AM, Miroslav Beranič
mailto:miroslav.bera...@mibesis.si
>> wrote:

Hi Oleg,

I've just downloaded package from:

http://karaf.apache.org/download.html
Binary Distribution : tar.gz [PGP] [SHA512]

I've downloaded to /opt/ folder and unpacked the package.

I am using RHEL 7.5, Oracle Java 8 ( 1.8.0.172 )

Next I've started Karf with:

[root@framework apache-karaf-4.2.0]# ls -al
total 424
drwxr-xr-x. 9 root root156 jul 24 17:35 .
drwxr-xr-x. 4 root root110 jul 24 17:35 ..
drwxr-xr-x. 3 root root282 apr  5 06:29 bin
drwxr-xr-x. 3 root root 17 apr  5 06:29 data
drwxr-xr-x. 9 root root123 apr  5 06:29 demos
drwxr-xr-x. 2 root root 20 apr  5 06:29 deploy
drwxr-xr-x. 3 root root   4096 apr  5 06:29 etc
drwxr-xr-x. 5 root root 59 apr  5 06:29 lib
-rw-r--r--. 1 root root  27754 apr  5 06:29 LICENSE
-rw-r--r--. 1 root root   1829 apr  5 06:29 NOTICE
-rw-r--r--. 1 root root   4025 apr  5 06:29 README
-rw-r--r--. 1 root root 390829 apr  5 06:29 RELEASE-NOTES
drwxr-xr-x. 3 root root 31 apr  5 06:29 system
[root@framework apache-karaf-4.2.0]# JAVA_HOME=/opt/jdk ./bin/karaf debug
Listening for transport dt_socket at address: 5005
__ __  
   / //_/ __ _/ __/
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (4.2.0)

Hit '' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.

karaf@root()> feature:install
service-wrapper

karaf@root()> wrapper:install
Creating file: /opt/apache-karaf-4.2.0/bin/karaf-wrapper
Creating file: /opt/apache-karaf-4.2.0/bin/karaf-service
Creating file: /opt/apache-karaf-4.2.0/bin/karaf.service
Creating file: /opt/apache-karaf-4.2.0/etc/karaf-wrapper.conf
Creating missing directory: /opt/apache-karaf-4.2.0/lib/wrapper
Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/libwrapper.so
Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/karaf-wrapper.jar
Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/karaf-wrapper-main.jar

Setup complete.  You may wish to tweak the JVM properties in the
wrapper configuration file:
/opt/apache-karaf-4.2.0/etc/karaf-wrapper.conf
before installing and starting the service.


RedHat/Fedora/CentOS Linux system detected (SystemV):
  To install the service:
$ ln -s /opt/apache-karaf-4.2.0/bin/karaf-service /etc/init.d/
$ chkconfig karaf-service --add

  To start the service when the machine is rebooted:
$ chkconfig karaf-service on

  To disable starting the service when the machine is rebooted:
$ chkconfig karaf-service off

  To start the service:
$ service karaf-service start

  To stop the service:
$ service karaf-service stop

  To uninstall the service :
$ chkconfig karaf-service --del
$ rm /etc/init.d/karaf-service

For systemd compliant Linux:
  To install the service (and enable at system boot):
   $ systemctl enable /opt/apache-karaf-4.2.0/bin/karaf.service

  To start the service:
   $ systemctl start karaf

  To stop the service:
   $ systemctl stop karaf

  To check the current service status:
   $ systemctl status karaf

  To see service activity journal:
   $ journalctl -u karaf

Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

Hi JB,

I am using the wrapper. bin/karaf works fine.

Thank you!
Oleg

> On Jul 24, 2018, at 2:58 PM, Jean-Baptiste Onofré  wrote:
> 
> Maybe it's related to:
> 
> https://issues.apache.org/jira/browse/KARAF-5840 
> <https://issues.apache.org/jira/browse/KARAF-5840> (I already have a fix
> on a local branch)
> 
> The problem only occurs when using the wrapper.
> 
> @Oleg/Miroslav: do you use wrapper to start Karaf instead of bin/karaf ?
> 
> Regards
> JB
> 
> On 24/07/2018 20:54, Francois Papon wrote:
>> Hi,
>> 
>> It's weird because I downloaded the binary and after extract it, I can
>> see the org.apache.karaf.specs.locator-4.2.0.jar in the lib/endorsed
>> directory.
>> 
>> regards,
>> 
>> François Papon
>> fpa...@apache.org
>> 
>> Le 24/07/2018 à 22:31, Oleg Cohen a écrit :
>>> Hi Miroslav,
>>> 
>>> I think I found the issue. You are right a JAR is missing.
>>> 
>>> I built org.apache.karaf.specs.locator-4.2.0.jar and added it to the
>>> boot/lib folder and the exception is now gone.
>>> 
>>> Thank you!
>>> Oleg
>>> 
>>> 
>>>> On Jul 24, 2018, at 11:45 AM, Miroslav Beranič
>>>> mailto:miroslav.bera...@mibesis.si> 
>>>> <mailto:miroslav.bera...@mibesis.si <mailto:miroslav.bera...@mibesis.si>>> 
>>>> wrote:
>>>> 
>>>> Hi Oleg,
>>>> 
>>>> I've just downloaded package from:
>>>> 
>>>> http://karaf.apache.org/download.html 
>>>> <http://karaf.apache.org/download.html>
>>>> Binary Distribution : tar.gz [PGP] [SHA512]
>>>> 
>>>> I've downloaded to /opt/ folder and unpacked the package.
>>>> 
>>>> I am using RHEL 7.5, Oracle Java 8 ( 1.8.0.172 )
>>>> 
>>>> Next I've started Karf with:
>>>> 
>>>> [root@framework apache-karaf-4.2.0]# ls -al
>>>> total 424
>>>> drwxr-xr-x. 9 root root156 jul 24 17:35 .
>>>> drwxr-xr-x. 4 root root110 jul 24 17:35 ..
>>>> drwxr-xr-x. 3 root root282 apr  5 06:29 bin
>>>> drwxr-xr-x. 3 root root 17 apr  5 06:29 data
>>>> drwxr-xr-x. 9 root root123 apr  5 06:29 demos
>>>> drwxr-xr-x. 2 root root 20 apr  5 06:29 deploy
>>>> drwxr-xr-x. 3 root root   4096 apr  5 06:29 etc
>>>> drwxr-xr-x. 5 root root 59 apr  5 06:29 lib
>>>> -rw-r--r--. 1 root root  27754 apr  5 06:29 LICENSE
>>>> -rw-r--r--. 1 root root   1829 apr  5 06:29 NOTICE
>>>> -rw-r--r--. 1 root root   4025 apr  5 06:29 README
>>>> -rw-r--r--. 1 root root 390829 apr  5 06:29 RELEASE-NOTES
>>>> drwxr-xr-x. 3 root root 31 apr  5 06:29 system
>>>> [root@framework apache-karaf-4.2.0]# JAVA_HOME=/opt/jdk ./bin/karaf debug
>>>> Listening for transport dt_socket at address: 5005
>>>> __ __    
>>>>/ //_/ __ _/ __/  
>>>>   / ,<  / __ `/ ___/ __ `/ /_
>>>>  / /| |/ /_/ / /  / /_/ / __/
>>>> /_/ |_|\__,_/_/   \__,_/_/ 
>>>> 
>>>>   Apache Karaf (4.2.0)
>>>> 
>>>> Hit '' for a list of available commands
>>>> and '[cmd] --help' for help on a specific command.
>>>> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
>>>> 
>>>> karaf@root()> feature:install
>>>> service-wrapper
>>>>
>>>>   
>>>>  
>>>> karaf@root()> wrapper:install
>>>> Creating file: /opt/apache-karaf-4.2.0/bin/karaf-wrapper
>>>> Creating file: /opt/apache-karaf-4.2.0/bin/karaf-service
>>>> Creating file: /opt/apache-karaf-4.2.0/bin/karaf.service
>>>> Creating file: /opt/apache-karaf-4.2.0/etc/karaf-wrapper.conf
>>>> Creating missing directory: /opt/apache-karaf-4.2.0/lib/wrapper
>>>> Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/libwrapper.so
>>>> Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/karaf-wrapper.jar
>>>> Creating file: /opt/apache-karaf-4.2.0/lib/wrapper/karaf-wrapper-main.jar
>>>> 
>>>> Setup complete.  You may wish to tweak the JVM properties in the
>>>> wrapper configuration file:
>>>> /opt/apache-karaf-4.2.0/etc/kara

Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

tc/init.d/
> [root@framework apache-karaf-4.2.0]# chkconfig karaf-service --add
> [root@framework apache-karaf-4.2.0]# chkconfig karaf-service on
> [root@framework apache-karaf-4.2.0]# service karaf-service start
> Starting karaf...
> [root@framework apache-karaf-4.2.0]# reboot
> 
> Now you can go back to terminal or connect over ssh --- I use SSH :
> 
> so now I ssh to Karaf with:
> 
> # ssh -p 8101 karaf@framework
> The authenticity of host '[localhost]:8101 ([::1]:8101)' can't be established.
> RSA key fingerprint is SHA256:g
> RSA key fingerprint is MD5:fc:b5:ed:9
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added '[localhost]:8101' (RSA) to the list of known 
> hosts.
> Password authentication
> Password: 
> __ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
> 
>   Apache Karaf (4.2.0)
> 
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit 'system:shutdown' to shutdown Karaf.
> Hit '' or type 'logout' to disconnect shell from current session.
> 
> karaf@root()> log:tail
> 17:39:21.456 INFO [activator-1-thread-2] Registering commands for bundle 
> org.apache.karaf.log.core/4.2.0
> 
> 
> 
> I hope this is of any help.
> 
> Kind Regards,
> Miroslav
> 
> 
> 
> 2018-07-24 17:34 GMT+02:00 Oleg Cohen  <mailto:oleg.co...@assurebridge.com>>:
> Hi Miroslav,
> 
> Java is version 1.8
> 
> ava version "1.8.0_172"
> Java(TM) SE Runtime Environment (build 1.8.0_172-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)
> 
> Thank you!
> Oleg
> 
> 
>> On Jul 24, 2018, at 11:30 AM, Miroslav Beranič > <mailto:miroslav.bera...@mibesis.si>> wrote:
>> 
>> Hi Oleg,
>> 
>> one more question - what version of Java do you use?
>> 
>> Kind Regards,
>> Miroslav
>> 
>> 
>> 2018-07-24 17:28 GMT+02:00 Miroslav Beranič > <mailto:miroslav.bera...@mibesis.si>>:
>> Hi Oleg,
>> 
>> well, I've never installed from here ( I did not even looked before).
>> Will try it for my self also. In Git repository I used 4.1.x and 4.2.x.
>> 
>> I guess 4.1.x is more "stable" for production. I've just started using 4.2. 
>> I was on 4.0.9 till previous week. I am doing upgrade across nodes.
>> 
>> 
>> Kind Regards,
>> Miroslav
>> 
>> 
>> 2018-07-24 17:21 GMT+02:00 Oleg Cohen > <mailto:oleg.co...@assurebridge.com>>:
>> Hi Miroslav,
>> 
>> I got apache-karaf-4.2.0.tar.gz binary distribution from here 
>> http://karaf.apache.org/download.html <http://karaf.apache.org/download.html>
>> 
>> I can definitely try building from Git. Let me try …
>> 
>> Thank you!
>> Oleg
>> 
>>> On Jul 24, 2018, at 11:17 AM, Miroslav Beranič >> <mailto:miroslav.bera...@mibesis.si>> wrote:
>>> 
>>> Hi Oleg,
>>> 
>>> where from did you deployed Karaf? You build it from the source or some 
>>> pre-compiled package/distribution?
>>> 
>>> In general this is saying you are missing JAR ( but I guess you know 
>>> already this ).
>>> 
>>> ( I've deployed multiple times - in past week - Karaf on RHEL 7.5 and I had 
>>> no such problem - but I was building from the GitHub git repository )
>>> 
>>> Kind Regards,
>>> Miroslav
>>> 
>>> 
>>> 2018-07-24 17:11 GMT+02:00 Oleg Cohen >> <mailto:oleg.co...@assurebridge.com>>:
>>> Greetings,
>>> 
>>> I have deployed Karaf v4.2.0 into a Linux RH 7.5 server.
>>> 
>>> When I run Karaf as a service I get the following error in the log multiple 
>>> times:
>>> 
>>> 
>>> 2018-07-24T11:07:12,176 | ERROR | features-3-thread-1 | Felix   
>>>  |  -  -  | Bundle org.apache.felix.framework [0] 
>>> EventDispatcher: Error during dispatch. (java.lang.NoClassDefFoundError: 
>>> org/apache/karaf/specs/locator/OsgiLocator)
>>> java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator
>>> at 
>>> org.apache.karaf.specs.activator.Activator.register(Activator.java:124) 
>>> ~[?:?]
>>> at 
>>> org.apache.karaf.specs.activator.Activator.bundleChanged(Activator.java:96) 
>>> ~[?:?]
>>> at 
>>> org.apache.felix.framework.E

Re: java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator when running as Service on RedHat 7.5

[Oleg Cohen]

Hi Miroslav,

Java is version 1.8

ava version "1.8.0_172"
Java(TM) SE Runtime Environment (build 1.8.0_172-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)

Thank you!
Oleg


> On Jul 24, 2018, at 11:30 AM, Miroslav Beranič  
> wrote:
> 
> Hi Oleg,
> 
> one more question - what version of Java do you use?
> 
> Kind Regards,
> Miroslav
> 
> 
> 2018-07-24 17:28 GMT+02:00 Miroslav Beranič  <mailto:miroslav.bera...@mibesis.si>>:
> Hi Oleg,
> 
> well, I've never installed from here ( I did not even looked before).
> Will try it for my self also. In Git repository I used 4.1.x and 4.2.x.
> 
> I guess 4.1.x is more "stable" for production. I've just started using 4.2. I 
> was on 4.0.9 till previous week. I am doing upgrade across nodes.
> 
> 
> Kind Regards,
> Miroslav
> 
> 
> 2018-07-24 17:21 GMT+02:00 Oleg Cohen  <mailto:oleg.co...@assurebridge.com>>:
> Hi Miroslav,
> 
> I got apache-karaf-4.2.0.tar.gz binary distribution from here 
> http://karaf.apache.org/download.html <http://karaf.apache.org/download.html>
> 
> I can definitely try building from Git. Let me try …
> 
> Thank you!
> Oleg
> 
>> On Jul 24, 2018, at 11:17 AM, Miroslav Beranič > <mailto:miroslav.bera...@mibesis.si>> wrote:
>> 
>> Hi Oleg,
>> 
>> where from did you deployed Karaf? You build it from the source or some 
>> pre-compiled package/distribution?
>> 
>> In general this is saying you are missing JAR ( but I guess you know already 
>> this ).
>> 
>> ( I've deployed multiple times - in past week - Karaf on RHEL 7.5 and I had 
>> no such problem - but I was building from the GitHub git repository )
>> 
>> Kind Regards,
>> Miroslav
>> 
>> 
>> 2018-07-24 17:11 GMT+02:00 Oleg Cohen > <mailto:oleg.co...@assurebridge.com>>:
>> Greetings,
>> 
>> I have deployed Karaf v4.2.0 into a Linux RH 7.5 server.
>> 
>> When I run Karaf as a service I get the following error in the log multiple 
>> times:
>> 
>> 
>> 2018-07-24T11:07:12,176 | ERROR | features-3-thread-1 | Felix
>> |  -  -  | Bundle org.apache.felix.framework [0] 
>> EventDispatcher: Error during dispatch. (java.lang.NoClassDefFoundError: 
>> org/apache/karaf/specs/locator/OsgiLocator)
>> java.lang.NoClassDefFoundError: org/apache/karaf/specs/locator/OsgiLocator
>>  at 
>> org.apache.karaf.specs.activator.Activator.register(Activator.java:124) 
>> ~[?:?]
>>  at 
>> org.apache.karaf.specs.activator.Activator.bundleChanged(Activator.java:96) 
>> ~[?:?]
>>  at 
>> org.apache.felix.framework.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:915)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:516)
>>  ~[?:?]
>>  at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) 
>> ~[?:?]
>>  at 
>> org.apache.felix.framework.StatefulResolver.fireResolvedEvents(StatefulResolver.java:1289)
>>  ~[?:?]
>>  at 
>> org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:512)
>>  ~[?:?]
>>  at org.apache.felix.framework.Felix.resolveBundles(Felix.java:4108) 
>> ~[?:?]
>>  at 
>> org.apache.felix.framework.FrameworkWiringImpl.resolveBundles(FrameworkWiringImpl.java:133)
>>  ~[?:?]
>>  at 
>> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.resolveBundles(BundleInstallSupportImpl.java:240)
>>  ~[?:?]
>>  at 
>> org.apache.karaf.features.internal.service.FeaturesServiceImpl.resolveBundles(FeaturesServiceImpl.java:1131)
>>  ~[?:?]
>>  at 
>> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:982)
>>  ~[?:?]
>>  at 
>> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
>>  ~[?:?]
>>  at 
>> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
>>  ~[?:?]
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  [?:?]
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  [?:?]
>>  at java.lang.Thread.run(Thread.java:748) [?:?]
>> 
>> I would appreciate help with fixing this problem of finding a workaround!
>> 
>> Best,
>> Oleg
>> 
>> 
>> 
>> -- 
>> Miroslav Beranič
>> MIBESIS
>> +386(0)40/814-843
>> miroslav.bera...@mibesis.si <mailto:miroslav.bera...@mibesis.si>
>> http://www.mibesis.si <http://www.mibesis.si/>
> 
> 
> 
> -- 
> Miroslav Beranič
> MIBESIS
> +386(0)40/814-843
> miroslav.bera...@mibesis.si <mailto:miroslav.bera...@mibesis.si>
> http://www.mibesis.si <http://www.mibesis.si/>
> 
> 
> -- 
> Miroslav Beranič
> MIBESIS
> +386(0)40/814-843
> miroslav.bera...@mibesis.si <mailto:miroslav.bera...@mibesis.si>
> http://www.mibesis.si <http://www.mibesis.si/>