[jira] [Commented] (KARAF-4915) Login Event Spam
[
https://issues.apache.org/jira/browse/KARAF-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799366#comment-15799366
]
Jean-Baptiste Onofré commented on KARAF-4915:
-
It's normal: it's when any connection (SSH, webconsole, ...) occurs. Don't you
have Decanter for instance ?
> Login Event Spam
>
>
> Key: KARAF-4915
> URL: https://issues.apache.org/jira/browse/KARAF-4915
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.0.8
>Reporter: Stefan Simroth
> Attachments: Selection_209.png, Selection_210.png,
> karaf-login-event-spam.txt
>
>
> I noticed a lot of login events which I consider too much ("spam"), when I
> installed the webconsole. Before I did not notice them (which doesn't mean
> they were not there).
> Steps to reproduce:
> * install webconsole
> * login at http://localhost:8181/system/console/events with default
> credentials karaf:karaf
> * switch to events view
> *Bug:* There a lots of login events (>50 or 100...), alternating "login
> attempt" and "login success" which spam the whole view, making it very hard
> to see other events
> I would expect 1 login attempt and 1 login success event - not so many
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799339#comment-15799339 ] ASF subversion and git services commented on KARAF-4897: Commit 8ea352180978d69efd29d9daa90f474d52be41a8 in karaf's branch refs/heads/karaf-4.0.x from [~skitt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8ea3521 ] [KARAF-4897] Add an option to simplify bundle dependencies > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4897. - Resolution: Fixed > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4897: Fix Version/s: (was: 4.2.0) > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799274#comment-15799274 ] ASF subversion and git services commented on KARAF-4897: Commit 6023b5cb2581c4c8d31c52a62f846a5ad16fdc22 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=6023b5c ] [KARAF-4897] This closes #274 > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.2.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799273#comment-15799273 ] ASF subversion and git services commented on KARAF-4897: Commit f6127d9eca3bcd06275f290899080b0effb9c58a in karaf's branch refs/heads/master from [~skitt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f6127d9 ] [KARAF-4897] Add an option to simplify bundle dependencies > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.2.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4897) Add an option to simplify bundle dependencies
[ https://issues.apache.org/jira/browse/KARAF-4897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15799276#comment-15799276 ] ASF GitHub Bot commented on KARAF-4897: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/274 > Add an option to simplify bundle dependencies > - > > Key: KARAF-4897 > URL: https://issues.apache.org/jira/browse/KARAF-4897 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Affects Versions: 4.0.8 >Reporter: Stephen Kitt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.2.0, 4.0.9 > > > When using GenerateDescriptorMojo to generate feature XML descriptions, it > would be nice to have an option to simplify dependencies where possible. By > that I mean if feature a depends on feature b and bundle c, and feature b > also includes bundle c, then feature a could be simplified to only depend on > feature b. (Making this an option allows users to decide what to do — do they > want explicit dependencies, or does it make sense for them to ride on the > coat-tails of parent features?) -- 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] [Commented] (KARAF-4918) Upgrade to Felix FileInstall 3.5.8
[ https://issues.apache.org/jira/browse/KARAF-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15797963#comment-15797963 ] ASF subversion and git services commented on KARAF-4918: Commit 0d10c7f074a8056c783be2403ababbe74f5dbb32 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0d10c7f ] [KARAF-4918] Upgrade to Felix FileInstall 3.5.8 > Upgrade to Felix FileInstall 3.5.8 > -- > > Key: KARAF-4918 > URL: https://issues.apache.org/jira/browse/KARAF-4918 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4920) Upgrade to Aries Transaction Manager 1.3.2
[ https://issues.apache.org/jira/browse/KARAF-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15797965#comment-15797965 ] ASF subversion and git services commented on KARAF-4920: Commit 68c75f44ea7ac47f14374381f8e170177a6b9669 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=68c75f4 ] [KARAF-4920] Upgrade to Aries Transaction Manager 1.3.2 > Upgrade to Aries Transaction Manager 1.3.2 > -- > > Key: KARAF-4920 > URL: https://issues.apache.org/jira/browse/KARAF-4920 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4920) Upgrade to Aries Transaction Manager 1.3.2
[ https://issues.apache.org/jira/browse/KARAF-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4920. Resolution: Fixed > Upgrade to Aries Transaction Manager 1.3.2 > -- > > Key: KARAF-4920 > URL: https://issues.apache.org/jira/browse/KARAF-4920 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4919) Upgrade to Aries Proxy 1.0.6
[ https://issues.apache.org/jira/browse/KARAF-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15797964#comment-15797964 ] ASF subversion and git services commented on KARAF-4919: Commit 388fc1f88e878fc1e7eadf95e63877664710a044 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=388fc1f ] [KARAF-4919] Upgrade to Aries Proxy 1.0.6 > Upgrade to Aries Proxy 1.0.6 > > > Key: KARAF-4919 > URL: https://issues.apache.org/jira/browse/KARAF-4919 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4918) Upgrade to Felix FileInstall 3.5.8
[ https://issues.apache.org/jira/browse/KARAF-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4918. Resolution: Fixed > Upgrade to Felix FileInstall 3.5.8 > -- > > Key: KARAF-4918 > URL: https://issues.apache.org/jira/browse/KARAF-4918 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4919) Upgrade to Aries Proxy 1.0.6
[ https://issues.apache.org/jira/browse/KARAF-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4919. Resolution: Fixed > Upgrade to Aries Proxy 1.0.6 > > > Key: KARAF-4919 > URL: https://issues.apache.org/jira/browse/KARAF-4919 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4920) Upgrade to Aries Transaction Manager 1.3.2
Guillaume Nodet created KARAF-4920: -- Summary: Upgrade to Aries Transaction Manager 1.3.2 Key: KARAF-4920 URL: https://issues.apache.org/jira/browse/KARAF-4920 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4919) Upgrade to Aries Proxy 1.0.6
Guillaume Nodet created KARAF-4919: -- Summary: Upgrade to Aries Proxy 1.0.6 Key: KARAF-4919 URL: https://issues.apache.org/jira/browse/KARAF-4919 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4918) Upgrade to Felix FileInstall 3.5.8
Guillaume Nodet created KARAF-4918: -- Summary: Upgrade to Felix FileInstall 3.5.8 Key: KARAF-4918 URL: https://issues.apache.org/jira/browse/KARAF-4918 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4917) Support dynamicaliy registered configurations in RBAC
[
https://issues.apache.org/jira/browse/KARAF-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15797704#comment-15797704
]
ASF GitHub Bot commented on KARAF-4917:
---
Github user zregvart closed the pull request at:
https://github.com/apache/karaf/pull/275
> Support dynamicaliy registered configurations in RBAC
> -
>
> Key: KARAF-4917
> URL: https://issues.apache.org/jira/browse/KARAF-4917
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-security
>Affects Versions: 4.1.0
>Reporter: Zoran Regvart
>Assignee: Freeman Fang
>Priority: Minor
>
> When adding configuration at runtime through
> {{ConfigurationAdmin#createFactoryConfiguration}} Apache Felix appends
> [random|https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java#L397-L400]
>
> [UUID|https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java#L1093-L1137]
> to the Configuration PID.
> In order for those to be considered by {{getRequiredRoles}} that random UUID
> needs to be removed in comparison performed by {{getGeneralPid}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KARAF-4917) Support dynamicaliy registered configurations in RBAC
[
https://issues.apache.org/jira/browse/KARAF-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoran Regvart closed KARAF-4917.
Resolution: Won't Fix
As discussed above there is no need for this.
> Support dynamicaliy registered configurations in RBAC
> -
>
> Key: KARAF-4917
> URL: https://issues.apache.org/jira/browse/KARAF-4917
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-security
>Affects Versions: 4.1.0
>Reporter: Zoran Regvart
>Assignee: Freeman Fang
>Priority: Minor
>
> When adding configuration at runtime through
> {{ConfigurationAdmin#createFactoryConfiguration}} Apache Felix appends
> [random|https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java#L397-L400]
>
> [UUID|https://github.com/apache/felix/blob/trunk/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java#L1093-L1137]
> to the Configuration PID.
> In order for those to be considered by {{getRequiredRoles}} that random UUID
> needs to be removed in comparison performed by {{getGeneralPid}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
