[jira] [Commented] (KARAF-5574) Upgrade to Pax Web 6.1.2/Jetty 9.4.6
[ https://issues.apache.org/jira/browse/KARAF-5574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16337685#comment-16337685 ] Achim Nierbeck commented on KARAF-5574: --- I know this doesn't belong here, but Jetty 9.4 should go into a Pax Web 7. Especially since 9.4 is the first jetty fully supporting J9 just sayin' > Upgrade to Pax Web 6.1.2/Jetty 9.4.6 > > > Key: KARAF-5574 > URL: https://issues.apache.org/jira/browse/KARAF-5574 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > > In order to align with Camel, we should upgrade to Pax Web 6.1.2 that will > provide Jetty 9.4.6 support. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5509) http-whiteboard resources are not published properly
[
https://issues.apache.org/jira/browse/KARAF-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16269496#comment-16269496
]
Achim Nierbeck commented on KARAF-5509:
---
might be related to this issue:
https://ops4j1.jira.com/browse/PAXWEB-1085
> http-whiteboard resources are not published properly
>
>
> Key: KARAF-5509
> URL: https://issues.apache.org/jira/browse/KARAF-5509
> Project: Karaf
> Issue Type: Bug
> Components: karaf-scr
>Affects Versions: 4.1.3, 4.2.0.M1
>Reporter: Alexander Domke
>Assignee: Jean-Baptiste Onofré
>
> Hello everybody,
> the feature http-whiteboard does not work as expected.
> I have built a simple osgi application (jar bundle) with the following
> component:
> {code:java}
> import org.osgi.service.component.annotations.Component;
> @Component (service = HomepageResources.class, property =
> {"osgi.http.whiteboard.resource.pattern = / static / *",
> "osgi.http.whiteboard.resource.prefix = / static"})
> public class HomepageResources {}
> {code}
> After installing the http-whiteboard and scr features my bundle is active but
> my resource is not available at http://localhost:8181/static/img/profile.png.
> Apache Karaf bundle:list output - All bundles are active / no exceptions in
> log
> START LEVEL 100 , List Threshold: 0
> ID | State| Lvl | Version | Name
> +--+-+---+-
> 0 | Active | 0 | 5.6.8 | System Bundle, Fragments: 1
> 1 | Resolved | 1 | 4.1.3 | Apache Karaf :: Features ::
> Extension, Hosts: 0
> 2 | Active | 5 | 1.1.4 | Apache Felix Metatype Service
> 3 | Active | 5 | 4.1.3 | Apache Karaf :: OSGi Services
> :: EventAdmin
> 4 | Active | 5 | 2.5.3 | OPS4J Pax Url - aether:
> 5 | Active | 8 | 1.10.1| OPS4J Pax Logging - API
> 6 | Active | 8 | 1.10.1| OPS4J Pax Logging - Log4j v2
> 7 | Active | 10 | 1.8.16| Apache Felix Configuration
> Admin Service
> 8 | Active | 11 | 3.5.8 | Apache Felix File Install
> 9 | Active | 15 | 4.1.3 | Apache Karaf :: Features ::
> Core
> 10 | Active | 20 | 1.0.1 | Apache Aries Blueprint API
> 11 | Active | 20 | 1.1.0 | Apache Aries Blueprint CM
> 12 | Active | 20 | 1.8.3 | Apache Aries Blueprint Core
> 13 | Active | 30 | 1.1.5 | Apache Aries JMX API
> 14 | Active | 30 | 1.1.5 | Apache Aries JMX Blueprint API
> 15 | Active | 30 | 1.1.5 | Apache Aries JMX Blueprint Core
> 16 | Active | 30 | 1.1.7 | Apache Aries JMX Core
> 17 | Active | 30 | 1.1.5 | Apache Aries Whiteboard
> support for JMX DynamicMBean services
> 18 | Active | 20 | 1.1.1 | Apache Aries Proxy Service
> 19 | Active | 20 | 1.1.3 | Apache Aries Util
> 20 | Active | 30 | 4.1.3 | Apache Karaf :: Bundle ::
> BlueprintStateService
> 21 | Active | 30 | 4.1.3 | Apache Karaf :: Bundle :: Core
> 22 | Active | 30 | 4.1.3 | Apache Karaf :: ConfigAdmin ::
> Core
> 23 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer ::
> Blueprint
> 24 | Active | 26 | 4.1.3 | Apache Karaf :: Deployer ::
> Features
> 25 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer ::
> Karaf Archive (.kar)
> 26 | Active | 24 | 4.1.3 | Apache Karaf :: Deployer ::
> Wrap Non OSGi Jar
> 27 | Active | 30 | 4.1.3 | Apache Karaf :: Diagnostic ::
> Core
> 28 | Active | 80 | 4.1.3 | Apache Karaf :: OSGi Services
> :: Event
> 29 | Active | 30 | 4.1.3 | Apache Karaf :: Features ::
> Command
> 30 | Active | 30 | 4.1.3 | Apache Karaf :: Instance ::
> Core
> 31 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS ::
> Blueprint :: Config
> 32 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Command
> 33 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Config
> 34 | Active | 30 | 4.1.3 | Apache Karaf :: JAAS :: Modules
> 35 | Active | 30 | 4.1.3 | Apache Karaf :: KAR :: Core
> 36 | Active | 30 | 4.1.3 | Apache Karaf :: Log :: Core
> 37 | Active | 30 | 4.1.3 | Apache Karaf :: Management
> 38 | Active | 30 | 4.1.3 | Apache Karaf :: Package :: Core
> 39 | Active | 30 | 4.1.3 | Apache Karaf ::
[jira] [Commented] (KARAF-5471) Jetty version in Karaf and Pax Web are not aligned
[ https://issues.apache.org/jira/browse/KARAF-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16245466#comment-16245466 ] Achim Nierbeck commented on KARAF-5471: --- (y) > Jetty version in Karaf and Pax Web are not aligned > -- > > Key: KARAF-5471 > URL: https://issues.apache.org/jira/browse/KARAF-5471 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.3 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.4 > > > The Karaf (4.1.3) standard feature has a dependency to Jetty 9.3.15.v20161220 > whereas Pax Web (6.0.7) has a dependency to Jetty 9.3.14.v20161028. > Both should be aligned to be consistent. > Generally speaking, Karaf should not define a dependency to Jetty and should > delegate to Pax Web. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5460) Maven Plugin fails on verify due to missing class org/ops4j/pax/url/mvn/MavenResolver
Achim Nierbeck created KARAF-5460: - Summary: Maven Plugin fails on verify due to missing class org/ops4j/pax/url/mvn/MavenResolver Key: KARAF-5460 URL: https://issues.apache.org/jira/browse/KARAF-5460 Project: Karaf Issue Type: Bug Affects Versions: 4.1.3 Reporter: Achim Nierbeck When karaf-maven-plugin is run in verify mode the following error appears: Execution default-verify of goal org.apache.karaf.tooling:karaf-maven-plugin:4.1.3:verify failed: A required class was missing while executing org.apache.karaf.tooling:karaf-maven-plugin:4.1.3:verify: Lorg/ops4j/pax/url/mvn/MavenResolver; -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262
[ https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-5423. --- Resolution: Fixed > Karaf is flagged as vulnerable to CVE-2015-5262 > --- > > Key: KARAF-5423 > URL: https://issues.apache.org/jira/browse/KARAF-5423 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: Fabian Lange >Assignee: Achim Nierbeck > Fix For: 4.2.0, 4.1.3 > > > Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is > flagged vulnerable to CVE-2015-5262. > I already provided a patch upstream > https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues > in > https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510 > but it would require a pax-url release first followed by a dependency upgrade > in karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262
[ https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-5423: -- Fix Version/s: 4.1.3 > Karaf is flagged as vulnerable to CVE-2015-5262 > --- > > Key: KARAF-5423 > URL: https://issues.apache.org/jira/browse/KARAF-5423 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: Fabian Lange >Assignee: Achim Nierbeck > Fix For: 4.2.0, 4.1.3 > > > Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is > flagged vulnerable to CVE-2015-5262. > I already provided a patch upstream > https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues > in > https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510 > but it would require a pax-url release first followed by a dependency upgrade > in karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262
[ https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-5423: -- Fix Version/s: 4.2.0 > Karaf is flagged as vulnerable to CVE-2015-5262 > --- > > Key: KARAF-5423 > URL: https://issues.apache.org/jira/browse/KARAF-5423 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: Fabian Lange >Assignee: Achim Nierbeck > Fix For: 4.2.0 > > > Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is > flagged vulnerable to CVE-2015-5262. > I already provided a patch upstream > https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues > in > https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510 > but it would require a pax-url release first followed by a dependency upgrade > in karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262
[ https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-5423: - Assignee: Achim Nierbeck > Karaf is flagged as vulnerable to CVE-2015-5262 > --- > > Key: KARAF-5423 > URL: https://issues.apache.org/jira/browse/KARAF-5423 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: Fabian Lange >Assignee: Achim Nierbeck > > Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is > flagged vulnerable to CVE-2015-5262. > I already provided a patch upstream > https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues > in > https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510 > but it would require a pax-url release first followed by a dependency upgrade > in karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262
[ https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5423 started by Achim Nierbeck. - > Karaf is flagged as vulnerable to CVE-2015-5262 > --- > > Key: KARAF-5423 > URL: https://issues.apache.org/jira/browse/KARAF-5423 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.2 >Reporter: Fabian Lange >Assignee: Achim Nierbeck > > Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is > flagged vulnerable to CVE-2015-5262. > I already provided a patch upstream > https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues > in > https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510 > but it would require a pax-url release first followed by a dependency upgrade > in karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5314) The performance of profile builder used by karaf maven plugin has reduced significantly in 4.1 compared to 4.0
[ https://issues.apache.org/jira/browse/KARAF-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16134406#comment-16134406 ] Achim Nierbeck commented on KARAF-5314: --- Do we have a "high load test" available? In that case I'd try if parallel streams might help to increase performance when doing the streaming. > The performance of profile builder used by karaf maven plugin has reduced > significantly in 4.1 compared to 4.0 > -- > > Key: KARAF-5314 > URL: https://issues.apache.org/jira/browse/KARAF-5314 > Project: Karaf > Issue Type: Bug >Reporter: Vinay Shankar > Fix For: 4.1.3 > > > The performance of profile builder used by karaf maven plugin has reduced > significantly in 4.1 compared to 4.0. > The java streams API is being used in 4.1 to filter our the required features > from the set of all features present in the repositories that are part of the > profile. This is done in the "addFeatures" method in the "Builder.java" class > in the "org.apache.karaf.profile.core" bundle. This change (from 4.0) has > drastically reduced the performance. For a profile with ~900 features in all > the repositories in the profile and ~300 required features from a highly > complex feature dependency tree, this function is taking around 13min to > complete. The same execution took around 3-5min in 4.0 (where simple for > loops were being used). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4803) Turn off Karaf configuration persistence manager
[ https://issues.apache.org/jira/browse/KARAF-4803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4803: -- Fix Version/s: 4.2.0 > Turn off Karaf configuration persistence manager > > > Key: KARAF-4803 > URL: https://issues.apache.org/jira/browse/KARAF-4803 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Reporter: Dominik Przybysz > Fix For: 4.2.0 > > > I have provided my own PersistenceManager which persists configuration in > files not ending with cfg or config. > If I use karaf commands from config:* then for each update there is created > .cfg file in etc/ > It should be configurable to turn off this feature. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5200) A dependency declared feature isn't installed as boot-feature
[ https://issues.apache.org/jira/browse/KARAF-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-5200: -- Description: A custom karaf configured to have cellar-shell feature as transitive dependency in a boot-feature, doesn't provide the cellar-shell functionality. https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Feature/src/main/feature/feature.xml#L70 the corresponding customized Karaf build: https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Karaf-Cluster/pom.xml#L174 was: A custom karaf configured to have cellar-shell feature as transitive dependency in a boot-feature, doesn't provide the cellar-shell functionality. https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Feature/src/main/feature/feature.xml#L70 > A dependency declared feature isn't installed as boot-feature > - > > Key: KARAF-5200 > URL: https://issues.apache.org/jira/browse/KARAF-5200 > Project: Karaf > Issue Type: Bug > Components: cellar-features, karaf-feature >Affects Versions: 4.1.1, cellar-4.1.0 >Reporter: Achim Nierbeck > > A custom karaf configured to have cellar-shell feature as transitive > dependency in a boot-feature, doesn't provide the cellar-shell functionality. > https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Feature/src/main/feature/feature.xml#L70 > the corresponding customized Karaf build: > https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Karaf-Cluster/pom.xml#L174 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KARAF-5185) Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa feature
[ https://issues.apache.org/jira/browse/KARAF-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-5185: -- Fix Version/s: 4.2.0 > Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa > feature > - > > Key: KARAF-5185 > URL: https://issues.apache.org/jira/browse/KARAF-5185 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.1.1 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.2.0 > > > If one installs next to the karaf enterprise feature also the aries jpa > feature there are two features defined with the same name and verison > jpa/2.6.0 > Instead of containing almost the same feature in the karaf enterprise feature > it would be best to omit it there and rather reference the aries feature > definition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-5185) Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa feature
[ https://issues.apache.org/jira/browse/KARAF-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-5185. --- Resolution: Fixed Assignee: Achim Nierbeck > Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa > feature > - > > Key: KARAF-5185 > URL: https://issues.apache.org/jira/browse/KARAF-5185 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.1.1 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > > If one installs next to the karaf enterprise feature also the aries jpa > feature there are two features defined with the same name and verison > jpa/2.6.0 > Instead of containing almost the same feature in the karaf enterprise feature > it would be best to omit it there and rather reference the aries feature > definition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5201) cluster:feature-* commands are gone
Achim Nierbeck created KARAF-5201: - Summary: cluster:feature-* commands are gone Key: KARAF-5201 URL: https://issues.apache.org/jira/browse/KARAF-5201 Project: Karaf Issue Type: Bug Components: cellar-features, cellar-shell Affects Versions: cellar-4.1.0 Reporter: Achim Nierbeck Having a customized Karaf with cellar installed, the cellar-shell is missing (see KARAF-5200), if that feature is installed later, the cluster:feature-* commands are missing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5200) A dependency declared feature isn't installed as boot-feature
Achim Nierbeck created KARAF-5200: - Summary: A dependency declared feature isn't installed as boot-feature Key: KARAF-5200 URL: https://issues.apache.org/jira/browse/KARAF-5200 Project: Karaf Issue Type: Bug Components: cellar-features, karaf-feature Affects Versions: cellar-4.1.0, 4.1.1 Reporter: Achim Nierbeck A custom karaf configured to have cellar-shell feature as transitive dependency in a boot-feature, doesn't provide the cellar-shell functionality. https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Feature/src/main/feature/feature.xml#L70 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5191) can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features
[ https://issues.apache.org/jira/browse/KARAF-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045550#comment-16045550 ] Achim Nierbeck commented on KARAF-5191: --- I think that one is already fixed. But the other way round, someone wanted to install 6.0.4 instead of 6.0.3. It's been fixed in the next Karaf 4.2.0 line. afaik the http and web wrapper features are causing this. Otherwise there is no reason why the pax web version needs to be "fix" > can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > -- > > Key: KARAF-5191 > URL: https://issues.apache.org/jira/browse/KARAF-5191 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Steven Spungin > > I am trying to install pax-war/6.0.2. The current Karaf uses pax-war/6.0.3. > If I add mvn:org.ops4j.pax.web/pax-web-features/6.0.2/xml/features and then > install pax-war/6.0.2, features from both 6.0.2 and 6.0.3 are installed. > Now, if I try to uninstall > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features, I get a confirm > message but the repo is not removed. > ``` > karaf@root()> repo-remove > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > 08:26:31 > Removing features repository > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > ``` > ``` > pax-jetty │ 9.3.14.v20161028 │ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide Jetty engine support > pax-http-jetty │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ > pax-http│ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Implementation of the OSGI HTTP Service > pax-http-whiteboard │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide HTTP Whiteboard pattern support > pax-jetty │ 9.3.15.v20161220 │ │ Started │ > org.ops4j.pax.web-6.0.2 │ Provide Jetty engine support > pax-http-jetty │ 6.0.2│ │ Started │ > org.ops4j.pax.web-6.0.2 │ > pax-war │ 6.0.2│ x│ Started │ > org.ops4j.pax.web-6.0.2 │ Provide support of a full WebContainer > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5191) can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features
[ https://issues.apache.org/jira/browse/KARAF-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16045544#comment-16045544 ] Achim Nierbeck commented on KARAF-5191: --- that's most likely because this repo is referenced by the std. feature. > can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > -- > > Key: KARAF-5191 > URL: https://issues.apache.org/jira/browse/KARAF-5191 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Steven Spungin > > I am trying to install pax-war/6.0.2. The current Karaf uses pax-war/6.0.3. > If I add mvn:org.ops4j.pax.web/pax-web-features/6.0.2/xml/features and then > install pax-war/6.0.2, features from both 6.0.2 and 6.0.3 are installed. > Now, if I try to uninstall > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features, I get a confirm > message but the repo is not removed. > ``` > karaf@root()> repo-remove > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > 08:26:31 > Removing features repository > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > ``` > ``` > pax-jetty │ 9.3.14.v20161028 │ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide Jetty engine support > pax-http-jetty │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ > pax-http│ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Implementation of the OSGI HTTP Service > pax-http-whiteboard │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide HTTP Whiteboard pattern support > pax-jetty │ 9.3.15.v20161220 │ │ Started │ > org.ops4j.pax.web-6.0.2 │ Provide Jetty engine support > pax-http-jetty │ 6.0.2│ │ Started │ > org.ops4j.pax.web-6.0.2 │ > pax-war │ 6.0.2│ x│ Started │ > org.ops4j.pax.web-6.0.2 │ Provide support of a full WebContainer > ``` -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
[ https://issues.apache.org/jira/browse/KARAF-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-5186. --- Resolution: Fixed > [DECANTER] - Fails work in case the event topic contains arbitrary characters > like % > > > Key: KARAF-5186 > URL: https://issues.apache.org/jira/browse/KARAF-5186 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
[ https://issues.apache.org/jira/browse/KARAF-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-5186 started by Achim Nierbeck. - > [DECANTER] - Fails work in case the event topic contains arbitrary characters > like % > > > Key: KARAF-5186 > URL: https://issues.apache.org/jira/browse/KARAF-5186 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
[ https://issues.apache.org/jira/browse/KARAF-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-5186: - Assignee: Achim Nierbeck (was: Jean-Baptiste Onofré) > [DECANTER] - Fails work in case the event topic contains arbitrary characters > like % > > > Key: KARAF-5186 > URL: https://issues.apache.org/jira/browse/KARAF-5186 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.3.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
[
https://issues.apache.org/jira/browse/KARAF-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042632#comment-16042632
]
Achim Nierbeck edited comment on KARAF-5186 at 6/8/17 12:40 PM:
this one is causing issues:
{code}
log = (GridLoggerProxy)cfg.getGridLogger().getLogger(
getClass().getName() + (igniteInstanceName != null ? '%' + igniteInstanceName :
""));
{code}
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L776
so in the worst case it's both
was (Author: achim_nierbeck):
this one is causing issues:
{code}
log = (GridLoggerProxy)cfg.getGridLogger().getLogger(
getClass().getName() + (igniteInstanceName != null ? '%' + igniteInstanceName :
""));
{code}
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L776
> [DECANTER] - Fails work in case the event topic contains arbitrary characters
> like %
>
>
> Key: KARAF-5186
> URL: https://issues.apache.org/jira/browse/KARAF-5186
> Project: Karaf
> Issue Type: Bug
> Components: decanter
>Affects Versions: decanter-1.3.0
>Reporter: Achim Nierbeck
>Assignee: Jean-Baptiste Onofré
> Fix For: decanter-1.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
[
https://issues.apache.org/jira/browse/KARAF-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16042632#comment-16042632
]
Achim Nierbeck commented on KARAF-5186:
---
this one is causing issues:
{code}
log = (GridLoggerProxy)cfg.getGridLogger().getLogger(
getClass().getName() + (igniteInstanceName != null ? '%' + igniteInstanceName :
""));
{code}
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/IgniteKernal.java#L776
> [DECANTER] - Fails work in case the event topic contains arbitrary characters
> like %
>
>
> Key: KARAF-5186
> URL: https://issues.apache.org/jira/browse/KARAF-5186
> Project: Karaf
> Issue Type: Bug
> Components: decanter
>Affects Versions: decanter-1.3.0
>Reporter: Achim Nierbeck
>Assignee: Jean-Baptiste Onofré
> Fix For: decanter-1.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (KARAF-5186) [DECANTER] - Fails work in case the event topic contains arbitrary characters like %
Achim Nierbeck created KARAF-5186: - Summary: [DECANTER] - Fails work in case the event topic contains arbitrary characters like % Key: KARAF-5186 URL: https://issues.apache.org/jira/browse/KARAF-5186 Project: Karaf Issue Type: Bug Components: decanter Affects Versions: decanter-1.3.0 Reporter: Achim Nierbeck -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5185) Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa feature
Achim Nierbeck created KARAF-5185: - Summary: Karaf enterprise feature shall omit the jpa feature in favor of the aries jpa feature Key: KARAF-5185 URL: https://issues.apache.org/jira/browse/KARAF-5185 Project: Karaf Issue Type: Improvement Components: karaf-feature Affects Versions: 4.1.1 Reporter: Achim Nierbeck If one installs next to the karaf enterprise feature also the aries jpa feature there are two features defined with the same name and verison jpa/2.6.0 Instead of containing almost the same feature in the karaf enterprise feature it would be best to omit it there and rather reference the aries feature definition. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5165) Custom Distributions: Pax-Web gets installed twice
[
https://issues.apache.org/jira/browse/KARAF-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030806#comment-16030806
]
Achim Nierbeck commented on KARAF-5165:
---
This could be becaues of the http or the war feature, which itself reference
the "older" Pax-Web versions.
In the Pax Web Karaf integration tests, it's done without the http and war
feature.
> Custom Distributions: Pax-Web gets installed twice
> --
>
> Key: KARAF-5165
> URL: https://issues.apache.org/jira/browse/KARAF-5165
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.1.1
>Reporter: Stephan Siano
>Priority: Minor
> Attachments: pom.xml
>
>
> When I create a custom distribution with the attached pom, which tries to
> exchange Pax-Web with a newer version, Pax-Web gets installed twice:
> {noformat}
> karaf@root()> feature:list -i
> Name| Version | Required | State | Repository
> | Description
> +--+--+-+-+--
> pax-jetty | 9.3.14.v20161028 | | Started |
> org.ops4j.pax.web-6.0.4 | Provide Jetty engine support
> pax-http-jetty | 6.0.4| | Started |
> org.ops4j.pax.web-6.0.4 |
> pax-http| 6.0.4| | Started |
> org.ops4j.pax.web-6.0.4 | Implementation of the OSGI HTTP Service
> pax-http-whiteboard | 6.0.4| | Started |
> org.ops4j.pax.web-6.0.4 | Provide HTTP Whiteboard pattern support
> pax-war | 6.0.4| | Started |
> org.ops4j.pax.web-6.0.4 | Provide support of a full WebContainer
> pax-http-tomcat | 6.0.4| | Started |
> org.ops4j.pax.web-6.0.4 | Provide Tomcat support
> pax-war-tomcat | 6.0.4| x| Started |
> org.ops4j.pax.web-6.0.4 |
> aries-proxy | 4.1.1| | Started | standard-4.1.1
> | Aries Proxy
> aries-blueprint | 4.1.1| | Started | standard-4.1.1
> | Aries Blueprint
> feature | 4.1.1| | Started | standard-4.1.1
> | Features Support
> shell | 4.1.1| | Started | standard-4.1.1
> | Karaf Shell
> shell-compat| 4.1.1| | Started | standard-4.1.1
> | Karaf Shell Compatibility
> deployer| 4.1.1| | Started | standard-4.1.1
> | Karaf Deployer
> bundle | 4.1.1| | Started | standard-4.1.1
> | Provide Bundle support
> config | 4.1.1| | Started | standard-4.1.1
> | Provide OSGi ConfigAdmin support
> diagnostic | 4.1.1| | Started | standard-4.1.1
> | Provide Diagnostic support
> instance| 4.1.1| | Started | standard-4.1.1
> | Provide Instance support
> jaas| 4.1.1| | Started | standard-4.1.1
> | Provide JAAS support
> log | 4.1.1| | Started | standard-4.1.1
> | Provide Log support
> package | 4.1.1| | Started | standard-4.1.1
> | Package commands and mbeans
> service | 4.1.1| | Started | standard-4.1.1
> | Provide Service support
> system | 4.1.1| | Started | standard-4.1.1
> | Provide System support
> kar | 4.1.1| | Started | standard-4.1.1
> | Provide KAR (KARaf archive) support
> ssh | 4.1.1| | Started | standard-4.1.1
> | Provide a SSHd server on Karaf
> management | 4.1.1| | Started | standard-4.1.1
> | Provide a JMX MBeanServer and a set of MBeans in
> eventadmin | 4.1.1| x| Started | standard-4.1.1
> | OSGi Event Admin service specification for event-
> scr | 4.1.1| | Started | standard-4.1.1
> | Declarative Service support
> wrap| 0.0.0| | Started | standard-4.1.1
> | Wrap URL handler
> standard| 4.1.1| x| Started | standard-4.1.1
> | Wrap feature describing all features part of a st
> pax-jetty | 9.3.14.v20161028 | | Started |
> org.ops4j.pax.web-6.0.3 | Provide Jetty engine support
> pax-http-jetty | 6.0.3| | Started |
> org.ops4j.pax.web-6.0.3 |
> pax-http-whiteboard |
[jira] [Resolved] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-5021. --- Resolution: Fixed > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Achim Nierbeck > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (KARAF-5032) Upgrade to Pax Web 6.0.3
[ https://issues.apache.org/jira/browse/KARAF-5032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-5032. --- Resolution: Fixed > Upgrade to Pax Web 6.0.3 > > > Key: KARAF-5032 > URL: https://issues.apache.org/jira/browse/KARAF-5032 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KARAF-5032) Upgrade to Pax Web 6.0.3
Achim Nierbeck created KARAF-5032: - Summary: Upgrade to Pax Web 6.0.3 Key: KARAF-5032 URL: https://issues.apache.org/jira/browse/KARAF-5032 Project: Karaf Issue Type: Dependency upgrade Components: karaf-webcontainer Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: 4.1.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15931402#comment-15931402 ] Achim Nierbeck commented on KARAF-5021: --- see KARAF-5032 > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Achim Nierbeck > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-5021: - Assignee: Achim Nierbeck (was: Jean-Baptiste Onofré) > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Achim Nierbeck > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903984#comment-15903984 ] Achim Nierbeck commented on KARAF-5021: --- We need to upgrade to Pax-Web 6.0.3-SNAPSHOT to have this now ... > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903425#comment-15903425 ] Achim Nierbeck edited comment on KARAF-5021 at 3/9/17 5:20 PM: --- Oh wait, we have an issue about that in Pax-Web with an upgrade to 9.3.16, that should also do Could you test if that also works for CXF? https://ops4j1.jira.com/browse/PAXWEB-1065 https://github.com/ops4j/org.ops4j.pax.web/commit/5d7650cb53516f945375a980aad780850c4404c7 that's already Pax-Web 6.0.3 we should check with that snapshot version was (Author: achim_nierbeck): Oh wait, we have an issue about that in Pax-Web with an upgrade to 9.3.16, that should also do Could you test if that also works for CXF? https://ops4j1.jira.com/browse/PAXWEB-1065 https://github.com/ops4j/org.ops4j.pax.web/commit/5d7650cb53516f945375a980aad780850c4404c7 > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903363#comment-15903363 ] Achim Nierbeck commented on KARAF-5021: --- oh boy ... that's fubar ... so lets turn back the version ... need to change some other issues to re-opened than again :/ > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903230#comment-15903230 ] Achim Nierbeck commented on KARAF-5021: --- Why is there a hard requirement for CXF on a certain Jetty version in the first place? That's creepy by itself already ... but if it has to ... I'm not going to block it ... but we should make sure we don't introduce some security issues by turning back to the old version. We loose functionality on the Websocket front ... people already are using ... :/ https://ops4j1.jira.com/browse/PAXWEB-1065 > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-5021) Downgrade to Jetty 9.3.14
[ https://issues.apache.org/jira/browse/KARAF-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15903150#comment-15903150 ] Achim Nierbeck commented on KARAF-5021: --- we had a reason for bumping to that version ... > Downgrade to Jetty 9.3.14 > - > > Key: KARAF-5021 > URL: https://issues.apache.org/jira/browse/KARAF-5021 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.1 > > > Due to a bunch of breaking changes, and in order to smoothly work with CXF, > it would be better to downgrade to Jetty 9.3.14. > I will create the Jetty at Pax Web too (cc [~achim_nierbeck]). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KARAF-201) Add post feature installation triggers
[
https://issues.apache.org/jira/browse/KARAF-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853912#comment-15853912
]
Achim Nierbeck commented on KARAF-201:
--
hmm ... for DB migration you might also want to take a look at [PAX
Warp|http://ops4j.github.io/pax/warp/0.7.0/index.html]
> Add post feature installation triggers
> --
>
> Key: KARAF-201
> URL: https://issues.apache.org/jira/browse/KARAF-201
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-core, karaf-feature
>Reporter: Guillaume Nodet
> Fix For: 4.1.1
>
>
> Something like:
> {code}
>
> // do anything using gogo commands
>
> {code}
> The result could be displayed to the user so that the installation could give
> him some information (manual steps, or whatever), though it may need a
> separate element.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4944. --- Resolution: Fixed > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827795#comment-15827795 ] Achim Nierbeck commented on KARAF-4944: --- updated to Pax Web 6.0.2-SNAPSHOT with this commit: http://git-wip-us.apache.org/repos/asf/karaf/commit/2f3a38c6 > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827796#comment-15827796 ] Achim Nierbeck commented on KARAF-4944: --- leaving in progress till Pax Web 6.0.2 is released > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4944 started by Achim Nierbeck. - > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15827791#comment-15827791 ] Achim Nierbeck commented on KARAF-4944: --- I'll do, that shouldn't be to hard ;) > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4944) Upgrade to Pax Web 6.0.2
[ https://issues.apache.org/jira/browse/KARAF-4944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-4944: - Assignee: Achim Nierbeck (was: Jean-Baptiste Onofré) > Upgrade to Pax Web 6.0.2 > > > Key: KARAF-4944 > URL: https://issues.apache.org/jira/browse/KARAF-4944 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Oliver Lietz >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > [~achim_nierbeck], can you update Pax Web to 6.0.2-SNAPSHOT? That would allow > me to follow 4.1.0-SNAPSHOT _head_ without having to rebuild myself > (SLING-6411). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4931) Static Profile generation fails if configfile element contains a placeholder
[
https://issues.apache.org/jira/browse/KARAF-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck resolved KARAF-4931.
---
Resolution: Fixed
Assignee: Achim Nierbeck
Fix Version/s: 4.1.0
fixed with:
http://git-wip-us.apache.org/repos/asf/karaf/commit/e6e0928b
> Static Profile generation fails if configfile element contains a placeholder
>
>
> Key: KARAF-4931
> URL: https://issues.apache.org/jira/browse/KARAF-4931
> Project: Karaf
> Issue Type: Bug
> Components: karaf-profile
>Affects Versions: 4.1.0, 4.0.8
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
>
> The demo/profiles/static fails in case of a feature file containing a
> placeholder for a file location
> karaf.etc in this sample
> {code}
> ...
>
> finalname="${karaf.etc}/jetty.xml">mvn:org.ops4j.pax.web/pax-web-features/${project.version}/xml/jettyconfig
>
> org.osgi.service.http.port=8181
> javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
> org.ops4j.pax.web.config.file=${karaf.etc}/jetty.xml
>
> ...
> {code}
> see also:
> https://ops4j1.jira.com/browse/PAXWEB-999
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4931) Static Profile generation fails if configfile element contains a placeholder
Achim Nierbeck created KARAF-4931:
-
Summary: Static Profile generation fails if configfile element
contains a placeholder
Key: KARAF-4931
URL: https://issues.apache.org/jira/browse/KARAF-4931
Project: Karaf
Issue Type: Bug
Components: karaf-profile
Affects Versions: 4.0.8, 4.1.0
Reporter: Achim Nierbeck
The demo/profiles/static fails in case of a feature file containing a
placeholder for a file location
karaf.etc in this sample
{code}
...
mvn:org.ops4j.pax.web/pax-web-features/${project.version}/xml/jettyconfig
org.osgi.service.http.port=8181
javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
org.ops4j.pax.web.config.file=${karaf.etc}/jetty.xml
...
{code}
see also:
https://ops4j1.jira.com/browse/PAXWEB-999
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4913) Upgrade to Pax-Web 6.0.1
[ https://issues.apache.org/jira/browse/KARAF-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4913. --- Resolution: Fixed > Upgrade to Pax-Web 6.0.1 > - > > Key: KARAF-4913 > URL: https://issues.apache.org/jira/browse/KARAF-4913 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > Upgrade to version 6.0.1-SNAPSHOT first, this is a requirement to fix > KARAF-4912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck updated KARAF-4912:
--
Fix Version/s: (was: 4.1.0)
4.2.0
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.2.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15798300#comment-15798300
]
Achim Nierbeck commented on KARAF-4912:
---
Event though this issue has been addressed by a Pax-web 6.0.1 snapshot version.
We decided to move against a full support of JDK9 (see also dev mailinglist)
As ASM 6.0 is still ALPHA and a lot of other projects also need to make sure
they are JDK9 compatible (not even released yet)
We can't have this for a Karaf 4.1, JDK 9 full support will be targeted for
Karaf 4.2, because of all those dependencies.
sorry for the inconvenience.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4916) Upgrade Aries SPI-Fly dependencies
[ https://issues.apache.org/jira/browse/KARAF-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4916: -- Labels: java9 (was: ) > Upgrade Aries SPI-Fly dependencies > -- > > Key: KARAF-4916 > URL: https://issues.apache.org/jira/browse/KARAF-4916 > Project: Karaf > Issue Type: Dependency upgrade >Affects Versions: 4.1.0 >Reporter: Achim Nierbeck > Labels: java9 > Fix For: 4.1.0 > > > An update to a newer version of SPI-Fly is needed (Aries dependencies) > This issue is more a reminder, to not forget to set the correct Aries > dependencies for Java 9. > As SPI-Fly also needs an update due to ASM 6.0 ALPHA > ARIES-1646 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4916) Upgrade Aries SPI-Fly dependencies
Achim Nierbeck created KARAF-4916: - Summary: Upgrade Aries SPI-Fly dependencies Key: KARAF-4916 URL: https://issues.apache.org/jira/browse/KARAF-4916 Project: Karaf Issue Type: Dependency upgrade Affects Versions: 4.1.0 Reporter: Achim Nierbeck Fix For: 4.1.0 An update to a newer version of SPI-Fly is needed (Aries dependencies) This issue is more a reminder, to not forget to set the correct Aries dependencies for Java 9. As SPI-Fly also needs an update due to ASM 6.0 ALPHA ARIES-1646 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4913) Upgrade to Pax-Web 6.0.1
[ https://issues.apache.org/jira/browse/KARAF-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791386#comment-15791386 ] Achim Nierbeck commented on KARAF-4913: --- This is only a snapshot version, this issue needs to be opened until a release of Pax-web 6.0.1 is available. > Upgrade to Pax-Web 6.0.1 > - > > Key: KARAF-4913 > URL: https://issues.apache.org/jira/browse/KARAF-4913 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > Upgrade to version 6.0.1-SNAPSHOT first, this is a requirement to fix > KARAF-4912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4913) Upgrade to Pax-Web 6.0.1
[ https://issues.apache.org/jira/browse/KARAF-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4913 started by Achim Nierbeck. - > Upgrade to Pax-Web 6.0.1 > - > > Key: KARAF-4913 > URL: https://issues.apache.org/jira/browse/KARAF-4913 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > Upgrade to version 6.0.1-SNAPSHOT first, this is a requirement to fix > KARAF-4912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791350#comment-15791350
]
Achim Nierbeck commented on KARAF-4912:
---
will do so for 6.0.1
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791028#comment-15791028
]
Achim Nierbeck edited comment on KARAF-4912 at 1/1/17 1:00 PM:
---
I opened https://ops4j1.jira.com/browse/PAXWEB-1047 to track this.
This upgrade does have some rather not so nice implications.
ASM is an alpha version.
Pax-Web requires xbeans in a newer version (XBEAN-296) also, but those are also
only SNAPSHOT versions.
In the end if we want to be JDK9 compliant it requires quite some
synchronization between different projects.
was (Author: achim_nierbeck):
I opened https://ops4j1.jira.com/browse/PAXWEB-1047 to track this.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4913) Upgrade to Pax-Web 6.0.1
Achim Nierbeck created KARAF-4913: - Summary: Upgrade to Pax-Web 6.0.1 Key: KARAF-4913 URL: https://issues.apache.org/jira/browse/KARAF-4913 Project: Karaf Issue Type: Dependency upgrade Components: karaf-webcontainer Affects Versions: 4.1.0 Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: 4.1.0 Upgrade to version 6.0.1-SNAPSHOT first, this is a requirement to fix KARAF-4912 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15791028#comment-15791028
]
Achim Nierbeck commented on KARAF-4912:
---
I opened https://ops4j1.jira.com/browse/PAXWEB-1047 to track this.
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck updated KARAF-4912:
--
Component/s: karaf-webcontainer
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (KARAF-4912) Cannot register Servlet via http-whiteboard under Java 9
[
https://issues.apache.org/jira/browse/KARAF-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck reassigned KARAF-4912:
-
Assignee: Achim Nierbeck
> Cannot register Servlet via http-whiteboard under Java 9
>
>
> Key: KARAF-4912
> URL: https://issues.apache.org/jira/browse/KARAF-4912
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-webcontainer
>Affects Versions: 4.1.0
> Environment: Linux (Ubuntu 12.4)
> Java 9 (JDK and JRE 9 - ea+149)
>Reporter: Lijun Liao
>Assignee: Achim Nierbeck
> Fix For: 4.1.0
>
> Attachments: ServletTest-0.0.1.jar, ServletTest-src.zip, karaf.log
>
>
> Under JDK / JRE 9 (tested with ea+149), it is impossibile to register the
> servlet via http-whiteboard.
> Steps to reproduce the problem:
> 1. Delete the folder data
> 2. Start karaf {code}bin/karaf{code}
> 3. Install feature http-whiteboard {code}feature:install http-whiteboard{code}
> 3. Copy the attached ServletTest.jar to $KARAF_HOME/deploy. The blueprint
> configuration tells karaf to register a servlet under the alias "/hw".
> 4. Open the browser and go to http://localhost:8181/hw, you will get an error.
> And ERROR message as follows will be logged in the data/log/karaf.log.
> {code}
> 2017-01-01T12:34:06,862 | ERROR |
> fileinstall-/.../apache-karaf-4.1.0-SNAPSHOT/deploy | WebApplication
> | 97 - org.ops4j.pax.web.pax-web-extender-whiteboard - 6.0.0 |
> Registration skipped for
> [ServletWebElement{mapping=DefaultServletMapping{httpContextId=null,urlPatterns=null,initParams={},servlet=foo.HelloWorldServlet@61a63ed6,
> alias=/hw, servletNamenull}}] due to error during registration
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4439) Prevent user authentication (shell & JMX) if he doesn't have role
[ https://issues.apache.org/jira/browse/KARAF-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773135#comment-15773135 ] Achim Nierbeck commented on KARAF-4439: --- Still I'm not sure how the roles for shell and JMX are supposed to affect any webconsole :) > Prevent user authentication (shell & JMX) if he doesn't have role > - > > Key: KARAF-4439 > URL: https://issues.apache.org/jira/browse/KARAF-4439 > Project: Karaf > Issue Type: Bug > Components: karaf-management, karaf-security, karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 4.1.0, 4.0.9 > > > Right now, if an user doesn't have any role defined, he can logon and perform > "non" critical operations (the "critical" operation). > We should define a minimum role required for login and prevent users access > if they don't have the minimum role (before the ACL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4895. --- Resolution: Won't Fix Fix Version/s: (was: 4.1.0) will be gone as soon as a newer version of Karaf 4.1.0 is available in the snapshot repo. Unfortunately right now it's missing the latest snapshot version for gogo shell > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck edited comment on KARAF-4895 at 12/18/16 10:39 AM: -- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. The issue is, the latest version available from the snapshot Repo still references 4.4.0 in it's feature file for Pax Web 4.4.0 while your own application already references 6.0.0 see [latest available feature descriptor|https://repository.apache.org/content/groups/snapshots-group/org/apache/karaf/features/standard/4.1.0-SNAPSHOT/standard-4.1.0-20161206.084410-264-features.xml] was (Author: achim_nierbeck): Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck edited comment on KARAF-4895 at 12/18/16 10:20 AM: -- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0. Seems to be some transitive dependency in that feature list. was (Author: achim_nierbeck): Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15758594#comment-15758594 ] Achim Nierbeck commented on KARAF-4895: --- Must be because Pax-Web 4.4.0 has been installed instead of 6.0.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-4895: - Assignee: Achim Nierbeck > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4895: -- Fix Version/s: 4.1.0 > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4895) Karaf http feature installs jetty 9.2 and 9.3
[ https://issues.apache.org/jira/browse/KARAF-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4895: -- Component/s: karaf-webcontainer > Karaf http feature installs jetty 9.2 and 9.3 > - > > Key: KARAF-4895 > URL: https://issues.apache.org/jira/browse/KARAF-4895 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Affects Versions: 4.1.0 >Reporter: Dariush Amiri >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > If you build a container that installs "http" as a boot feature, karaf > installs both the 9.2.x and the 9.3.x version of jetty. This is, of course, > very annoying. > I have a project that reproduces the issue here: > [https://github.com/damiri-ts/karaf-features-issue]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4888. --- Resolution: Fixed > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4888 started by Achim Nierbeck. - > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4888: -- Fix Version/s: 4.1.0 > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4888) Upgrade to Pax-Web 6.0.0
Achim Nierbeck created KARAF-4888: - Summary: Upgrade to Pax-Web 6.0.0 Key: KARAF-4888 URL: https://issues.apache.org/jira/browse/KARAF-4888 Project: Karaf Issue Type: Dependency upgrade Reporter: Achim Nierbeck Assignee: Achim Nierbeck The latest SNAPSHOT dependency should be added, and changed to the release version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4888) Upgrade to Pax-Web 6.0.0
[ https://issues.apache.org/jira/browse/KARAF-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck updated KARAF-4888: -- Component/s: karaf-webcontainer > Upgrade to Pax-Web 6.0.0 > > > Key: KARAF-4888 > URL: https://issues.apache.org/jira/browse/KARAF-4888 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-webcontainer >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: 4.1.0 > > > The latest SNAPSHOT dependency should be added, and changed to the release > version as soon as it's available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4882) keystore.jks update in karaf requires force restart
[ https://issues.apache.org/jira/browse/KARAF-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4882. --- Resolution: Won't Fix Is not an issue of Karaf itself. Pax Web doesn't monitor the key file. If you want to have an update without restart, just restart the pax-web-runtime bundle, that should take care of it. > keystore.jks update in karaf requires force restart > --- > > Key: KARAF-4882 > URL: https://issues.apache.org/jira/browse/KARAF-4882 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.5 > Environment: Cent OS 7.2, RHEL 7.2 >Reporter: Suresh Perumal >Priority: Blocker > > We are using Karaf 4.0.5, 4.0.6. > We are using self signed certificate for https support. > There are some scenarios where the certificate will get expired where we need > to regenerate the certificate again. > During this scenario, newly generated keystore.jks getting stored in Karaf. > ,KARAF_HOME/etc folder. > But looks like it is not picking up the latest keystore.jks and it requires > restart of karaf server. > To some extent we will not be able to restart the karaf server which might > not be correct approach. > I would like to know the approach to force update of certificates without > restarts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4873) keystore.jks update in karaf requires force restart
[ https://issues.apache.org/jira/browse/KARAF-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721501#comment-15721501 ] Achim Nierbeck commented on KARAF-4873: --- No Pax Web doesn't monitor the filesystem for a new file, therefore you won't get around restarting. > keystore.jks update in karaf requires force restart > --- > > Key: KARAF-4873 > URL: https://issues.apache.org/jira/browse/KARAF-4873 > Project: Karaf > Issue Type: Bug > Components: cellar-http >Affects Versions: 4.0.5 > Environment: karaf 4.0.5/4.0.6 on Linux CentOS, RHEL Platform >Reporter: Suresh Perumal >Priority: Blocker > > We are using Karaf 4.0.5, 4.0.6. > We are using self signed certificate for https support. > There are some scenarios where the certificate will get expired where we need > to regenerate the certificate again. > During this scenario, newly generated keystore.jks getting stored in Karaf. > ,KARAF_HOME/etc folder. > But looks like it is not picking up the latest keystore.jks and it requires > restart of karaf server. > To some extent we will not be able to restart the karaf server which might > not be correct approach. > I would like to know the approach to force update of certificates without > restarts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4809) SSH should not listen to all hosts
[ https://issues.apache.org/jira/browse/KARAF-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663325#comment-15663325 ] Achim Nierbeck commented on KARAF-4809: --- I see this more to be a documentation issue on how to secure your instance, per default I'd rather have SSH handled the way it is before. Therefore a -1 on this change > SSH should not listen to all hosts > -- > > Key: KARAF-4809 > URL: https://issues.apache.org/jira/browse/KARAF-4809 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.0.7 >Reporter: Lars Kiesow >Assignee: Jean-Baptiste Onofré > > The default SSH server configuration will make Karaf listen to all hosts. It > is usually good practice to instead listen to localhost only by default to > avoid possible security risks (e.g. accidentally exposing an unconfigured SSH > server). > This can be fixed by adjusting `sshHost` in `org.apache.karaf.shell.cfg` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4794) Decanter: make sure the discovery is disabled if only one address is configured
[ https://issues.apache.org/jira/browse/KARAF-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4794. --- Resolution: Fixed > Decanter: make sure the discovery is disabled if only one address is > configured > --- > > Key: KARAF-4794 > URL: https://issues.apache.org/jira/browse/KARAF-4794 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4794) Decanter: make sure the discovery is disabled if only one address is configured
Achim Nierbeck created KARAF-4794: - Summary: Decanter: make sure the discovery is disabled if only one address is configured Key: KARAF-4794 URL: https://issues.apache.org/jira/browse/KARAF-4794 Project: Karaf Issue Type: Improvement Components: decanter Affects Versions: decanter-1.2.0 Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4794) Decanter: make sure the discovery is disabled if only one address is configured
[ https://issues.apache.org/jira/browse/KARAF-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4794 started by Achim Nierbeck. - > Decanter: make sure the discovery is disabled if only one address is > configured > --- > > Key: KARAF-4794 > URL: https://issues.apache.org/jira/browse/KARAF-4794 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4791) Decanter: elasticsearch-rest appender should support multipe addresses
[ https://issues.apache.org/jira/browse/KARAF-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4791. --- Resolution: Fixed fixed with the attached commit > Decanter: elasticsearch-rest appender should support multipe addresses > -- > > Key: KARAF-4791 > URL: https://issues.apache.org/jira/browse/KARAF-4791 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > The rest appender doesn't support multiple addresses even though it is > configured to uses discovery. > Either discovery is disabled or multiple addresses are supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4791) Decanter: elasticsearch-rest appender should support multipe addresses
[ https://issues.apache.org/jira/browse/KARAF-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4791 started by Achim Nierbeck. - > Decanter: elasticsearch-rest appender should support multipe addresses > -- > > Key: KARAF-4791 > URL: https://issues.apache.org/jira/browse/KARAF-4791 > Project: Karaf > Issue Type: Improvement > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > The rest appender doesn't support multiple addresses even though it is > configured to uses discovery. > Either discovery is disabled or multiple addresses are supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4791) Decanter: elasticsearch-rest appender should support multipe addresses
Achim Nierbeck created KARAF-4791: - Summary: Decanter: elasticsearch-rest appender should support multipe addresses Key: KARAF-4791 URL: https://issues.apache.org/jira/browse/KARAF-4791 Project: Karaf Issue Type: Improvement Components: decanter Affects Versions: decanter-1.2.0 Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 The rest appender doesn't support multiple addresses even though it is configured to uses discovery. Either discovery is disabled or multiple addresses are supported. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration
[ https://issues.apache.org/jira/browse/KARAF-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4767. --- Resolution: Fixed fixed with last commit > Decanter: collectors and appenders can't be re-used without default > configuration > - > > Key: KARAF-4767 > URL: https://issues.apache.org/jira/browse/KARAF-4767 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now the jmx collector and various appenders can't be re-used without > the default configs, those features should be split into the current one > which references a *-core feature. This way it's easier to re-use the jmx > collector or the elasticsearch appender ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration
Achim Nierbeck created KARAF-4767: - Summary: Decanter: collectors and appenders can't be re-used without default configuration Key: KARAF-4767 URL: https://issues.apache.org/jira/browse/KARAF-4767 Project: Karaf Issue Type: Bug Components: decanter Affects Versions: decanter-1.2.0 Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 Right now the jmx collector and various appenders can't be re-used without the default configs, those features should be split into the current one which references a *-core feature. This way it's easier to re-use the jmx collector or the elasticsearch appender ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration
[ https://issues.apache.org/jira/browse/KARAF-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4767 started by Achim Nierbeck. - > Decanter: collectors and appenders can't be re-used without default > configuration > - > > Key: KARAF-4767 > URL: https://issues.apache.org/jira/browse/KARAF-4767 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now the jmx collector and various appenders can't be re-used without > the default configs, those features should be split into the current one > which references a *-core feature. This way it's easier to re-use the jmx > collector or the elasticsearch appender ... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4757) Decanter: elasticsearch-appender-rest shouldn't be dependent on http
[ https://issues.apache.org/jira/browse/KARAF-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4757. --- Resolution: Fixed fixed with last commit: http://git-wip-us.apache.org/repos/asf/karaf-decanter/commit/469591ba > Decanter: elasticsearch-appender-rest shouldn't be dependent on http > > > Key: KARAF-4757 > URL: https://issues.apache.org/jira/browse/KARAF-4757 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now the feature of the elasticsearch rest appender requires http, for > no reason. The Import-Packages does have javax.servlet as import but non are > required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4757) Decanter: elasticsearch-appender-rest shouldn't be dependent on http
Achim Nierbeck created KARAF-4757: - Summary: Decanter: elasticsearch-appender-rest shouldn't be dependent on http Key: KARAF-4757 URL: https://issues.apache.org/jira/browse/KARAF-4757 Project: Karaf Issue Type: Bug Components: decanter Affects Versions: decanter-1.2.0 Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 Right now the feature of the elasticsearch rest appender requires http, for no reason. The Import-Packages does have javax.servlet as import but non are required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4757) Decanter: elasticsearch-appender-rest shouldn't be dependent on http
[ https://issues.apache.org/jira/browse/KARAF-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4757 started by Achim Nierbeck. - > Decanter: elasticsearch-appender-rest shouldn't be dependent on http > > > Key: KARAF-4757 > URL: https://issues.apache.org/jira/browse/KARAF-4757 > Project: Karaf > Issue Type: Bug > Components: decanter >Affects Versions: decanter-1.2.0 >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now the feature of the elasticsearch rest appender requires http, for > no reason. The Import-Packages does have javax.servlet as import but non are > required. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4742. --- Resolution: Fixed > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reopened KARAF-4742: --- versions shouldn't be 1.2.1 ... > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4742) Decanter: Add Java Process JMX Collector
[ https://issues.apache.org/jira/browse/KARAF-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck resolved KARAF-4742. --- Resolution: Fixed fixed by: http://git-wip-us.apache.org/repos/asf/karaf-decanter/commit/f1fa5cb6 > Decanter: Add Java Process JMX Collector > > > Key: KARAF-4742 > URL: https://issues.apache.org/jira/browse/KARAF-4742 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.3.0 > > > Right now there is a JMX collector available. Which is ok for open JMX > connections. Sometimes there are Java applications running which don't > explicitly have a JMX connection open, but are monitor able by JConsole. For > this a special JVM Process Collector is needed, which hooks itself into the > JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4742) Decanter: Add Java Process JMX Collector
Achim Nierbeck created KARAF-4742: - Summary: Decanter: Add Java Process JMX Collector Key: KARAF-4742 URL: https://issues.apache.org/jira/browse/KARAF-4742 Project: Karaf Issue Type: New Feature Components: decanter Reporter: Achim Nierbeck Assignee: Achim Nierbeck Fix For: decanter-1.3.0 Right now there is a JMX collector available. Which is ok for open JMX connections. Sometimes there are Java applications running which don't explicitly have a JMX connection open, but are monitor able by JConsole. For this a special JVM Process Collector is needed, which hooks itself into the JVM Processes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4714) shell (so also ssh) not working anymore on ARM
[
https://issues.apache.org/jira/browse/KARAF-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15520312#comment-15520312
]
Achim Nierbeck commented on KARAF-4714:
---
we love contribution :-)
it has been addressed on the ml
https://lists.apache.org/thread.html/d19fda54132fbe9f16ee1caf621122c8e3a8feea1d2bc501d725a9ff@%3Cdev.karaf.apache.org%3E
> shell (so also ssh) not working anymore on ARM
> --
>
> Key: KARAF-4714
> URL: https://issues.apache.org/jira/browse/KARAF-4714
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.0.6
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.8
>
> Attachments: karaf.log.k405.txt, karaf.log.k406.txt
>
>
> The official Karaf 4.0.6 distribution (the archive
> "apache-karaf-4.0.6.tar.gz" from your homepage) does not work correctly on
> ARM systems.
> I unpacked and started the official distribution (bin/karaf).
> The log file shows this content:
> {noformat}
> 2016-09-14 19:25:16,104 | ERROR | pool-7-thread-1 |
> BootFeaturesInstaller| 8 - org.apache.karaf.features.core
> - 4.0.6 | Error installing boot features
> org.apache.karaf.features.internal.util.MultiException: Error restarting
> bundles
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:854)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
> Caused by: org.osgi.framework.BundleException: Activator start error
> in bundle org.apache.karaf.shell.core [43].
> at
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1286)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:846)[8:org.apache.karaf.features.core:4.0.6]
> ... 6 more
> Caused by: java.lang.UnsatisfiedLinkError: Could not load library.
> Reasons: [no jansi in java.library.path,
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> cannot open shared object file: No such file or directory (Possible
> cause: can't load IA 32-bit .so on a ARM-bit platform)]
> at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
> at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
> at org.fusesource.jansi.internal.CLibrary.(CLibrary.java:42)
> at org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
> at org.fusesource.jansi.AnsiConsole.(AnsiConsole.java:38)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.wrap(StreamWrapUtil.java:62)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.reWrap(StreamWrapUtil.java:89)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:81)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:76)
> at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_65]
> at org.apache.karaf.util.jaas.JaasHelper.doAs(JaasHelper.java:93)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:76)
> at
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:112)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4714) shell (so also ssh) not working anymore on ARM
[
https://issues.apache.org/jira/browse/KARAF-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15520290#comment-15520290
]
Achim Nierbeck commented on KARAF-4714:
---
It should be tackled with 4.0.8, as 4.0.7 is on vote already
> shell (so also ssh) not working anymore on ARM
> --
>
> Key: KARAF-4714
> URL: https://issues.apache.org/jira/browse/KARAF-4714
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.0.6
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.8
>
> Attachments: karaf.log.k405.txt, karaf.log.k406.txt
>
>
> The official Karaf 4.0.6 distribution (the archive
> "apache-karaf-4.0.6.tar.gz" from your homepage) does not work correctly on
> ARM systems.
> I unpacked and started the official distribution (bin/karaf).
> The log file shows this content:
> {noformat}
> 2016-09-14 19:25:16,104 | ERROR | pool-7-thread-1 |
> BootFeaturesInstaller| 8 - org.apache.karaf.features.core
> - 4.0.6 | Error installing boot features
> org.apache.karaf.features.internal.util.MultiException: Error restarting
> bundles
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:854)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
> Caused by: org.osgi.framework.BundleException: Activator start error
> in bundle org.apache.karaf.shell.core [43].
> at
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1286)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:846)[8:org.apache.karaf.features.core:4.0.6]
> ... 6 more
> Caused by: java.lang.UnsatisfiedLinkError: Could not load library.
> Reasons: [no jansi in java.library.path,
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> cannot open shared object file: No such file or directory (Possible
> cause: can't load IA 32-bit .so on a ARM-bit platform)]
> at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
> at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
> at org.fusesource.jansi.internal.CLibrary.(CLibrary.java:42)
> at org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
> at org.fusesource.jansi.AnsiConsole.(AnsiConsole.java:38)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.wrap(StreamWrapUtil.java:62)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.reWrap(StreamWrapUtil.java:89)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:81)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:76)
> at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_65]
> at org.apache.karaf.util.jaas.JaasHelper.doAs(JaasHelper.java:93)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:76)
> at
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:112)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4714) shell (so also ssh) not working anymore on ARM
[
https://issues.apache.org/jira/browse/KARAF-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Achim Nierbeck updated KARAF-4714:
--
Fix Version/s: 4.0.8
> shell (so also ssh) not working anymore on ARM
> --
>
> Key: KARAF-4714
> URL: https://issues.apache.org/jira/browse/KARAF-4714
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.0.6
>Reporter: Markus Rathgeb
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.8
>
> Attachments: karaf.log.k405.txt, karaf.log.k406.txt
>
>
> The official Karaf 4.0.6 distribution (the archive
> "apache-karaf-4.0.6.tar.gz" from your homepage) does not work correctly on
> ARM systems.
> I unpacked and started the official distribution (bin/karaf).
> The log file shows this content:
> {noformat}
> 2016-09-14 19:25:16,104 | ERROR | pool-7-thread-1 |
> BootFeaturesInstaller| 8 - org.apache.karaf.features.core
> - 4.0.6 | Error installing boot features
> org.apache.karaf.features.internal.util.MultiException: Error restarting
> bundles
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:854)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1176)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1074)[8:org.apache.karaf.features.core:4.0.6]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_65]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_65]
> Caused by: org.osgi.framework.BundleException: Activator start error
> in bundle org.apache.karaf.shell.core [43].
> at
> org.apache.felix.framework.Felix.activateBundle(Felix.java:2276)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.Felix.startBundle(Felix.java:2144)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1286)[8:org.apache.karaf.features.core:4.0.6]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:846)[8:org.apache.karaf.features.core:4.0.6]
> ... 6 more
> Caused by: java.lang.UnsatisfiedLinkError: Could not load library.
> Reasons: [no jansi in java.library.path,
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> /home/alarm/apache-karaf-4.0.6/data/tmp/libjansi-32-1562974624645500249.so:
> cannot open shared object file: No such file or directory (Possible
> cause: can't load IA 32-bit .so on a ARM-bit platform)]
> at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
> at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
> at org.fusesource.jansi.internal.CLibrary.(CLibrary.java:42)
> at org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
> at org.fusesource.jansi.AnsiConsole.(AnsiConsole.java:38)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.wrap(StreamWrapUtil.java:62)
> at
> org.apache.karaf.shell.impl.console.osgi.StreamWrapUtil.reWrap(StreamWrapUtil.java:89)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:81)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager$2.run(LocalConsoleManager.java:76)
> at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_65]
> at org.apache.karaf.util.jaas.JaasHelper.doAs(JaasHelper.java:93)
> at
> org.apache.karaf.shell.impl.console.osgi.LocalConsoleManager.start(LocalConsoleManager.java:76)
> at
> org.apache.karaf.shell.impl.console.osgi.Activator.start(Activator.java:112)
> at
> org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)
> at org.apache.felix.framework.Felix.activateBundle(Felix.java:2226)
> ... 11 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4696) Upgrade to Pax-Web 4.3.0
Achim Nierbeck created KARAF-4696: - Summary: Upgrade to Pax-Web 4.3.0 Key: KARAF-4696 URL: https://issues.apache.org/jira/browse/KARAF-4696 Project: Karaf Issue Type: Bug Components: karaf-webcontainer Reporter: Achim Nierbeck Fix For: 4.0.7 API Changes in Pax-Web require a Minor version bump to 4.3.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard
[ https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457897#comment-15457897 ] Achim Nierbeck commented on KARAF-4685: --- Well the proposed flags are only available from that feature on ... (or better understood with that version) BUT ... we have a similar thing already available with the current version of Pax-Web :-) > Support session replication through OSGi 6 http whiteboard > -- > > Key: KARAF-4685 > URL: https://issues.apache.org/jira/browse/KARAF-4685 > Project: Karaf > Issue Type: Improvement > Components: cellar-http >Reporter: Roland Hauser >Assignee: Jean-Baptiste Onofré > > Currently, session replication can only be done through specifying the > Hazelcast filter/listener in the web.xml file of a web-application. This can > be a serious disadvantage if you also want to install a web-application to > another web-container which does not need clustering, and, consequently, does > not contain the Hazelcast libs. In this case, the application won't start. > I suggest an additional way how session replication could be realized without > the need of modifying the web-app: it could be done through a Cellar > component which implements a http whiteboard. I would realize this as follows: > - Register a Filter/Session listener to the OSGi service registry. Per > default, every web-application installed is considered for session > replication. > - It should be possible to configure Hazelcast filter properties either > through a config file inside the OSGI-INF folder of the web-app, or, through > the ConfigAdmin service. > - If the sessions of a specific web-application should not be replicated, > then this could be flagged either through a config file inside the OSGI-INF > folder of the web-app, or, through the ConfigAdmin service. > - The new Cellar component should be installable as additional feature > "http-failover" > What's your opinion? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KARAF-4685) Support session replication through OSGi 6 http whiteboard
[ https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457864#comment-15457864 ] Achim Nierbeck edited comment on KARAF-4685 at 9/2/16 8:01 AM: --- This will require Pax-Web 6.0 as it's the version handling OSGi R6 Http-Whiteboard service. So this will only be possible on a Karaf 4.1 not lower. was (Author: achim_nierbeck): This will require Pax-Web 6.0 as it's the version handling OSGi R6 Http-Whiteboard service. > Support session replication through OSGi 6 http whiteboard > -- > > Key: KARAF-4685 > URL: https://issues.apache.org/jira/browse/KARAF-4685 > Project: Karaf > Issue Type: Improvement > Components: cellar-http >Reporter: Roland Hauser >Assignee: Jean-Baptiste Onofré > > Currently, session replication can only be done through specifying the > Hazelcast filter/listener in the web.xml file of a web-application. This can > be a serious disadvantage if you also want to install a web-application to > another web-container which does not need clustering, and, consequently, does > not contain the Hazelcast libs. In this case, the application won't start. > I suggest an additional way how session replication could be realized without > the need of modifying the web-app: it could be done through a Cellar > component which implements a http whiteboard. I would realize this as follows: > - Register a Filter/Session listener to the OSGi service registry. Per > default, every web-application installed is considered for session > replication. > - It should be possible to configure Hazelcast filter properties either > through a config file inside the OSGI-INF folder of the web-app, or, through > the ConfigAdmin service. > - If the sessions of a specific web-application should not be replicated, > then this could be flagged either through a config file inside the OSGI-INF > folder of the web-app, or, through the ConfigAdmin service. > - The new Cellar component should be installable as additional feature > "http-failover" > What's your opinion? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4685) Support session replication through OSGi 6 http whiteboard
[ https://issues.apache.org/jira/browse/KARAF-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457864#comment-15457864 ] Achim Nierbeck commented on KARAF-4685: --- This will require Pax-Web 6.0 as it's the version handling OSGi R6 Http-Whiteboard service. > Support session replication through OSGi 6 http whiteboard > -- > > Key: KARAF-4685 > URL: https://issues.apache.org/jira/browse/KARAF-4685 > Project: Karaf > Issue Type: Improvement > Components: cellar-http >Reporter: Roland Hauser >Assignee: Jean-Baptiste Onofré > > Currently, session replication can only be done through specifying the > Hazelcast filter/listener in the web.xml file of a web-application. This can > be a serious disadvantage if you also want to install a web-application to > another web-container which does not need clustering, and, consequently, does > not contain the Hazelcast libs. In this case, the application won't start. > I suggest an additional way how session replication could be realized without > the need of modifying the web-app: it could be done through a Cellar > component which implements a http whiteboard. I would realize this as follows: > - Register a Filter/Session listener to the OSGi service registry. Per > default, every web-application installed is considered for session > replication. > - It should be possible to configure Hazelcast filter properties either > through a config file inside the OSGI-INF folder of the web-app, or, through > the ConfigAdmin service. > - If the sessions of a specific web-application should not be replicated, > then this could be flagged either through a config file inside the OSGI-INF > folder of the web-app, or, through the ConfigAdmin service. > - The new Cellar component should be installable as additional feature > "http-failover" > What's your opinion? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4501) Documentation still refers to deprecated org.apache.karaf.tooling.exam.container
Achim Nierbeck created KARAF-4501:
-
Summary: Documentation still refers to deprecated
org.apache.karaf.tooling.exam.container
Key: KARAF-4501
URL: https://issues.apache.org/jira/browse/KARAF-4501
Project: Karaf
Issue Type: Bug
Components: karaf-documentation
Affects Versions: 4.0.4
Reporter: Achim Nierbeck
The
[documentation|https://karaf.apache.org/manual/latest/developers-guide/writing-tests.html]
still refers to the old karaf internal container testing framework. This
should be replaced by:
{code}
org.ops4j.pax.exam
pax-exam-junit4
test
org.ops4j.pax.exam
pax-exam-container-karaf
test
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4470) Upgrade to Pax Web 4.2.5
[ https://issues.apache.org/jira/browse/KARAF-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15224307#comment-15224307 ] Achim Nierbeck commented on KARAF-4470: --- afaik 4.1 already sits on top of Pax-Web 6.0.0-SNAPSHOT ... > Upgrade to Pax Web 4.2.5 > > > Key: KARAF-4470 > URL: https://issues.apache.org/jira/browse/KARAF-4470 > Project: Karaf > Issue Type: Bug > Components: karaf-webcontainer >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-3698) Add decanter cassandra appender
[ https://issues.apache.org/jira/browse/KARAF-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Achim Nierbeck reassigned KARAF-3698: - Assignee: Achim Nierbeck (was: Jean-Baptiste Onofré) > Add decanter cassandra appender > --- > > Key: KARAF-3698 > URL: https://issues.apache.org/jira/browse/KARAF-3698 > Project: Karaf > Issue Type: New Feature > Components: decanter >Reporter: Achim Nierbeck >Assignee: Achim Nierbeck > Fix For: decanter-1.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
