[jira] [Resolved] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved KARAF-4600.
-
Resolution: Fixed
Fix Version/s: 2.4.5
3.0.8
4.0.6
4.1.0
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
> Fix For: 4.1.0, 4.0.6, 3.0.8, 2.4.5
>
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356368#comment-15356368
]
Freeman Fang commented on KARAF-4600:
-
patch applied on behalf of Tadayoshi Sato with thanks!
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356366#comment-15356366
]
ASF subversion and git services commented on KARAF-4600:
Commit affb5308bffa904518fab8a567d906cd89a83200 in karaf's branch
refs/heads/karaf-2.x from [~tadayosi]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=affb530 ]
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties in
object name differs
(cherry picked from commit ce1b778138d4eee7992b25386aa19c6a7edaf384)
(cherry picked from commit 1fe22425f9e0d3e0e6e2b40ebb02b9cfcbdbcae1)
(cherry picked from commit 5bf2185c2397753417072a5bdcf0b4c6a1ef6d13)
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356365#comment-15356365
]
ASF subversion and git services commented on KARAF-4600:
Commit 5bf2185c2397753417072a5bdcf0b4c6a1ef6d13 in karaf's branch
refs/heads/karaf-3.0.x from [~tadayosi]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5bf2185 ]
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties in
object name differs
(cherry picked from commit ce1b778138d4eee7992b25386aa19c6a7edaf384)
(cherry picked from commit 1fe22425f9e0d3e0e6e2b40ebb02b9cfcbdbcae1)
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356355#comment-15356355
]
ASF subversion and git services commented on KARAF-4600:
Commit 1fe22425f9e0d3e0e6e2b40ebb02b9cfcbdbcae1 in karaf's branch
refs/heads/karaf-4.0.x from [~tadayosi]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=1fe2242 ]
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties in
object name differs
(cherry picked from commit ce1b778138d4eee7992b25386aa19c6a7edaf384)
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356353#comment-15356353
]
ASF GitHub Bot commented on KARAF-4600:
---
Github user asfgit closed the pull request at:
https://github.com/apache/karaf/pull/205
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356352#comment-15356352
]
ASF subversion and git services commented on KARAF-4600:
Commit ce1b778138d4eee7992b25386aa19c6a7edaf384 in karaf's branch
refs/heads/master from [~tadayosi]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=ce1b778 ]
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties in
object name differs
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-4600 started by Freeman Fang.
---
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned KARAF-4600:
---
Assignee: Freeman Fang
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>Assignee: Freeman Fang
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
[
https://issues.apache.org/jira/browse/KARAF-4600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356338#comment-15356338
]
ASF GitHub Bot commented on KARAF-4600:
---
GitHub user tadayosi opened a pull request:
https://github.com/apache/karaf/pull/205
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties
in object name differs
https://issues.apache.org/jira/browse/KARAF-4600
This fix makes `KarafMBeanServerGuard` always use the canonical object name
when resolving ACL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tadayosi/karaf KARAF-4600
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/karaf/pull/205.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #205
commit ce1b778138d4eee7992b25386aa19c6a7edaf384
Author: Tadayoshi Sato
Date: 2016-06-30T02:22:17Z
[KARAF-4600] RBAC - MBean fails to resolve ACL if the order of properties
in object name differs
> RBAC - MBean fails to resolve ACL if the order of properties in object name
> differs
> ---
>
> Key: KARAF-4600
> URL: https://issues.apache.org/jira/browse/KARAF-4600
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Affects Versions: 4.0.5
>Reporter: Tadayoshi Sato
>
> An MBean:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> has an ACL file with the following configuration:
> {{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
> {code}
> browse* = viewer
> {code}
> While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
> viewer role on this object name:
> {code}
> org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
> {code}
> and operation {{"browse"}}, it returns {{false}} on the canonical form of the
> same object name and operation, i.e.:
> {code}
> org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
> {code}
> and RBAC doesn't work correctly.
> The root cause is that the resolution of ACL configuration is affected by the
> order of properties in an object name. In the original form of the object
> name, ACL resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.Queue.TEST
> {code}
> whereas in the canonical form it resolves as:
> {code}
> org.apache.activemq.Broker.amq-broker.TEST.Queue
> {code}
> and thus cannot find the correct ACL file (note the {{"type"}} property
> precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-4600) RBAC - MBean fails to resolve ACL if the order of properties in object name differs
Tadayoshi Sato created KARAF-4600:
-
Summary: RBAC - MBean fails to resolve ACL if the order of
properties in object name differs
Key: KARAF-4600
URL: https://issues.apache.org/jira/browse/KARAF-4600
Project: Karaf
Issue Type: Bug
Components: karaf-security
Affects Versions: 4.0.5
Reporter: Tadayoshi Sato
An MBean:
{code}
org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
{code}
has an ACL file with the following configuration:
{{etc/jmx.acl.org.apache.activemq.Broker._.Queue.cfg}}
{code}
browse* = viewer
{code}
While {{JMXSecurityMBean#canInvoke(String, String)}} returns {{true}} for the
viewer role on this object name:
{code}
org.apache.activemq:type=Broker,brokerName=amq-broker,destinationType=Queue,destinationName=TEST
{code}
and operation {{"browse"}}, it returns {{false}} on the canonical form of the
same object name and operation, i.e.:
{code}
org.apache.activemq:brokerName=amq-broker,destinationName=TEST,destinationType=Queue,type=Broker
{code}
and RBAC doesn't work correctly.
The root cause is that the resolution of ACL configuration is affected by the
order of properties in an object name. In the original form of the object name,
ACL resolves as:
{code}
org.apache.activemq.Broker.amq-broker.Queue.TEST
{code}
whereas in the canonical form it resolves as:
{code}
org.apache.activemq.Broker.amq-broker.TEST.Queue
{code}
and thus cannot find the correct ACL file (note the {{"type"}} property
precedes others due to KARAF-3020).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
[
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356187#comment-15356187
]
Michael Vorburger commented on KARAF-4599:
--
[~jbonofre] I'm NOT a UNIX Shell script crack, BUT I've just played around with
this, and added this at the top of the startup script to understand, after that
new first block ending in PROGNAME=`basename "$REALNAME"` :
{noformat}echo "€0 = " $0
echo "REALNAME = " $REALNAME
echo "DIRNAME = " $DIRNAME
echo "PROGNAME = " $PROGNAME{noformat}
AND as far as I can see, what was done in KARAF-4564 is simply completely
broken, no? I never see any values set for DIRNAME and PROGNAME, and it seems
to just work by chance.
However, if you REMOVE "> /dev/null 2>&1" from that readlink, so that the first
line reads:
{noformat}REALNAME=`readlink -e "$0"`{noformat}
THEN it all works great for me. Given that readlink is a command which prints
to STDOUT, isn't that redirect just plain wrong then? Or am I totally not
getting something here?
PS: Will someone else with a better understand about Karaf's release management
and knowledge about whether KARAF-4564 went into master and/or 4.0.x do the
necessary Affects Version & Fix Version and later cherry-pick correctly etc.
> KARAF-4564 impact: karaf startup command now only works when invoked from
> current directoy, no longer via absolute path
> ---
>
> Key: KARAF-4599
> URL: https://issues.apache.org/jira/browse/KARAF-4599
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.7, 3.0.8
>Reporter: Michael Vorburger
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 3.0.8
>
>
> KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
> this introduced a new regression: Following that change, the ./karaf startup
> command now only works when invoked from current directoy, no longer via
> absolute path. For example:
> {noformat}git clone git://git.apache.org/karaf.git
> cd karaf
> git checkout karaf-3.0.x
> cd tooling/karaf-maven-plugin
> mvn clean install
> cd ../..
> mvn clean install -DskipTests
> cd assemblies/apache-karaf/target/assembly/bin/
> chmod +x karaf
> ./karaf
> cd ../../../../..
> ./assemblies/apache-karaf/target/assembly/bin/karaf
> Error: Could not find or load main class org.apache.karaf.main.Main
> {noformat}
> Of course we could further fiddle with the startup script to solve this
> somehow, but it occurred to me that perhaps somewhere on Apache there is a
> ready made script for this already? Like maybe looking at e.g. how the Maven
> / Ant & other such tools (Gradle?) would be valuable.
> Perhaps some sort of non-regression integration test for both start-up
> scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4510) Initial instance.properties file root location uses karaf.home instead of karaf.base
[ https://issues.apache.org/jira/browse/KARAF-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4510. - Resolution: Fixed > Initial instance.properties file root location uses karaf.home instead of > karaf.base > > > Key: KARAF-4510 > URL: https://issues.apache.org/jira/browse/KARAF-4510 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-instance >Affects Versions: 4.0.4, 4.0.5 >Reporter: Frédérik ROULEAU >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > Attachments: Fix_KARAF_4510.patch > > > When we start a karaf root instance for the first time, the > instance.properties file created contains for instance root location the > karaf's home directory instead of karaf's base directory. > That lead instance:list to show root with the error status ! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4510) Initial instance.properties file root location uses karaf.home instead of karaf.base
[ https://issues.apache.org/jira/browse/KARAF-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355869#comment-15355869 ] ASF GitHub Bot commented on KARAF-4510: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/183 > Initial instance.properties file root location uses karaf.home instead of > karaf.base > > > Key: KARAF-4510 > URL: https://issues.apache.org/jira/browse/KARAF-4510 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-instance >Affects Versions: 4.0.4, 4.0.5 >Reporter: Frédérik ROULEAU >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > Attachments: Fix_KARAF_4510.patch > > > When we start a karaf root instance for the first time, the > instance.properties file created contains for instance root location the > karaf's home directory instead of karaf's base directory. > That lead instance:list to show root with the error status ! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4510) Initial instance.properties file root location uses karaf.home instead of karaf.base
[ https://issues.apache.org/jira/browse/KARAF-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355870#comment-15355870 ] ASF subversion and git services commented on KARAF-4510: Commit d082f8239c4856707e9c8546ff9f06af8df419a7 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d082f82 ] [KARAF-4510] This closes #183 > Initial instance.properties file root location uses karaf.home instead of > karaf.base > > > Key: KARAF-4510 > URL: https://issues.apache.org/jira/browse/KARAF-4510 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-instance >Affects Versions: 4.0.4, 4.0.5 >Reporter: Frédérik ROULEAU >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > Attachments: Fix_KARAF_4510.patch > > > When we start a karaf root instance for the first time, the > instance.properties file created contains for instance root location the > karaf's home directory instead of karaf's base directory. > That lead instance:list to show root with the error status ! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
[
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned KARAF-4599:
---
Assignee: Jean-Baptiste Onofré
> KARAF-4564 impact: karaf startup command now only works when invoked from
> current directoy, no longer via absolute path
> ---
>
> Key: KARAF-4599
> URL: https://issues.apache.org/jira/browse/KARAF-4599
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.7, 3.0.8
>Reporter: Michael Vorburger
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 3.0.8
>
>
> KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
> this introduced a new regression: Following that change, the ./karaf startup
> command now only works when invoked from current directoy, no longer via
> absolute path. For example:
> {noformat}git clone git://git.apache.org/karaf.git
> cd karaf
> git checkout karaf-3.0.x
> cd tooling/karaf-maven-plugin
> mvn clean install
> cd ../..
> mvn clean install -DskipTests
> cd assemblies/apache-karaf/target/assembly/bin/
> chmod +x karaf
> ./karaf
> cd ../../../../..
> ./assemblies/apache-karaf/target/assembly/bin/karaf
> Error: Could not find or load main class org.apache.karaf.main.Main
> {noformat}
> Of course we could further fiddle with the startup script to solve this
> somehow, but it occurred to me that perhaps somewhere on Apache there is a
> ready made script for this already? Like maybe looking at e.g. how the Maven
> / Ant & other such tools (Gradle?) would be valuable.
> Perhaps some sort of non-regression integration test for both start-up
> scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4442) Improve slightly misleading message after SNAPSHOT feature installation
[ https://issues.apache.org/jira/browse/KARAF-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4442. - Resolution: Fixed > Improve slightly misleading message after SNAPSHOT feature installation > --- > > Key: KARAF-4442 > URL: https://issues.apache.org/jira/browse/KARAF-4442 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Yurii Rashkovskii >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > According to Karaf's own provisioning manual > (https://karaf.apache.org/manual/latest/users-guide/provisioning.html), "You > can update a release by installing the same feature (with the same SNAPSHOT > version or a different version)" > When I try to install a feature of the same SNAPSHOT version, in my case, > both through kar:install and feature:install, I get the following message: > The specified feature: 'feature' version '1.0.0.SNAPSHOT' is already > installed > However, if I look into the logs and effects of the command, I can clearly > see that the feature was in fact upgraded. > Therefore, I suggest that in this case (SNAPSHOT upgrade) the message should > be something like this > 'feature' version '1.0.0.SNAPSHOT' has been upgraded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4442) Improve slightly misleading message after SNAPSHOT feature installation
[ https://issues.apache.org/jira/browse/KARAF-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355823#comment-15355823 ] ASF subversion and git services commented on KARAF-4442: Commit 2d579b8e8df9c4b70a6486fddd139feb763ece7b in karaf's branch refs/heads/master from mfrazier [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=2d579b8 ] [KARAF-4442] Improving misleading message when updating a SNAPSHOT > Improve slightly misleading message after SNAPSHOT feature installation > --- > > Key: KARAF-4442 > URL: https://issues.apache.org/jira/browse/KARAF-4442 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Yurii Rashkovskii >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > According to Karaf's own provisioning manual > (https://karaf.apache.org/manual/latest/users-guide/provisioning.html), "You > can update a release by installing the same feature (with the same SNAPSHOT > version or a different version)" > When I try to install a feature of the same SNAPSHOT version, in my case, > both through kar:install and feature:install, I get the following message: > The specified feature: 'feature' version '1.0.0.SNAPSHOT' is already > installed > However, if I look into the logs and effects of the command, I can clearly > see that the feature was in fact upgraded. > Therefore, I suggest that in this case (SNAPSHOT upgrade) the message should > be something like this > 'feature' version '1.0.0.SNAPSHOT' has been upgraded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4442) Improve slightly misleading message after SNAPSHOT feature installation
[ https://issues.apache.org/jira/browse/KARAF-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355824#comment-15355824 ] ASF subversion and git services commented on KARAF-4442: Commit 62cee1c577519df59b75f35bd72ef04642f463b7 in karaf's branch refs/heads/master from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=62cee1c ] [KARAF-4442] This closes #188 > Improve slightly misleading message after SNAPSHOT feature installation > --- > > Key: KARAF-4442 > URL: https://issues.apache.org/jira/browse/KARAF-4442 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Yurii Rashkovskii >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > According to Karaf's own provisioning manual > (https://karaf.apache.org/manual/latest/users-guide/provisioning.html), "You > can update a release by installing the same feature (with the same SNAPSHOT > version or a different version)" > When I try to install a feature of the same SNAPSHOT version, in my case, > both through kar:install and feature:install, I get the following message: > The specified feature: 'feature' version '1.0.0.SNAPSHOT' is already > installed > However, if I look into the logs and effects of the command, I can clearly > see that the feature was in fact upgraded. > Therefore, I suggest that in this case (SNAPSHOT upgrade) the message should > be something like this > 'feature' version '1.0.0.SNAPSHOT' has been upgraded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4442) Improve slightly misleading message after SNAPSHOT feature installation
[ https://issues.apache.org/jira/browse/KARAF-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355828#comment-15355828 ] ASF subversion and git services commented on KARAF-4442: Commit 7b2dcb067b4e855c97fc2ee156e3723bad2efded in karaf's branch refs/heads/karaf-4.0.x from mfrazier [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7b2dcb0 ] [KARAF-4442] Improving misleading message when updating a SNAPSHOT > Improve slightly misleading message after SNAPSHOT feature installation > --- > > Key: KARAF-4442 > URL: https://issues.apache.org/jira/browse/KARAF-4442 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Yurii Rashkovskii >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > According to Karaf's own provisioning manual > (https://karaf.apache.org/manual/latest/users-guide/provisioning.html), "You > can update a release by installing the same feature (with the same SNAPSHOT > version or a different version)" > When I try to install a feature of the same SNAPSHOT version, in my case, > both through kar:install and feature:install, I get the following message: > The specified feature: 'feature' version '1.0.0.SNAPSHOT' is already > installed > However, if I look into the logs and effects of the command, I can clearly > see that the feature was in fact upgraded. > Therefore, I suggest that in this case (SNAPSHOT upgrade) the message should > be something like this > 'feature' version '1.0.0.SNAPSHOT' has been upgraded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4442) Improve slightly misleading message after SNAPSHOT feature installation
[ https://issues.apache.org/jira/browse/KARAF-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355827#comment-15355827 ] ASF GitHub Bot commented on KARAF-4442: --- Github user asfgit closed the pull request at: https://github.com/apache/karaf/pull/188 > Improve slightly misleading message after SNAPSHOT feature installation > --- > > Key: KARAF-4442 > URL: https://issues.apache.org/jira/browse/KARAF-4442 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 4.0.4 >Reporter: Yurii Rashkovskii >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.1.0, 4.0.6 > > > According to Karaf's own provisioning manual > (https://karaf.apache.org/manual/latest/users-guide/provisioning.html), "You > can update a release by installing the same feature (with the same SNAPSHOT > version or a different version)" > When I try to install a feature of the same SNAPSHOT version, in my case, > both through kar:install and feature:install, I get the following message: > The specified feature: 'feature' version '1.0.0.SNAPSHOT' is already > installed > However, if I look into the logs and effects of the command, I can clearly > see that the feature was in fact upgraded. > Therefore, I suggest that in this case (SNAPSHOT upgrade) the message should > be something like this > 'feature' version '1.0.0.SNAPSHOT' has been upgraded -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
[
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger updated KARAF-4599:
-
Affects Version/s: 3.0.7
> KARAF-4564 impact: karaf startup command now only works when invoked from
> current directoy, no longer via absolute path
> ---
>
> Key: KARAF-4599
> URL: https://issues.apache.org/jira/browse/KARAF-4599
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.7, 3.0.8
>Reporter: Michael Vorburger
>Priority: Critical
> Fix For: 3.0.8
>
>
> KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
> this introduced a new regression: Following that change, the ./karaf startup
> command now only works when invoked from current directoy, no longer via
> absolute path. For example:
> {noformat}git clone git://git.apache.org/karaf.git
> cd karaf
> git checkout karaf-3.0.x
> cd tooling/karaf-maven-plugin
> mvn clean install
> cd ../..
> mvn clean install -DskipTests
> cd assemblies/apache-karaf/target/assembly/bin/
> chmod +x karaf
> ./karaf
> cd ../../../../..
> ./assemblies/apache-karaf/target/assembly/bin/karaf
> Error: Could not find or load main class org.apache.karaf.main.Main
> {noformat}
> Of course we could further fiddle with the startup script to solve this
> somehow, but it occurred to me that perhaps somewhere on Apache there is a
> ready made script for this already? Like maybe looking at e.g. how the Maven
> / Ant & other such tools (Gradle?) would be valuable.
> Perhaps some sort of non-regression integration test for both start-up
> scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
[
https://issues.apache.org/jira/browse/KARAF-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Vorburger updated KARAF-4599:
-
Fix Version/s: 3.0.8
> KARAF-4564 impact: karaf startup command now only works when invoked from
> current directoy, no longer via absolute path
> ---
>
> Key: KARAF-4599
> URL: https://issues.apache.org/jira/browse/KARAF-4599
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.8
>Reporter: Michael Vorburger
>Priority: Critical
> Fix For: 3.0.8
>
>
> KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
> this introduced a new regression: Following that change, the ./karaf startup
> command now only works when invoked from current directoy, no longer via
> absolute path. For example:
> {noformat}git clone git://git.apache.org/karaf.git
> cd karaf
> git checkout karaf-3.0.x
> cd tooling/karaf-maven-plugin
> mvn clean install
> cd ../..
> mvn clean install -DskipTests
> cd assemblies/apache-karaf/target/assembly/bin/
> chmod +x karaf
> ./karaf
> cd ../../../../..
> ./assemblies/apache-karaf/target/assembly/bin/karaf
> Error: Could not find or load main class org.apache.karaf.main.Main
> {noformat}
> Of course we could further fiddle with the startup script to solve this
> somehow, but it occurred to me that perhaps somewhere on Apache there is a
> ready made script for this already? Like maybe looking at e.g. how the Maven
> / Ant & other such tools (Gradle?) would be valuable.
> Perhaps some sort of non-regression integration test for both start-up
> scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link
[ https://issues.apache.org/jira/browse/KARAF-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355623#comment-15355623 ] Michael Vorburger commented on KARAF-4564: -- ==> KARAF-4599 > Can't start karaf using symbolic link > -- > > Key: KARAF-4564 > URL: https://issues.apache.org/jira/browse/KARAF-4564 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.6 > Environment: Ubuntu (Linux vagrant 3.19.0-25-generic > #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 > GNU/Linux) > OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep 1 > 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64) > Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc) >Reporter: Alexis de Talhouët >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 3.0.7, 4.0.6 > > > When using a symbolic link to use the scripts defined here: > https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin > e.g. karaf or client and so on, it's failing to start the container and show > this error: > Error: Could not find or load main class org.apache.karaf.main.Main > This issue is related to the DIRNAME variable and the way it is setup. > This bug has been found in OpenDaylight, here is the ticket with more > information https://bugs.opendaylight.org/show_bug.cgi?id=6027 > I have also propose a candidate fix in ODL: > https://git.opendaylight.org/gerrit/#/c/39982/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4599) KARAF-4564 impact: karaf startup command now only works when invoked from current directoy, no longer via absolute path
Michael Vorburger created KARAF-4599:
Summary: KARAF-4564 impact: karaf startup command now only works
when invoked from current directoy, no longer via absolute path
Key: KARAF-4599
URL: https://issues.apache.org/jira/browse/KARAF-4599
Project: Karaf
Issue Type: Bug
Affects Versions: 3.0.8
Reporter: Michael Vorburger
Priority: Critical
KARAF-4564 introduced a fix for "Can't start karaf using symbolic link", but
this introduced a new regression: Following that change, the ./karaf startup
command now only works when invoked from current directoy, no longer via
absolute path. For example:
{noformat}git clone git://git.apache.org/karaf.git
cd karaf
git checkout karaf-3.0.x
cd tooling/karaf-maven-plugin
mvn clean install
cd ../..
mvn clean install -DskipTests
cd assemblies/apache-karaf/target/assembly/bin/
chmod +x karaf
./karaf
cd ../../../../..
./assemblies/apache-karaf/target/assembly/bin/karaf
Error: Could not find or load main class org.apache.karaf.main.Main
{noformat}
Of course we could further fiddle with the startup script to solve this
somehow, but it occurred to me that perhaps somewhere on Apache there is a
ready made script for this already? Like maybe looking at e.g. how the Maven /
Ant & other such tools (Gradle?) would be valuable.
Perhaps some sort of non-regression integration test for both start-up
scenarios, from current as well as via abs. path, would be of value?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4529) deployment of feature containing bundles with camel blueprint routes fail
[
https://issues.apache.org/jira/browse/KARAF-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355309#comment-15355309
]
John Poth commented on KARAF-4529:
--
Hello [~sahlex],
I havent been able to reproduce your issue in 4.0.5. From the logs it seems
though that you are missing the camel-blueprint bundle. Can you make sure it's
already installed in karaf or declared in your feature?
Cheers,
John.
> deployment of feature containing bundles with camel blueprint routes fail
> -
>
> Key: KARAF-4529
> URL: https://issues.apache.org/jira/browse/KARAF-4529
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.5
> Environment: Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17,
> mixed mode)
> Linux dbserver-p2 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> (2015-11-09) x86_64 GNU/Linux
>Reporter: Alexander Sahler
>Priority: Blocker
>
> When using the feature mechanism to deploy bundles containing blueprint files
> with camel routes, the deployment fails with exception
> {code}
> 2016-05-13 13:21:05,172 | ERROR | nsole user karaf | ShellUtil
> | 107 - org.apache.karaf.shell.core
> - 4.0.5 | Exception caught while executing command
> org.osgi.service.resolver.ResolutionException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.iden
> tity=pmc-impl; type=karaf.feature; version="[1.4.0.SNAPSHOT,1.4.0.SNAPSHOT]";
> filter:="(&(osgi.identity=pmc-impl)(type=kar
> af.feature)(version>=1.4.0.SNAPSHOT)(version<=1.4.0.SNAPSHOT))" [caused by:
> Unable to resolve pmc-impl/1.4.0.SNAPSHOT: mis
> sing requirement [pmc-impl/1.4.0.SNAPSHOT] osgi.identity;
> osgi.identity=pmc-impl; type=osgi.bundle; version="[1.4.0.SNAPSH
> OT,1.4.0.SNAPSHOT]"; resolution:=mandatory [caused by: Unable to resolve
> pmc-impl/1.4.0.SNAPSHOT: missing requirement [pmc
> -impl/1.4.0.SNAPSHOT] osgi.service; effective:=active;
> filter:="(&(objectClass=org.apache.aries.blueprint.NamespaceHandler
> )(osgi.service.blueprint.namespace=http://camel.apache.org/schema/blueprint))"]]
> at
> org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)[org.apache.felix.framework-5.4.0
> .jar:]
> at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:216)[9:org.apache.ka
> raf.features.core:4.0.5]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:263)[9:org.apache.karaf.features.core:
> 4.0.5]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1152)[9:org
> .apache.karaf.features.core:4.0.5]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:1048)[9:org.apac
> he.karaf.features.core:4.0.5]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_66]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_66]
> at java.lang.Thread.run(Thread.java:745)[:1.8.0_66]
> {code}
> However, when I install all the dependencies in the feature manually in the
> console (via install -s) and the bundle itself the same way, the deployment
> works perfectly!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
