[jira] [Commented] (KARAF-6074) Race condition between the FeaturesService and FeatureDeploymentListener
[
https://issues.apache.org/jira/browse/KARAF-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735832#comment-16735832
]
Jean-Baptiste Onofré commented on KARAF-6074:
-
You use the regular {{etc/org.apache.karaf.features.cfg}} right ? No sync for
feature install, correct ?
> Race condition between the FeaturesService and FeatureDeploymentListener
>
>
> Key: KARAF-6074
> URL: https://issues.apache.org/jira/browse/KARAF-6074
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Karaf 4.2.2 Windows 7 and Equinox
>Reporter: J. Brébec
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> On the first start of a custom Karaf container (4.2.2), the logs shows a log
> of NPE in FeatureDeploymentListener.
> After some analysis of this Exception, it's look like a race condition
> between the FeaturesService and the FeatureDeploymentListener :
> # The FeaturesService starts and launch a provisioning in another thread
> # a FeatureDeploymentListener is registered, and call bundleChanged for
> every bundle installed (the startup bundles)
> # It calls FeaturesService.state.requirements and get an empty map
> # Updating the root regions in the requirements map fails with an NPE
> # Some times later, the deployment task launched at step 1 is started, and
> FeaturesService.saveState() is called : state.requirements."root region" is
> initialised
> The step 5 is executed in another thread, so it can happens before step 2
> (and it works) or after, causing this NPE
> Moreover, some methods in FeaturesService assume that
> state.requirements."root region" exists. There are probably others npe here.
>
> {code:java}
> 14:37:55.668 ERROR [activator-1-thread-2] Unable to update deployed features
> for bundle: org.eclipse.osgi - 3.12.100.v20180210-1608
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:247)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.init(FeatureDeploymentListener.java:95)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.osgi.Activator.doStart(Activator.java:52)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:292)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:?]
> 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)
> [?:?]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6061) Help for shell: commands are not properly formatted
[
https://issues.apache.org/jira/browse/KARAF-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736022#comment-16736022
]
Martin Lichtin commented on KARAF-6061:
---
I'm trying this under Unix (Linux CentOS 6.6).
I see your output has the word "while" colored, this doesn't happen for me
either.
Perhaps something with the terminal settings.
> Help for shell: commands are not properly formatted
> ---
>
> Key: KARAF-6061
> URL: https://issues.apache.org/jira/browse/KARAF-6061
> Project: Karaf
> Issue Type: Wish
> Components: karaf
>Affects Versions: 4.1.7
>Reporter: Martin Lichtin
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: shell
> Fix For: 4.1.8, 4.2.3
>
>
> A 'nice' help looks like
> {noformat}
> System/admin@ccstp1()> help log:set
> DESCRIPTION
> log:set
> Sets the log level.
> SYNTAX
> log:set level [logger]
> ARGUMENTS
> level
> The log level to set (TRACE, DEBUG, INFO, WARN, ERROR) or
> DEFAULT to unset
> logger
> Logger name or ROOT (default)
> {noformat}
> whereas shell: command help looks like:
> {noformat}
> System/admin@ccstp1()> help shell:while
> while - while loop
> Usage: while { condition } { action }
> -? --help
> Show help
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6074) Race condition between the FeaturesService and FeatureDeploymentListener
[
https://issues.apache.org/jira/browse/KARAF-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735974#comment-16735974
]
J. Brébec commented on KARAF-6074:
--
Yes.
It's easy to reproduce with the default distrib in a debugger, by simulating a
delay with a break point in
"org.apache.karaf.features.internal.service.Deployer.deploy()" line 917
(callback.saveState() is the call which initialises the root region in the
requirements on the first cold start).
> Race condition between the FeaturesService and FeatureDeploymentListener
>
>
> Key: KARAF-6074
> URL: https://issues.apache.org/jira/browse/KARAF-6074
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Karaf 4.2.2 Windows 7 and Equinox
>Reporter: J. Brébec
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> On the first start of a custom Karaf container (4.2.2), the logs shows a log
> of NPE in FeatureDeploymentListener.
> After some analysis of this Exception, it's look like a race condition
> between the FeaturesService and the FeatureDeploymentListener :
> # The FeaturesService starts and launch a provisioning in another thread
> # a FeatureDeploymentListener is registered, and call bundleChanged for
> every bundle installed (the startup bundles)
> # It calls FeaturesService.state.requirements and get an empty map
> # Updating the root regions in the requirements map fails with an NPE
> # Some times later, the deployment task launched at step 1 is started, and
> FeaturesService.saveState() is called : state.requirements."root region" is
> initialised
> The step 5 is executed in another thread, so it can happens before step 2
> (and it works) or after, causing this NPE
> Moreover, some methods in FeaturesService assume that
> state.requirements."root region" exists. There are probably others npe here.
>
> {code:java}
> 14:37:55.668 ERROR [activator-1-thread-2] Unable to update deployed features
> for bundle: org.eclipse.osgi - 3.12.100.v20180210-1608
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:247)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.init(FeatureDeploymentListener.java:95)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.osgi.Activator.doStart(Activator.java:52)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:292)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:?]
> 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)
> [?:?]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-6069.
-
Resolution: Fixed
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-6064) Add command/option to list the PID
[
https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735933#comment-16735933
]
Jean-Baptiste Onofré edited comment on KARAF-6064 at 1/7/19 4:34 PM:
-
In Karaf itself, that's already provided by {{config:list -s}} command and
{{Configs}} attribute on the {{ConfigMBean}}.
was (Author: jbonofre):
In Karaf itself, that's already provided by {{config:list -s}} command and
{{getConfigs()}} operation on the {{ConfigMBean}}.
> Add command/option to list the PID
> --
>
> Key: KARAF-6064
> URL: https://issues.apache.org/jira/browse/KARAF-6064
> Project: Karaf
> Issue Type: Wish
> Components: cave
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: cave-4.2.0
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6068) Karaf hangs by bundle resolving (felix resolver)
[
https://issues.apache.org/jira/browse/KARAF-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735890#comment-16735890
]
Jean-Baptiste Onofré commented on KARAF-6068:
-
This is a very simple test case I did to try to reproduce this issue:
https://github.com/jbonofre/resolver-test
I've tested with Karaf 4.2.3-SNAPSHOT without problem.
I'm now testing with Karaf 4.1.5.
> Karaf hangs by bundle resolving (felix resolver)
>
>
> Key: KARAF-6068
> URL: https://issues.apache.org/jira/browse/KARAF-6068
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.5
> Environment: JDK 8
> Windows, Linux
>Reporter: Andrei Shakirin
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Attachments: karaf-hangs-stacktrace.txt, tesb.log, threads-cpu.png
>
>
> I faced following situation in project uses Karaf as deployment container for
> microservices:
> 1) bundle A is installed with feature A and exports java packages xxx.yyy in
> version 10.2.0
> 2) additionally, bundle B was created and installed with feature B. Bundle B
> exporting the same java packages (xxx.yyy) as bundle A, but with another
> version 1.1.0
> Problem: as soon as other modules importing java packages (xxx.yyy) with
> version [1.1, 2.0) - Karaf completely hangs on startup. There are no logs
> describing the problem. The last log statement is about JMX registration.
> Karaf JVM takes about 90% CPU - looks like infinite loop.
> The thread dump shows that threads occupied CPU are the following:
> {code}
> "pool-38-thread-8" #245 prio=5 os_prio=0 tid=0x1cd94000 nid=0x3094
> runnable [0x29f0e000]
>java.lang.Thread.State: RUNNABLE
> at
> org.apache.felix.resolver.util.ArrayMap.getOrCompute(ArrayMap.java:74)
> at
> org.apache.felix.resolver.ResolverImpl.addUsedBlame(ResolverImpl.java:1284)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1110)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.computeUses(ResolverImpl.java:872)
> at
> org.apache.felix.resolver.ResolverImpl.access$500(ResolverImpl.java:59)
> at
> org.apache.felix.resolver.ResolverImpl$6.run(ResolverImpl.java:1231)
> at
> org.apache.felix.resolver.ResolverImpl$EnhancedExecutor$1.run(ResolverImpl.java:2442)
> 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)
> {code}
> Full logs and thread dumps are attached.
> The problem makes diagnostic of package exports/imports issues completely
> impossible.
> I will try to reproduce it on simple example, but perhaps you can start
> analyse based om thread dumps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6064: Issue Type: Improvement (was: Wish) > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5996) client scripts require the control key to submit commands in Windows Powershell
[ https://issues.apache.org/jira/browse/KARAF-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5996: --- Assignee: Jean-Baptiste Onofré > client scripts require the control key to submit commands in Windows > Powershell > --- > > Key: KARAF-5996 > URL: https://issues.apache.org/jira/browse/KARAF-5996 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.1 > Environment: Windows 2012 and Windows 10 >Reporter: Brandan Jeter >Assignee: Jean-Baptiste Onofré >Priority: Major > > I have verified this on both 4.2.1 and master. > Steps to reproduce: > * Run karaf in Windows > * Run the client.bat script from within Powershell > * Type in a command > * Press enter (does not submit the command) > * Press control+enter (command is submitted) > I've also noticed some of the encoding is messed up, and backspace does not > work correctly. I had to use control+c to undo any text I typed into the > console. > > I believe it's an issue with jline. I was able to swap out jline 3.9.0 for > 3.6.2 in the karaf 4.2.1 distribution, and the bug went away. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6061) Help for shell: commands are not properly formatted
[
https://issues.apache.org/jira/browse/KARAF-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6061:
Labels: shell (was: )
> Help for shell: commands are not properly formatted
> ---
>
> Key: KARAF-6061
> URL: https://issues.apache.org/jira/browse/KARAF-6061
> Project: Karaf
> Issue Type: Wish
> Components: karaf
>Affects Versions: 4.1.7
>Reporter: Martin Lichtin
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Labels: shell
> Fix For: 4.1.8, 4.2.3
>
>
> A 'nice' help looks like
> {noformat}
> System/admin@ccstp1()> help log:set
> DESCRIPTION
> log:set
> Sets the log level.
> SYNTAX
> log:set level [logger]
> ARGUMENTS
> level
> The log level to set (TRACE, DEBUG, INFO, WARN, ERROR) or
> DEFAULT to unset
> logger
> Logger name or ROOT (default)
> {noformat}
> whereas shell: command help looks like:
> {noformat}
> System/admin@ccstp1()> help shell:while
> while - while loop
> Usage: while { condition } { action }
> -? --help
> Show help
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6068) Karaf hangs by bundle resolving (felix resolver)
[
https://issues.apache.org/jira/browse/KARAF-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735899#comment-16735899
]
Jean-Baptiste Onofré commented on KARAF-6068:
-
I don't reproduce the issue on Karaf 4.1.5 (tested with both felix and equinox
as framework). I'm taking a look on your zip.
> Karaf hangs by bundle resolving (felix resolver)
>
>
> Key: KARAF-6068
> URL: https://issues.apache.org/jira/browse/KARAF-6068
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.1.5
> Environment: JDK 8
> Windows, Linux
>Reporter: Andrei Shakirin
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Attachments: karaf-hangs-stacktrace.txt, tesb.log, threads-cpu.png
>
>
> I faced following situation in project uses Karaf as deployment container for
> microservices:
> 1) bundle A is installed with feature A and exports java packages xxx.yyy in
> version 10.2.0
> 2) additionally, bundle B was created and installed with feature B. Bundle B
> exporting the same java packages (xxx.yyy) as bundle A, but with another
> version 1.1.0
> Problem: as soon as other modules importing java packages (xxx.yyy) with
> version [1.1, 2.0) - Karaf completely hangs on startup. There are no logs
> describing the problem. The last log statement is about JMX registration.
> Karaf JVM takes about 90% CPU - looks like infinite loop.
> The thread dump shows that threads occupied CPU are the following:
> {code}
> "pool-38-thread-8" #245 prio=5 os_prio=0 tid=0x1cd94000 nid=0x3094
> runnable [0x29f0e000]
>java.lang.Thread.State: RUNNABLE
> at
> org.apache.felix.resolver.util.ArrayMap.getOrCompute(ArrayMap.java:74)
> at
> org.apache.felix.resolver.ResolverImpl.addUsedBlame(ResolverImpl.java:1284)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1110)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:1105)
> at
> org.apache.felix.resolver.ResolverImpl.computeUses(ResolverImpl.java:872)
> at
> org.apache.felix.resolver.ResolverImpl.access$500(ResolverImpl.java:59)
> at
> org.apache.felix.resolver.ResolverImpl$6.run(ResolverImpl.java:1231)
> at
> org.apache.felix.resolver.ResolverImpl$EnhancedExecutor$1.run(ResolverImpl.java:2442)
> 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)
> {code}
> Full logs and thread dumps are attached.
> The problem makes diagnostic of package exports/imports issues completely
> impossible.
> I will try to reproduce it on simple example, but perhaps you can start
> analyse based om thread dumps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[
https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735933#comment-16735933
]
Jean-Baptiste Onofré commented on KARAF-6064:
-
In Karaf itself, that's already provided by {{config:list -s}} command and
{{getConfigs()}} operation on the {{ConfigMBean}}.
> Add command/option to list the PID
> --
>
> Key: KARAF-6064
> URL: https://issues.apache.org/jira/browse/KARAF-6064
> Project: Karaf
> Issue Type: Wish
> Components: cave, karaf
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: cave-4.2.0, 4.2.3
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6064: Fix Version/s: (was: 4.2.3) > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Wish > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6064: Component/s: (was: karaf) > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Wish > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0, 4.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Deleted] (KARAF-6067) Rename openjpa3 feature as openjpa
[ https://issues.apache.org/jira/browse/KARAF-6067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré deleted KARAF-6067: > Rename openjpa3 feature as openjpa > -- > > Key: KARAF-6067 > URL: https://issues.apache.org/jira/browse/KARAF-6067 > Project: Karaf > Issue Type: Task >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6061) Help for shell: commands are not properly formatted
[
https://issues.apache.org/jira/browse/KARAF-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6061:
Component/s: karaf
> Help for shell: commands are not properly formatted
> ---
>
> Key: KARAF-6061
> URL: https://issues.apache.org/jira/browse/KARAF-6061
> Project: Karaf
> Issue Type: Wish
> Components: karaf
>Affects Versions: 4.1.7
>Reporter: Martin Lichtin
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.8, 4.2.3
>
>
> A 'nice' help looks like
> {noformat}
> System/admin@ccstp1()> help log:set
> DESCRIPTION
> log:set
> Sets the log level.
> SYNTAX
> log:set level [logger]
> ARGUMENTS
> level
> The log level to set (TRACE, DEBUG, INFO, WARN, ERROR) or
> DEFAULT to unset
> logger
> Logger name or ROOT (default)
> {noformat}
> whereas shell: command help looks like:
> {noformat}
> System/admin@ccstp1()> help shell:while
> while - while loop
> Usage: while { condition } { action }
> -? --help
> Show help
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6061) Help for shell: commands are not properly formatted
[
https://issues.apache.org/jira/browse/KARAF-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735938#comment-16735938
]
Jean-Baptiste Onofré commented on KARAF-6061:
-
I tested with Karaf 4.1.7 and 4.2.3-SNAPSHOT and formatting is fine for me:
{code}
karaf@root()> help shell:while
while - while loop
Usage: while { condition } { action }
-? --helpShow help
{code}
Are you on Windows or Unix ?
> Help for shell: commands are not properly formatted
> ---
>
> Key: KARAF-6061
> URL: https://issues.apache.org/jira/browse/KARAF-6061
> Project: Karaf
> Issue Type: Wish
>Affects Versions: 4.1.7
>Reporter: Martin Lichtin
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.8, 4.2.3
>
>
> A 'nice' help looks like
> {noformat}
> System/admin@ccstp1()> help log:set
> DESCRIPTION
> log:set
> Sets the log level.
> SYNTAX
> log:set level [logger]
> ARGUMENTS
> level
> The log level to set (TRACE, DEBUG, INFO, WARN, ERROR) or
> DEFAULT to unset
> logger
> Logger name or ROOT (default)
> {noformat}
> whereas shell: command help looks like:
> {noformat}
> System/admin@ccstp1()> help shell:while
> while - while loop
> Usage: while { condition } { action }
> -? --help
> Show help
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5996) client scripts require the control key to submit commands in Windows Powershell
[ https://issues.apache.org/jira/browse/KARAF-5996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5996: Fix Version/s: 4.2.3 > client scripts require the control key to submit commands in Windows > Powershell > --- > > Key: KARAF-5996 > URL: https://issues.apache.org/jira/browse/KARAF-5996 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.1 > Environment: Windows 2012 and Windows 10 >Reporter: Brandan Jeter >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.3 > > > I have verified this on both 4.2.1 and master. > Steps to reproduce: > * Run karaf in Windows > * Run the client.bat script from within Powershell > * Type in a command > * Press enter (does not submit the command) > * Press control+enter (command is submitted) > I've also noticed some of the encoding is messed up, and backspace does not > work correctly. I had to use control+c to undo any text I typed into the > console. > > I believe it's an issue with jline. I was able to swap out jline 3.9.0 for > 3.6.2 in the karaf 4.2.1 distribution, and the bug went away. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735977#comment-16735977
]
ASF GitHub Bot commented on KARAF-6069:
---
jbonofre commented on pull request #712: [KARAF-6069] Avoid to overwrite
project artifact if the packaging is pom
URL: https://github.com/apache/karaf/pull/712
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735978#comment-16735978
]
ASF subversion and git services commented on KARAF-6069:
Commit aa78736c8da40d8a292d5c474fd270ab397b5074 in karaf's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=aa78736 ]
[KARAF-6069] Avoid to overwrite project artifact if the packaging is pom
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735979#comment-16735979
]
ASF subversion and git services commented on KARAF-6069:
Commit 138f617d9cc249ecb9193eb3c92736a6d0a84525 in karaf's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=138f617 ]
Merge pull request #712 from jbonofre/KARAF-6069
[KARAF-6069] Avoid to overwrite project artifact if the packaging is pom
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735980#comment-16735980
]
ASF subversion and git services commented on KARAF-6069:
Commit 138f617d9cc249ecb9193eb3c92736a6d0a84525 in karaf's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=138f617 ]
Merge pull request #712 from jbonofre/KARAF-6069
[KARAF-6069] Avoid to overwrite project artifact if the packaging is pom
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6069:
Labels: maven (was: )
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Labels: maven
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736032#comment-16736032 ] ASF GitHub Bot commented on KARAF-6064: --- jbonofre commented on pull request #17: [KARAF-6064] Add configs operation on Cave Deployer to list the configuration PIDs URL: https://github.com/apache/karaf-cave/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-6074) Race condition between the FeaturesService and FeatureDeploymentListener
[
https://issues.apache.org/jira/browse/KARAF-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-6074:
---
Assignee: Jean-Baptiste Onofré
> Race condition between the FeaturesService and FeatureDeploymentListener
>
>
> Key: KARAF-6074
> URL: https://issues.apache.org/jira/browse/KARAF-6074
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
> Environment: Karaf 4.2.2 Windows 7 and Equinox
>Reporter: J. Brébec
>Assignee: Jean-Baptiste Onofré
>Priority: Major
>
> On the first start of a custom Karaf container (4.2.2), the logs shows a log
> of NPE in FeatureDeploymentListener.
> After some analysis of this Exception, it's look like a race condition
> between the FeaturesService and the FeatureDeploymentListener :
> # The FeaturesService starts and launch a provisioning in another thread
> # a FeatureDeploymentListener is registered, and call bundleChanged for
> every bundle installed (the startup bundles)
> # It calls FeaturesService.state.requirements and get an empty map
> # Updating the root regions in the requirements map fails with an NPE
> # Some times later, the deployment task launched at step 1 is started, and
> FeaturesService.saveState() is called : state.requirements."root region" is
> initialised
> The step 5 is executed in another thread, so it can happens before step 2
> (and it works) or after, causing this NPE
> Moreover, some methods in FeaturesService assume that
> state.requirements."root region" exists. There are probably others npe here.
>
> {code:java}
> 14:37:55.668 ERROR [activator-1-thread-2] Unable to update deployed features
> for bundle: org.eclipse.osgi - 3.12.100.v20180210-1608
> java.lang.NullPointerException: null
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:247)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.FeatureDeploymentListener.init(FeatureDeploymentListener.java:95)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at
> org.apache.karaf.deployer.features.osgi.Activator.doStart(Activator.java:52)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:292)
> [25:org.apache.karaf.deployer.features:4.2.2]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [?:?]
> 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)
> [?:?]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6069) Distribution pom is not uploaded on Central
[
https://issues.apache.org/jira/browse/KARAF-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735821#comment-16735821
]
ASF GitHub Bot commented on KARAF-6069:
---
jbonofre commented on pull request #712: [KARAF-6069] Avoid to overwrite
project artifact if the packaging is pom
URL: https://github.com/apache/karaf/pull/712
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Distribution pom is not uploaded on Central
> ---
>
> Key: KARAF-6069
> URL: https://issues.apache.org/jira/browse/KARAF-6069
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.2.3
>
>
> With the change to support maven-install-plugin 3.0.0.M1, the distributions
> ({{apache-karaf}} and {{apache-karaf-minimal}}) pom are not uploaded. The
> reason is that the attached artifact is not the pom anymore but the
> {{tar.gz}} by default.
> I'm fixing that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6074) Race condition between the FeaturesService and FeatureDeploymentListener
J. Brébec created KARAF-6074:
Summary: Race condition between the FeaturesService and
FeatureDeploymentListener
Key: KARAF-6074
URL: https://issues.apache.org/jira/browse/KARAF-6074
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.2
Environment: Karaf 4.2.2 Windows 7 and Equinox
Reporter: J. Brébec
On the first start of a custom Karaf container (4.2.2), the logs shows a log of
NPE in FeatureDeploymentListener.
After some analysis of this Exception, it's look like a race condition between
the FeaturesService and the FeatureDeploymentListener :
# The FeaturesService starts and launch a provisioning in another thread
# a FeatureDeploymentListener is registered, and call bundleChanged for every
bundle installed (the startup bundles)
# It calls FeaturesService.state.requirements and get an empty map
# Updating the root regions in the requirements map fails with an NPE
# Some times later, the deployment task launched at step 1 is started, and
FeaturesService.saveState() is called : state.requirements."root region" is
initialised
The step 5 is executed in another thread, so it can happens before step 2 (and
it works) or after, causing this NPE
Moreover, some methods in FeaturesService assume that state.requirements."root
region" exists. There are probably others npe here.
{code:java}
14:37:55.668 ERROR [activator-1-thread-2] Unable to update deployed features
for bundle: org.eclipse.osgi - 3.12.100.v20180210-1608
java.lang.NullPointerException: null
at
org.apache.karaf.deployer.features.FeatureDeploymentListener.bundleChanged(FeatureDeploymentListener.java:247)
[25:org.apache.karaf.deployer.features:4.2.2]
at
org.apache.karaf.deployer.features.FeatureDeploymentListener.init(FeatureDeploymentListener.java:95)
[25:org.apache.karaf.deployer.features:4.2.2]
at org.apache.karaf.deployer.features.osgi.Activator.doStart(Activator.java:52)
[25:org.apache.karaf.deployer.features:4.2.2]
at org.apache.karaf.util.tracker.BaseActivator.run(BaseActivator.java:292)
[25:org.apache.karaf.deployer.features:4.2.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
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)
[?:?]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736078#comment-16736078 ] ASF subversion and git services commented on KARAF-6064: Commit 56e3c2e735f37851421bfd774ad3c6bcc74f3696 in karaf-cave's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf-cave.git;h=56e3c2e ] Merge pull request #17 from jbonofre/KARAF-6064 [KARAF-6064] Add configs operation on Cave Deployer to list the configuration PIDs > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6064. - Resolution: Fixed > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736076#comment-16736076 ] ASF subversion and git services commented on KARAF-6064: Commit 97f406b61a1b60d61c7ca1865d27282494fec79c in karaf-cave's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf-cave.git;h=97f406b ] [KARAF-6064] Add configs operation on Cave Deployer to list the configuration PIDs > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736075#comment-16736075 ] ASF GitHub Bot commented on KARAF-6064: --- jbonofre commented on pull request #17: [KARAF-6064] Add configs operation on Cave Deployer to list the configuration PIDs URL: https://github.com/apache/karaf-cave/pull/17 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6064) Add command/option to list the PID
[ https://issues.apache.org/jira/browse/KARAF-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16736077#comment-16736077 ] ASF subversion and git services commented on KARAF-6064: Commit 56e3c2e735f37851421bfd774ad3c6bcc74f3696 in karaf-cave's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf-cave.git;h=56e3c2e ] Merge pull request #17 from jbonofre/KARAF-6064 [KARAF-6064] Add configs operation on Cave Deployer to list the configuration PIDs > Add command/option to list the PID > -- > > Key: KARAF-6064 > URL: https://issues.apache.org/jira/browse/KARAF-6064 > Project: Karaf > Issue Type: Improvement > Components: cave >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: cave-4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated KARAF-6005:
Description:
I defined a feature with a ranged bundle version:
{code:xml}
mvn:de.some.api/api/[1,2)
{code}
If a bundle within that range lies within the global/user Maven repo ".m2", the
bundle gets resolved.
If it resides only within the "system" folder of Karaf I get an exception:
{noformat}
karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
Error downloading mvn:de.some.api/api/[1,2)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
at
org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
at
org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
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:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Suppressed: java.io.IOException: Error downloading
mvn:de.some.api/api/[1,2)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
... 3 more
Caused by: java.io.IOException: Error resolving artifact
de.some.api:api:[1,2)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
at
org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
... 7 more
Caused by:
shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
highest version found for de.some.api:api:[1,2)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
... 12 more
{noformat}
Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
mentioned in the mailing list does not help.
was:
I defined a feature with a ranged bundle version:
mvn:de.some.api/api/[1,2)
If a bundle within that range lies within the global/user Maven repo ".m2", the
bundle gets resolved.
If it resides only within the "system" folder of Karaf I get an exception:
{noformat}
karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
Error downloading mvn:de.some.api/api/[1,2)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
at
org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
at
org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
at
org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
at
org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
at
org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
at
[jira] [Commented] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735610#comment-16735610
]
Grzegorz Grzybek commented on KARAF-6005:
-
https://ops4j1.jira.com/browse/PAXURL-350
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
>
> I defined a feature with a ranged bundle version:
>
> mvn:de.some.api/api/[1,2)
>
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> 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:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
> mentioned in the mailing list does not help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6076) Blueprint loading fails with Saxon or Xalan
Jean-Baptiste Onofré created KARAF-6076:
---
Summary: Blueprint loading fails with Saxon or Xalan
Key: KARAF-6076
URL: https://issues.apache.org/jira/browse/KARAF-6076
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Reported on the mailing list:
{code}
I use Karaf as a runtime to host my Apache Camel routes. They are
mostly plain blueprint .xmls that are installed and deployed with the
blueprint handler. I make heavy use of xsl tranformations and have in
the past used Xalan but am moving to Saxon for xslt/xpath 2.0.
On 4.2.1 I don't have any issues installing and using either Xalan or
Saxon bundles, but on 4.2.2, once either are installed I can no longer
install through blueprint. It looks to be the result of the change for
"Set the secure processing feature on TransformerFactory instances" in
XmlUtils in commit de4c413925379913ffb3bf96ead7edc2dba98d4b. That
commit sets XMLConstants.ACCESS_EXTERNAL_DTD and neither Xalan nor
Saxon support that property. From what I've read searching for that
error I believe external DTD isn't in the purview of transformation
but in the document parser.
Note that it is after a restart of Karaf after installing Saxon that I
get the exception when trying to install another blueprint bundle. I
believe a transfomer is already created from the default
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImp.
Has anyone else seen this?
Thanks.
-John
2018-12-31T16:17:31,853 | ERROR |
fileinstall-/opt/sgscamel/karaf/apache-karaf-4.2.2/deploy |
BlueprintURLHandler | 63 -
org.apache.karaf.deployer.blueprint - 4.2.2 | Error opening blueprint
xml url
java.lang.IllegalArgumentException: Unknown configuration property
http://javax.xml.XMLConstants/property/accessExternalDTD
at
net.sf.saxon.Configuration.setConfigurationProperty(Configuration.java:4644)
~[?:?]
at
net.sf.saxon.s9api.Processor.setConfigurationProperty(Processor.java:352)
~[?:?]
at
net.sf.saxon.jaxp.SaxonTransformerFactory.setAttribute(SaxonTransformerFactory.java:306)
~[?:?]
at org.apache.karaf.util.XmlUtils.transformer(XmlUtils.java:154)
~[63:org.apache.karaf.deployer.blueprint:4.2.2]
at org.apache.karaf.util.XmlUtils.transform(XmlUtils.java:96)
~[63:org.apache.karaf.deployer.blueprint:4.2.2]
at
org.apache.karaf.deployer.blueprint.BlueprintTransformer.analyze(BlueprintTransformer.java:129)
~[63:org.apache.karaf.deployer.blueprint:4.2.2]
at
org.apache.karaf.deployer.blueprint.BlueprintTransformer.transform(BlueprintTransformer.java:71)
~[63:org.apache.karaf.deployer.blueprint:4.2.2]
at
org.apache.karaf.deployer.blueprint.BlueprintURLHandler$Connection.getInputStream(BlueprintURLHandler.java:73)
[63:org.apache.karaf.deployer.blueprint:4.2.2]
at java.net.URL.openStream(URL.java:1045) [?:?]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:962)
[10:org.apache.felix.fileinstall:3.6.4]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:884)
[10:org.apache.felix.fileinstall:3.6.4]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:489)
[10:org.apache.felix.fileinstall:3.6.4]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365)
[10:org.apache.felix.fileinstall:3.6.4]
at
org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316)
[10:org.apache.felix.fileinstall:3.6.4]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6075) When using enterprise feature, karaf distribution contains invalid etc/org.apache.karaf.features.cfg
Jean-Baptiste Onofré created KARAF-6075:
---
Summary: When using enterprise feature, karaf distribution
contains invalid etc/org.apache.karaf.features.cfg
Key: KARAF-6075
URL: https://issues.apache.org/jira/browse/KARAF-6075
Project: Karaf
Issue Type: Bug
Components: karaf
Affects Versions: 4.2.2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
Reported on the mailing list:
{code}
We are trying to build our own custom Karaf 4.2.2 distribution and
when we include the enterprise feature repository along with the
ActiveMQ 5.15.8 feature repository, we get an invalid
org.apache.karaf.features.cfg file which includes 4.2.3-SNAPSHOT
versions of some of the boot features. I have created an example
project here:
https://github.com/jwcarman/custom-karaf-example
If you build it as-is, you'll see the problem. If you comment out the
enterprise feature repo, the problem goes away.
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6077) Feature verify fails with UnsupportedOperationException on some features
Jean-Baptiste Onofré created KARAF-6077: --- Summary: Feature verify fails with UnsupportedOperationException on some features Key: KARAF-6077 URL: https://issues.apache.org/jira/browse/KARAF-6077 Project: Karaf Issue Type: Bug Components: karaf Affects Versions: 4.2.2 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Reported on the mailing list and reproducible on the following example: https://github.com/mrulli/example.feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
