[jira] [Assigned] (KARAF-6360) Intermittent "unknown protocol: blueprint" errors on startup
[ https://issues.apache.org/jira/browse/KARAF-6360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-6360: --- Assignee: Jean-Baptiste Onofré > Intermittent "unknown protocol: blueprint" errors on startup > > > Key: KARAF-6360 > URL: https://issues.apache.org/jira/browse/KARAF-6360 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.2.6 >Reporter: Jesse WHite >Assignee: Jean-Baptiste Onofré >Priority: Major > Attachments: karaf.blueprint.error.log > > > We have some features that use Blueprint which are included in the > featuresBoot and we've been noticing that these fail to load > intermittently on startup. > When it fails, we get a 'java.lang.IllegalStateException: Unknown > protocol: blueprint' when our 'scv' feature. See attached log. > The featuresBoot is defined as follows: > https://github.com/OpenNMS/opennms/blob/bec4abd8e1e75d5a2e23d6b02fc7d93c0414902c/container/shared/src/main/filtered-resources/etc/org.apache.karaf.features.cfg#L34 > Given that the "aries-blueprint" feature is installed *before* the "scv" > feature, I would expect the "blueprint" protocol to be known, but there > appears to be some race condition here. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
[ https://issues.apache.org/jira/browse/KARAF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890406#comment-16890406 ] ASF subversion and git services commented on KARAF-6362: Commit 2f966c675cd478f4cd0a5b6b4cf938a9f0064b88 in karaf's branch refs/heads/master from Freeman Fang [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=2f966c6 ] [KARAF-6362][karaf-maven-plugin] client goal:only one command in script file could be executed > [karaf-maven-plugin] client goal:only the fist command in script file could > be executed > --- > > Key: KARAF-6362 > URL: https://issues.apache.org/jira/browse/KARAF-6362 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > All commands from script are evaluated with same rank and because we have a > Set with Rank as comparator so only one command from the script file is > stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work started] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
[ https://issues.apache.org/jira/browse/KARAF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-6362 started by Freeman Fang. --- > [karaf-maven-plugin] client goal:only the fist command in script file could > be executed > --- > > Key: KARAF-6362 > URL: https://issues.apache.org/jira/browse/KARAF-6362 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > All commands from script are evaluated with same rank and because we have a > Set with Rank as comparator so only one command from the script file is > stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
Freeman Fang created KARAF-6362: --- Summary: [karaf-maven-plugin] client goal:only the fist command in script file could be executed Key: KARAF-6362 URL: https://issues.apache.org/jira/browse/KARAF-6362 Project: Karaf Issue Type: Bug Reporter: Freeman Fang All commands from script are evaluated with same rank and because we have a Set with Rank as comparator so only one command from the script file is stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (KARAF-6362) [karaf-maven-plugin] client goal:only the fist command in script file could be executed
[ https://issues.apache.org/jira/browse/KARAF-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-6362: --- Assignee: Freeman Fang > [karaf-maven-plugin] client goal:only the fist command in script file could > be executed > --- > > Key: KARAF-6362 > URL: https://issues.apache.org/jira/browse/KARAF-6362 > Project: Karaf > Issue Type: Bug >Reporter: Freeman Fang >Assignee: Freeman Fang >Priority: Major > > All commands from script are evaluated with same rank and because we have a > Set with Rank as comparator so only one command from the script file is > stored, others are ignored. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (KARAF-6361) jre.properties lists CORBA packages for jre-11
[ https://issues.apache.org/jira/browse/KARAF-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890185#comment-16890185 ] ASF subversion and git services commented on KARAF-6361: Commit 468a844b433ac35c22455dcb6f1dadc5be7b0602 in karaf's branch refs/heads/master from Freeman Fang [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=468a844 ] [KARAF-6361]jre.properties lists CORBA packages for jre-11 > jre.properties lists CORBA packages for jre-11 > -- > > Key: KARAF-6361 > URL: https://issues.apache.org/jira/browse/KARAF-6361 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.3.0, 4.2.6 >Reporter: Robert Varga >Assignee: Freeman Fang >Priority: Minor > > [https://openjdk.java.net/jeps/320] removed Corba (and others), so the list > of JRE-provided packages is different between jre-9 and jre-11, but jre-11 is > an alias for jre-9. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (KARAF-6344) AsyncLogger fails due to bug in pax-logging
[
https://issues.apache.org/jira/browse/KARAF-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890159#comment-16890159
]
Rico Neubauer edited comment on KARAF-6344 at 7/22/19 1:27 PM:
---
Hi [~gzres], thanks for looking into it.
My startup.properties is this (default, plus lmax):
{code:java}
# Bundles to be started on startup, with startlevel
mvn\:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.6 = 1
mvn\:org.apache.felix/org.apache.felix.metatype/1.2.2 = 5
mvn\:org.apache.karaf.services/org.apache.karaf.services.eventadmin/4.2.6 = 5
mvn\:org.ops4j.pax.url/pax-url-aether/2.6.1 = 5
mvn\:com.lmax/disruptor/3.4.2 = 7
mvn\:org.fusesource.jansi/jansi/1.18 = 8
mvn\:org.ops4j.pax.logging/pax-logging-api/1.10.2 = 8
mvn\:org.ops4j.pax.logging/pax-logging-log4j2/1.10.2 = 8
mvn\:org.apache.felix/org.apache.felix.coordinator/1.0.2 = 9
mvn\:org.apache.felix/org.apache.felix.configadmin/1.9.14 = 10
mvn\:org.apache.felix/org.apache.felix.fileinstall/3.6.4 = 11
mvn\:org.apache.karaf.features/org.apache.karaf.features.core/4.2.6 = 15
mvn\:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.9.0
= 30
{code}
And added lmax artifact of course.
in org.ops4j.pax.logging.cfg I just comment-in the async logging. No further
changes to default distro.
{{Results in the java.lang.ClassNotFoundException:
com.lmax.disruptor.EventFactory not found by
org.ops4j.pax.logging.pax-logging-log4j mentioned before.}}
Uploaded the whole distro with adapted config here:
[https://mft.seeburger.de:443/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download|https://mft.seeburger.de/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download]
was (Author: riconeubauer):
Hi [~gzres], thanks for looking into it.
My startup.properties is this (default, plus lmax):
{code:java}
# Bundles to be started on startup, with startlevel
mvn\:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.6 = 1
mvn\:org.apache.felix/org.apache.felix.metatype/1.2.2 = 5
mvn\:org.apache.karaf.services/org.apache.karaf.services.eventadmin/4.2.6 = 5
mvn\:org.ops4j.pax.url/pax-url-aether/2.6.1 = 5
mvn\:com.lmax/disruptor/3.4.2 = 7
mvn\:org.fusesource.jansi/jansi/1.18 = 8
mvn\:org.ops4j.pax.logging/pax-logging-api/1.10.2 = 8
mvn\:org.ops4j.pax.logging/pax-logging-log4j2/1.10.2 = 8
mvn\:org.apache.felix/org.apache.felix.coordinator/1.0.2 = 9
mvn\:org.apache.felix/org.apache.felix.configadmin/1.9.14 = 10
mvn\:org.apache.felix/org.apache.felix.fileinstall/3.6.4 = 11
mvn\:org.apache.karaf.features/org.apache.karaf.features.core/4.2.6 = 15
mvn\:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.9.0
= 30
{code}
And added lmax artifats of course.
in org.ops4j.pax.logging.cfg I just comment-in the async logging. No further
changes to default distro.
{{Results in the java.lang.ClassNotFoundException:
com.lmax.disruptor.EventFactory not found by
org.ops4j.pax.logging.pax-logging-log4j mentioned before.}}
Uploaded the whole distro with adapted config here:
[https://mft.seeburger.de:443/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download|https://mft.seeburger.de/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download]
> AsyncLogger fails due to bug in pax-logging
> ---
>
> Key: KARAF-6344
> URL: https://issues.apache.org/jira/browse/KARAF-6344
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
>Reporter: Rico Neubauer
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: logging
> Fix For: 4.3.0, 4.2.7
>
>
> Just as reference:
> Karaf 4.2.6 updated to pax-logging 1.10.2, which introduced this regression:
> [https://ops4j1.jira.com/browse/PAXLOGGING-260]
> This leads to the logger breaking if e.g. Karaf gets configured for async
> logging _log4j2.rootLogger.type = asyncRoot_ in logging config. Exception
> below.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (KARAF-6344) AsyncLogger fails due to bug in pax-logging
[
https://issues.apache.org/jira/browse/KARAF-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16890159#comment-16890159
]
Rico Neubauer commented on KARAF-6344:
--
Hi [~gzres], thanks for looking into it.
My startup.properties is this (default, plus lmax):
{code:java}
# Bundles to be started on startup, with startlevel
mvn\:org.apache.karaf.features/org.apache.karaf.features.extension/4.2.6 = 1
mvn\:org.apache.felix/org.apache.felix.metatype/1.2.2 = 5
mvn\:org.apache.karaf.services/org.apache.karaf.services.eventadmin/4.2.6 = 5
mvn\:org.ops4j.pax.url/pax-url-aether/2.6.1 = 5
mvn\:com.lmax/disruptor/3.4.2 = 7
mvn\:org.fusesource.jansi/jansi/1.18 = 8
mvn\:org.ops4j.pax.logging/pax-logging-api/1.10.2 = 8
mvn\:org.ops4j.pax.logging/pax-logging-log4j2/1.10.2 = 8
mvn\:org.apache.felix/org.apache.felix.coordinator/1.0.2 = 9
mvn\:org.apache.felix/org.apache.felix.configadmin/1.9.14 = 10
mvn\:org.apache.felix/org.apache.felix.fileinstall/3.6.4 = 11
mvn\:org.apache.karaf.features/org.apache.karaf.features.core/4.2.6 = 15
mvn\:org.apache.servicemix.specs/org.apache.servicemix.specs.activation-api-1.1/2.9.0
= 30
{code}
And added lmax artifats of course.
in org.ops4j.pax.logging.cfg I just comment-in the async logging. No further
changes to default distro.
{{Results in the java.lang.ClassNotFoundException:
com.lmax.disruptor.EventFactory not found by
org.ops4j.pax.logging.pax-logging-log4j mentioned before.}}
Uploaded the whole distro with adapted config here:
[https://mft.seeburger.de:443/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download|https://mft.seeburger.de/portal-seefx/~public/da51bce9-0c45-4956-ab12-8cace8edd513?download]
> AsyncLogger fails due to bug in pax-logging
> ---
>
> Key: KARAF-6344
> URL: https://issues.apache.org/jira/browse/KARAF-6344
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.6
>Reporter: Rico Neubauer
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: logging
> Fix For: 4.3.0, 4.2.7
>
>
> Just as reference:
> Karaf 4.2.6 updated to pax-logging 1.10.2, which introduced this regression:
> [https://ops4j1.jira.com/browse/PAXLOGGING-260]
> This leads to the logger breaking if e.g. Karaf gets configured for async
> logging _log4j2.rootLogger.type = asyncRoot_ in logging config. Exception
> below.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
