[jira] [Commented] (KARAF-4578) Fileinstaller does not install bundle to root region after clean start
[ https://issues.apache.org/jira/browse/KARAF-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514193#comment-15514193 ] Benjamin Graf commented on KARAF-4578: -- KARAF-4723 seems to resolve this issue. > Fileinstaller does not install bundle to root region after clean start > -- > > Key: KARAF-4578 > URL: https://issues.apache.org/jira/browse/KARAF-4578 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-feature >Affects Versions: 4.0.5 >Reporter: Benjamin Graf >Assignee: Jean-Baptiste Onofré >Priority: Critical > > The file installer is starting to work in parallel to the activation of > org.apache.karaf.features.core which does the region hook initialization. > This causes that bundles are installed to no region causing them not to get > sucessfully resolved. Might also be the cause of KARAF-4498. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514171#comment-15514171 ] Marc Durand commented on KARAF-4723: I can reproduce this also on Karaf 4.0.6. I can test this with 4.0.8 but I don't know how to build my project to pull in the 4.0.8-SNAPSHOT. > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514155#comment-15514155 ] Guillaume Nodet commented on KARAF-4723: Yes, I think so. > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514047#comment-15514047 ] Benjamin Graf commented on KARAF-4723: -- @[~gnt]: Might be the same cause as in KARAF-4578? It seems that I can't reproduce error any more. > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3513) JMXConnectorServer should be able to pick up the new KeystoreInstance available in container
[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513081#comment-15513081
]
Freeman Fang commented on KARAF-3513:
-
Hi Paolo,
The fix for KARAF-3515 on master is [1].
In Karaf 4.x we get rid of the compulsory blueprint dependency so in Karaf 4.x
this fix introduce a ServiceTracker in Activator which play the same role as
reference-listener bind/unbind method in blueprint configuration of Karaf
2.x/3.x to handle the service come and go dynamically.
So about your patch on karaf master, I think you can merge your
register/unregister logic in the ServiceTracker of Activator, in the
addingService/removedService separately.
[1]http://git-wip-us.apache.org/repos/asf/karaf/commit/141bf0c9
Thanks
Freeman
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
>
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;>
> rank="1"
>path="..."
>keystorePassword="..."
>keyPasswords="..." />
>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (KARAF-3513) JMXConnectorServer should be able to pick up the new KeystoreInstance available in container
[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated KARAF-3513:
Comment: was deleted
(was: Hi Paolo,
A quick answer
The commit for KARAF-3513 on master is
http://git-wip-us.apache.org/repos/asf/karaf/commit/141bf0c9
Need take a close look and your PR and add comment later on.
Freeman
)
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
>
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;>
> rank="1"
>path="..."
>keystorePassword="..."
>keyPasswords="..." />
>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3513) JMXConnectorServer should be able to pick up the new KeystoreInstance available in container
[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513032#comment-15513032
]
Freeman Fang commented on KARAF-3513:
-
Hi Paolo,
A quick answer
The commit for KARAF-3513 on master is
http://git-wip-us.apache.org/repos/asf/karaf/commit/141bf0c9
Need take a close look and your PR and add comment later on.
Freeman
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
>
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;>
> rank="1"
>path="..."
>keystorePassword="..."
>keyPasswords="..." />
>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-4727) SCR bundle state should not report SATISFIED components
[ https://issues.apache.org/jira/browse/KARAF-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4727. Resolution: Fixed Fix Version/s: 4.1.0 > SCR bundle state should not report SATISFIED components > --- > > Key: KARAF-4727 > URL: https://issues.apache.org/jira/browse/KARAF-4727 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4727) SCR bundle state should not report SATISFIED components
[ https://issues.apache.org/jira/browse/KARAF-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated KARAF-4727: --- Affects Version/s: (was: 4.0.6) 4.1.0 > SCR bundle state should not report SATISFIED components > --- > > Key: KARAF-4727 > URL: https://issues.apache.org/jira/browse/KARAF-4727 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.1.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512973#comment-15512973 ] ASF subversion and git services commented on KARAF-4723: Commit 9e615f0007a29d012d6d35bbf63672d4f053463e in karaf's branch refs/heads/karaf-4.0.x from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9e615f0 ] [KARAF-4723] Make sure satisfied activators are started synchronously > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-4723. Resolution: Fixed Assignee: Guillaume Nodet Fix Version/s: 4.0.8 4.1.0 > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Assignee: Guillaume Nodet >Priority: Minor > Fix For: 4.1.0, 4.0.8 > > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3513) JMXConnectorServer should be able to pick up the new KeystoreInstance available in container
[
https://issues.apache.org/jira/browse/KARAF-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512886#comment-15512886
]
Paolo Antinori commented on KARAF-3513:
---
[~ffang] Hi, I don't see commits related to this JIRA
https://issues.apache.org/jira/browse/KARAF-3513 in current 4.x Master
Do you think this is correct?
I'd like to contribute on top of your commits, with this fix:
https://github.com/jboss-fuse/karaf/compare/2.4.0.redhat-6-3-x...paoloantinori:ENTESB-2192_picked?expand=1
that seems to have been already reported here:
https://issues.apache.org/jira/browse/KARAF-3887
Can I ask you to double check if anything is missing or if I'm looking at the
wrong place?
> JMXConnectorServer should be able to pick up the new KeystoreInstance
> available in container
>
>
> Key: KARAF-3513
> URL: https://issues.apache.org/jira/browse/KARAF-3513
> Project: Karaf
> Issue Type: Improvement
>Reporter: Freeman Fang
>Assignee: Freeman Fang
> Fix For: 2.4.2, 3.0.4, 4.0.0.M3
>
>
> when we configure the JMX Connector with SSL enabled, if there's no valid
> keystore available in the first place when start the "Apache Karaf ::
> Management" bundle, that bundle can't pick up any KeystoreInstance available
> afterwards.
> For an instance, if we drop a keystore.xml file like
> {code}
> http://www.osgi.org/xmlns/blueprint/v1.0.0;
> xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;>
> rank="1"
>path="..."
>keystorePassword="..."
>keyPasswords="..." />
>
> {code}
> into etc folder after we start karaf, a bundle created accordingly and a
> KeystoreInstance get published, however, the JMX Connector won't be able to
> pick up this new KeystoreInstance, unless we manually refresh "Apache Karaf
> :: Management" bundle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-4723) Karaf sometimes will prioritize bundles in deploy folder at first start regardless of run level
[ https://issues.apache.org/jira/browse/KARAF-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512845#comment-15512845 ] ASF subversion and git services commented on KARAF-4723: Commit bff4449972dc991e572681d1278249a05d7c2166 in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=bff4449 ] [KARAF-4723] Make sure satisfied activators are started synchronously > Karaf sometimes will prioritize bundles in deploy folder at first start > regardless of run level > --- > > Key: KARAF-4723 > URL: https://issues.apache.org/jira/browse/KARAF-4723 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Allen Bagwell >Priority: Minor > > Problem is illustrated at this link, and there is a potential fix. > http://karaf.922171.n3.nabble.com/Hot-deploy-priority-on-first-start-up-td4047948.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4727) SCR bundle state should not report SATISFIED components
[ https://issues.apache.org/jira/browse/KARAF-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512846#comment-15512846 ] ASF subversion and git services commented on KARAF-4727: Commit 858920dd0a50af2d52003c3e75ac5063b027ddac in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=858920d ] [KARAF-4727] SCR bundle state should not report SATISFIED components > SCR bundle state should not report SATISFIED components > --- > > Key: KARAF-4727 > URL: https://issues.apache.org/jira/browse/KARAF-4727 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 4.0.6 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4727) SCR bundle state should not report SATISFIED components
Guillaume Nodet created KARAF-4727: -- Summary: SCR bundle state should not report SATISFIED components Key: KARAF-4727 URL: https://issues.apache.org/jira/browse/KARAF-4727 Project: Karaf Issue Type: Bug Components: karaf-core Affects Versions: 4.0.6 Reporter: Guillaume Nodet Assignee: Guillaume Nodet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4726) Improve os-integration doc
[ https://issues.apache.org/jira/browse/KARAF-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512571#comment-15512571 ] ASF GitHub Bot commented on KARAF-4726: --- GitHub user lburgazzoli opened a pull request: https://github.com/apache/karaf/pull/242 KARAF-4726: Improve os-integration doc You can merge this pull request into a Git repository by running: $ git pull https://github.com/lburgazzoli/apache-karaf KARAF-4726 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/242.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 #242 > Improve os-integration doc > -- > > Key: KARAF-4726 > URL: https://issues.apache.org/jira/browse/KARAF-4726 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > > Document bin/contrib usage. > I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4726) Improve os-integration doc
[ https://issues.apache.org/jira/browse/KARAF-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4726: --- Assignee: (was: Jean-Baptiste Onofré) > Improve os-integration doc > -- > > Key: KARAF-4726 > URL: https://issues.apache.org/jira/browse/KARAF-4726 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > > Document bin/contrib usage. > I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4726) Improve os-integration doc
[ https://issues.apache.org/jira/browse/KARAF-4726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli updated KARAF-4726: --- Fix Version/s: (was: 4.0.7) (was: 4.1.0) > Improve os-integration doc > -- > > Key: KARAF-4726 > URL: https://issues.apache.org/jira/browse/KARAF-4726 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-os-integration >Reporter: Luca Burgazzoli >Priority: Minor > > Document bin/contrib usage. > I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KARAF-4726) Improve os-integration doc
Luca Burgazzoli created KARAF-4726: -- Summary: Improve os-integration doc Key: KARAF-4726 URL: https://issues.apache.org/jira/browse/KARAF-4726 Project: Karaf Issue Type: Bug Components: karaf-documentation, karaf-os-integration Reporter: Luca Burgazzoli Assignee: Jean-Baptiste Onofré Priority: Minor Fix For: 4.1.0, 4.0.7 Document bin/contrib usage. I will provide a PR -- This message was sent by Atlassian JIRA (v6.3.4#6332)
