[jira] [Commented] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692749#comment-16692749
]
Volker Althaus commented on KARAF-6005:
---
Thanks for your analysis. I also suspected that the missing metadata is the
cause.
But I do not quite agree to mark the bug as "won't fix".
If I have a Maven resolution mechanism and the range resolution is an official
supported feature, it should make no difference where the artifact lies.
Even without metadata you get the versions of an artifact from the existing
directory names and files. From then on, the resolution algorithm should
actually be the same as if the data comes from the maven-metadata-local.xml.
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
>
> I defined a feature with a ranged bundle version:
>
> mvn:de.some.api/api/[1,2)
>
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting
[jira] [Commented] (KARAF-5927) Upgrade to XBean 4.12
[ https://issues.apache.org/jira/browse/KARAF-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691832#comment-16691832 ] ASF subversion and git services commented on KARAF-5927: Commit 8824088340b6bae5e43ce03366bcc991284a5779 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=8824088 ] [KARAF-5927] Upgrade to XBean 4.12 > Upgrade to XBean 4.12 > - > > Key: KARAF-5927 > URL: https://issues.apache.org/jira/browse/KARAF-5927 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5927) Upgrade to XBean 4.12
[ https://issues.apache.org/jira/browse/KARAF-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5927. - Resolution: Fixed > Upgrade to XBean 4.12 > - > > Key: KARAF-5927 > URL: https://issues.apache.org/jira/browse/KARAF-5927 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5927) Upgrade to XBean 4.12
[ https://issues.apache.org/jira/browse/KARAF-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691833#comment-16691833 ] ASF subversion and git services commented on KARAF-5927: Commit 273f5e4251b36eabb21e90fd2f696e84d551eb80 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=273f5e4 ] Merge pull request #650 from jbonofre/KARAF-5927 [KARAF-5927] Upgrade to XBean 4.12 > Upgrade to XBean 4.12 > - > > Key: KARAF-5927 > URL: https://issues.apache.org/jira/browse/KARAF-5927 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5927) Upgrade to XBean 4.12
[ https://issues.apache.org/jira/browse/KARAF-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691834#comment-16691834 ] ASF subversion and git services commented on KARAF-5927: Commit 273f5e4251b36eabb21e90fd2f696e84d551eb80 in karaf's branch refs/heads/master from [~j...@nanthrax.net] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=273f5e4 ] Merge pull request #650 from jbonofre/KARAF-5927 [KARAF-5927] Upgrade to XBean 4.12 > Upgrade to XBean 4.12 > - > > Key: KARAF-5927 > URL: https://issues.apache.org/jira/browse/KARAF-5927 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5927) Upgrade to XBean 4.12
[ https://issues.apache.org/jira/browse/KARAF-5927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691831#comment-16691831 ] ASF GitHub Bot commented on KARAF-5927: --- jbonofre closed pull request #650: [KARAF-5927] Upgrade to XBean 4.12 URL: https://github.com/apache/karaf/pull/650 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index e64ae8632e..769c1b5175 100644 --- a/pom.xml +++ b/pom.xml @@ -305,7 +305,7 @@ 10.12.1.1 2.0.0-M24 1.3.10_1 -4.9 +4.12 2.12.0_1 2.7.2_3 2.7.2_1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to XBean 4.12 > - > > Key: KARAF-5927 > URL: https://issues.apache.org/jira/browse/KARAF-5927 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5939) karaf-assembly packaging fails with m-i-p 3.0.0-M1
[ https://issues.apache.org/jira/browse/KARAF-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691814#comment-16691814 ] ASF GitHub Bot commented on KARAF-5939: --- jbonofre opened a new pull request #654: [KARAF-5939] Update and support maven-install-plugin 3.0.0.M1 URL: https://github.com/apache/karaf/pull/654 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > karaf-assembly packaging fails with m-i-p 3.0.0-M1 > -- > > Key: KARAF-5939 > URL: https://issues.apache.org/jira/browse/KARAF-5939 > Project: Karaf > Issue Type: Bug > Components: karaf >Affects Versions: 4.0.10 >Reporter: Mark Derricutt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.11, 4.2.2, 4.1.7 > > > The Apache Maven team just released 3.0.0-M1 of the maven-install-plugin, > which contains > MINSTALL-118 - our project is using karaf-maven-plugin 4.0.10 and this seems > to trip up with: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install > (default-install) on project smx3.karaf.defaultconfig: > NoFileAssignedException: The packaging plugin for this project did not assign > a main file to the project but it has attachments. Change packaging to 'pom'. > -> [Help 1] > > I don't know if this has been fixed in later releases of karaf-maven-plugin, > or if a patch version of 4.0.10.x will be made, but for now will lock down > our builds install-plugin version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6014) Improve jdbc:* commands
[
https://issues.apache.org/jira/browse/KARAF-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691806#comment-16691806
]
Grzegorz Grzybek commented on KARAF-6014:
-
First improvement:
{noformat}
karaf@root()> jdbc:ds-factories
Name │ Class │ Version │
Registered by bundle
─┼─┼─┼
com.mysql.jdbc │ com.mysql.fabric.jdbc.FabricMySQLDriver │ 5.1.46 │
com.mysql.jdbc [59]
org.mariadb.jdbc │ org.mariadb.jdbc.Driver │ 1.5.9.0 │
org.mariadb.jdbc [49]
mariadb │ org.mariadb.jdbc.Driver │ │
org.ops4j.pax.jdbc.mariadb [50]
mysql│ org.mariadb.jdbc.Driver │ │
org.ops4j.pax.jdbc.mariadb [50]
{noformat}
> Improve jdbc:* commands
> ---
>
> Key: KARAF-6014
> URL: https://issues.apache.org/jira/browse/KARAF-6014
> Project: Karaf
> Issue Type: Improvement
>Affects Versions: 4.2.1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.2.2
>
>
> {{jdbc:*}} commands do not work well when there are multiple instances of:
> * {{org.osgi.service.jdbc.DataSourceFactory}}
> * {{javax.sql.DataSource}}
> This is caused partially by pax-jdbc itself, where:
> * {{pax-jdbc}} bundle registers {{DataSourceFactory}} for each driver class
> specified in {{/META-INF/services/java.sql.Driver}} of jdbc driver bundle
> * e.g., {{pax-jdbc-mariadb}} registers the same {{DataSourceFactory}}
> instance with different names: {{mariadb}} and {{mysql}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5703) pax jdbc config 1.2.0 fails to register XA Datasource
[
https://issues.apache.org/jira/browse/KARAF-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691753#comment-16691753
]
Grzegorz Grzybek commented on KARAF-5703:
-
This was fixed in pax-jdbc 1.2.1. Now I've upgraded to pax-jdbc 1.3.1 and it
should work.
> pax jdbc config 1.2.0 fails to register XA Datasource
> -
>
> Key: KARAF-5703
> URL: https://issues.apache.org/jira/browse/KARAF-5703
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.0
> Environment: Karaf 4.2.0, Windows 10 Centos 7/JDK 8 (1.8.0_162)
>Reporter: Carlos Villegas
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Labels: XA, jdbc, pool
> Fix For: 4.2.2
>
>
> Under Karaf 4.1.x I was able to define a XA DataSource by setting the
> following:
>
> {{feature:install transaction jndi pax-jdbc-config pax-jdbc-pool-dbcp2 jdbc}}
> {{bundle:install -s mvn:org.postgresql/postgresql/42.2.2}}
> {{config:edit org.ops4j.datasource-TestDS}}
> {{config:property-set osgi.jdbc.driver.class org.postgresql.Driver}}
> {{config:property-set pool dbcp2}}
> {{config:property-set xa true}}
> {{config:property-set serverName localhost}}
> {{config:property-set databaseName test}}
> {{config:property-set portNumber 5432}}
> {{config:property-set user test}}
> {{config:property-set password test}}
> {{config:property-set dataSourceName TestDS}}
> {{config:property-set jdbc.pool.maxTotal 16}}
> {{config:update}}
>
> This doesn't work anymore in 4.2.0, the DataSource doesn't get registered.
> pax-jdbc-config doesn't seem to be scanning the configuration anymore. I see
> no messages in the logs, not even errors.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5703) pax jdbc config 1.2.0 fails to register XA Datasource
[
https://issues.apache.org/jira/browse/KARAF-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved KARAF-5703.
-
Resolution: Fixed
> pax jdbc config 1.2.0 fails to register XA Datasource
> -
>
> Key: KARAF-5703
> URL: https://issues.apache.org/jira/browse/KARAF-5703
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.0
> Environment: Karaf 4.2.0, Windows 10 Centos 7/JDK 8 (1.8.0_162)
>Reporter: Carlos Villegas
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Labels: XA, jdbc, pool
> Fix For: 4.2.2
>
>
> Under Karaf 4.1.x I was able to define a XA DataSource by setting the
> following:
>
> {{feature:install transaction jndi pax-jdbc-config pax-jdbc-pool-dbcp2 jdbc}}
> {{bundle:install -s mvn:org.postgresql/postgresql/42.2.2}}
> {{config:edit org.ops4j.datasource-TestDS}}
> {{config:property-set osgi.jdbc.driver.class org.postgresql.Driver}}
> {{config:property-set pool dbcp2}}
> {{config:property-set xa true}}
> {{config:property-set serverName localhost}}
> {{config:property-set databaseName test}}
> {{config:property-set portNumber 5432}}
> {{config:property-set user test}}
> {{config:property-set password test}}
> {{config:property-set dataSourceName TestDS}}
> {{config:property-set jdbc.pool.maxTotal 16}}
> {{config:update}}
>
> This doesn't work anymore in 4.2.0, the DataSource doesn't get registered.
> pax-jdbc-config doesn't seem to be scanning the configuration anymore. I see
> no messages in the logs, not even errors.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-5703) pax jdbc config 1.2.0 fails to register XA Datasource
[
https://issues.apache.org/jira/browse/KARAF-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-5703:
---
Assignee: Grzegorz Grzybek
> pax jdbc config 1.2.0 fails to register XA Datasource
> -
>
> Key: KARAF-5703
> URL: https://issues.apache.org/jira/browse/KARAF-5703
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.0
> Environment: Karaf 4.2.0, Windows 10 Centos 7/JDK 8 (1.8.0_162)
>Reporter: Carlos Villegas
>Assignee: Grzegorz Grzybek
>Priority: Critical
> Labels: XA, jdbc, pool
> Fix For: 4.2.2
>
>
> Under Karaf 4.1.x I was able to define a XA DataSource by setting the
> following:
>
> {{feature:install transaction jndi pax-jdbc-config pax-jdbc-pool-dbcp2 jdbc}}
> {{bundle:install -s mvn:org.postgresql/postgresql/42.2.2}}
> {{config:edit org.ops4j.datasource-TestDS}}
> {{config:property-set osgi.jdbc.driver.class org.postgresql.Driver}}
> {{config:property-set pool dbcp2}}
> {{config:property-set xa true}}
> {{config:property-set serverName localhost}}
> {{config:property-set databaseName test}}
> {{config:property-set portNumber 5432}}
> {{config:property-set user test}}
> {{config:property-set password test}}
> {{config:property-set dataSourceName TestDS}}
> {{config:property-set jdbc.pool.maxTotal 16}}
> {{config:update}}
>
> This doesn't work anymore in 4.2.0, the DataSource doesn't get registered.
> pax-jdbc-config doesn't seem to be scanning the configuration anymore. I see
> no messages in the logs, not even errors.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5703) pax jdbc config 1.2.0 fails to register XA Datasource
[
https://issues.apache.org/jira/browse/KARAF-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated KARAF-5703:
Fix Version/s: 4.2.2
> pax jdbc config 1.2.0 fails to register XA Datasource
> -
>
> Key: KARAF-5703
> URL: https://issues.apache.org/jira/browse/KARAF-5703
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.0
> Environment: Karaf 4.2.0, Windows 10 Centos 7/JDK 8 (1.8.0_162)
>Reporter: Carlos Villegas
>Priority: Critical
> Labels: XA, jdbc, pool
> Fix For: 4.2.2
>
>
> Under Karaf 4.1.x I was able to define a XA DataSource by setting the
> following:
>
> {{feature:install transaction jndi pax-jdbc-config pax-jdbc-pool-dbcp2 jdbc}}
> {{bundle:install -s mvn:org.postgresql/postgresql/42.2.2}}
> {{config:edit org.ops4j.datasource-TestDS}}
> {{config:property-set osgi.jdbc.driver.class org.postgresql.Driver}}
> {{config:property-set pool dbcp2}}
> {{config:property-set xa true}}
> {{config:property-set serverName localhost}}
> {{config:property-set databaseName test}}
> {{config:property-set portNumber 5432}}
> {{config:property-set user test}}
> {{config:property-set password test}}
> {{config:property-set dataSourceName TestDS}}
> {{config:property-set jdbc.pool.maxTotal 16}}
> {{config:update}}
>
> This doesn't work anymore in 4.2.0, the DataSource doesn't get registered.
> pax-jdbc-config doesn't seem to be scanning the configuration anymore. I see
> no messages in the logs, not even errors.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5931) More than one Datrasource Configuration does not work
[
https://issues.apache.org/jira/browse/KARAF-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691747#comment-16691747
]
Grzegorz Grzybek commented on KARAF-5931:
-
Fixed in 4.2.2 by upgrading to pax-jdbc 1.3.1
[here|https://github.com/apache/karaf/commit/500885038b7d14337c87695af940de6f0a307ede].
> More than one Datrasource Configuration does not work
> -
>
> Key: KARAF-5931
> URL: https://issues.apache.org/jira/browse/KARAF-5931
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Gerhard Munze
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Labels: DataSource, karaf
> Fix For: 4.2.2
>
>
> When you configure more than one
> org.ops4j.datasource in karaf/etc folder,the server doesnt start.
> The following Exception is thrown:
> {code:java}
> 2018-09-06T13:10:49,587 | ERROR | activator-1-thread-2 |
> BootFeaturesInstaller | 9 - org.apache.karaf.features.core -
> 4.2.1 | Error installing boot features
> org.osgi.framework.BundleException: Activator stop error in bundle
> org.ops4j.pax.jdbc.config [14].
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2692)
> ~[?:?]
> at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:1038)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.stopBundle(BundleInstallSupportImpl.java:167)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.stopBundle(FeaturesServiceImpl.java:1121)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:748)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
> [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[?:?]
> at java.util.HashMap$KeyIterator.next(HashMap.java:1461) ~[?:?]
> at
> org.ops4j.pax.jdbc.config.impl.DataSourceConfigManager.destroy(DataSourceConfigManager.java:193)
> ~[?:?]
> at org.ops4j.pax.jdbc.config.impl.Activator.stop(Activator.java:77)
> ~[?:?]
> at
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>
> ~[?:?]
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2636)
> ~[?:?]
> ... 10 more
> {code}
> I am using one postgres Datasource and one mariadb/mysql datasource.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5931) More than one Datrasource Configuration does not work
[
https://issues.apache.org/jira/browse/KARAF-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved KARAF-5931.
-
Resolution: Fixed
> More than one Datrasource Configuration does not work
> -
>
> Key: KARAF-5931
> URL: https://issues.apache.org/jira/browse/KARAF-5931
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Gerhard Munze
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Labels: DataSource, karaf
> Fix For: 4.2.2
>
>
> When you configure more than one
> org.ops4j.datasource in karaf/etc folder,the server doesnt start.
> The following Exception is thrown:
> {code:java}
> 2018-09-06T13:10:49,587 | ERROR | activator-1-thread-2 |
> BootFeaturesInstaller | 9 - org.apache.karaf.features.core -
> 4.2.1 | Error installing boot features
> org.osgi.framework.BundleException: Activator stop error in bundle
> org.ops4j.pax.jdbc.config [14].
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2692)
> ~[?:?]
> at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:1038)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.stopBundle(BundleInstallSupportImpl.java:167)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.stopBundle(FeaturesServiceImpl.java:1121)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:748)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
> [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[?:?]
> at java.util.HashMap$KeyIterator.next(HashMap.java:1461) ~[?:?]
> at
> org.ops4j.pax.jdbc.config.impl.DataSourceConfigManager.destroy(DataSourceConfigManager.java:193)
> ~[?:?]
> at org.ops4j.pax.jdbc.config.impl.Activator.stop(Activator.java:77)
> ~[?:?]
> at
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>
> ~[?:?]
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2636)
> ~[?:?]
> ... 10 more
> {code}
> I am using one postgres Datasource and one mariadb/mysql datasource.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5931) More than one Datrasource Configuration does not work
[
https://issues.apache.org/jira/browse/KARAF-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691743#comment-16691743
]
ASF subversion and git services commented on KARAF-5931:
Commit 500885038b7d14337c87695af940de6f0a307ede in karaf's branch
refs/heads/master from [~grzes]
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=5008850 ]
[KARAF-5931] Upgrade to pax-jdbc 1.3.1
> More than one Datrasource Configuration does not work
> -
>
> Key: KARAF-5931
> URL: https://issues.apache.org/jira/browse/KARAF-5931
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Gerhard Munze
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Labels: DataSource, karaf
> Fix For: 4.2.2
>
>
> When you configure more than one
> org.ops4j.datasource in karaf/etc folder,the server doesnt start.
> The following Exception is thrown:
> {code:java}
> 2018-09-06T13:10:49,587 | ERROR | activator-1-thread-2 |
> BootFeaturesInstaller | 9 - org.apache.karaf.features.core -
> 4.2.1 | Error installing boot features
> org.osgi.framework.BundleException: Activator stop error in bundle
> org.ops4j.pax.jdbc.config [14].
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2692)
> ~[?:?]
> at org.apache.felix.framework.BundleImpl.stop(BundleImpl.java:1038)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.BundleInstallSupportImpl.stopBundle(BundleInstallSupportImpl.java:167)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.stopBundle(FeaturesServiceImpl.java:1121)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:748)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> ~[?:?]
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> ~[?:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
> [?:?]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
> [?:?]
> at java.lang.Thread.run(Thread.java:748) [?:?]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) ~[?:?]
> at java.util.HashMap$KeyIterator.next(HashMap.java:1461) ~[?:?]
> at
> org.ops4j.pax.jdbc.config.impl.DataSourceConfigManager.destroy(DataSourceConfigManager.java:193)
> ~[?:?]
> at org.ops4j.pax.jdbc.config.impl.Activator.stop(Activator.java:77)
> ~[?:?]
> at
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>
> ~[?:?]
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2636)
> ~[?:?]
> ... 10 more
> {code}
> I am using one postgres Datasource and one mariadb/mysql datasource.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691732#comment-16691732
]
Grzegorz Grzybek commented on KARAF-6005:
-
[~valthaus] I did one test.
I created artificial:
* ~/.m2/repository/commons-io/commons-io2/2.6/commons-io2-2.6.pom
* ~/.m2/repository/commons-io/commons-io2/2.6/commons-io2-2.6.jar
(note - there's no {{commons-io2}} artifact anywhere in the world).
With only this, I wasn't able to resolve such artifact:
{noformat}
karaf@root()> install 'mvn:commons-io/commons-io2/[2.5,2.7)'
Bundle IDs:
Error executing command: Error installing bundles:
Unable to install bundle mvn:commons-io/commons-io2/[2.5,2.7):
org.osgi.framework.BundleException: Unable to cache bundle:
mvn:commons-io/commons-io2/[2.5,2.7)
{noformat}
But after I created:
* ~/.m2/repository/commons-io/commons-io2/maven-metadata-local.xml
With:
{code:xml}
commons-io
commons-io2
2.6
20171211134705
{code}
I was able to resolve such artifact:
{noformat}
karaf@root()> install 'mvn:commons-io/commons-io2/[2.5,2.7)'
Bundle ID: 48
{noformat}
In logs (after uncomenting the section "# help with identification of
maven-related problems with pax-url-aether"), I saw:
{noformat}
2018-11-19T15:00:39,750 | DEBUG | pipe-install
'mvn:commons-io/commons-io2/[2.5,2.7)' | Connection | 4 -
org.ops4j.pax.url.mvn - 2.5.4 | Resolving [mvn:commons-io/commons-io2/[2.5,2.7)]
2018-11-19T15:00:39,754 | DEBUG | DefaultMetadataResolver-3-0 |
DefaultTransporterProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
transporter WagonTransporter with priority -1.0 for
http://repo1.maven.org/maven2/
2018-11-19T15:00:39,755 | DEBUG | DefaultMetadataResolver-3-2 |
DefaultTransporterProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
transporter WagonTransporter with priority -1.0 for
https://oss.sonatype.org/content/repositories/ops4j-snapshots/
2018-11-19T15:00:39,755 | DEBUG | DefaultMetadataResolver-3-1 |
DefaultTransporterProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
transporter WagonTransporter with priority -1.0 for
http://repository.apache.org/content/groups/snapshots-group/
2018-11-19T15:00:39,756 | DEBUG | DefaultMetadataResolver-3-0 |
DefaultRepositoryConnectorProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
connector BasicRepositoryConnector with priority 0.0 for
http://repo1.maven.org/maven2/
2018-11-19T15:00:39,757 | DEBUG | DefaultMetadataResolver-3-1 |
DefaultRepositoryConnectorProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
connector BasicRepositoryConnector with priority 0.0 for
http://repository.apache.org/content/groups/snapshots-group/
2018-11-19T15:00:39,757 | DEBUG | DefaultMetadataResolver-3-2 |
DefaultRepositoryConnectorProvider | 4 - org.ops4j.pax.url.mvn - 2.5.4 | Using
connector BasicRepositoryConnector with priority 0.0 for
https://oss.sonatype.org/content/repositories/ops4j-snapshots/
2018-11-19T15:00:39,854 | DEBUG | DefaultMetadataResolver-3-0 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-13 >> GET
/maven2/commons-io/commons-io2/maven-metadata.xml HTTP/1.1
...
2018-11-19T15:00:39,859 | DEBUG | DefaultMetadataResolver-3-0 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-13 >>
Host: repo1.maven.org
...
2018-11-19T15:00:39,912 | DEBUG | DefaultMetadataResolver-3-0 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-13 <<
HTTP/1.1 404 Not Found
...
2018-11-19T15:00:39,925 | DEBUG | DefaultMetadataResolver-3-0 |
DefaultUpdateCheckManager| 4 - org.ops4j.pax.url.mvn - 2.5.4 | Writing
tracking file
/home/ggrzybek/.m2/repository/commons-io/commons-io2/resolver-status.properties
2018-11-19T15:00:39,947 | DEBUG | DefaultMetadataResolver-3-1 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-14 >> GET
/content/groups/snapshots-group/commons-io/commons-io2/maven-metadata.xml
HTTP/1.1
...
2018-11-19T15:00:39,949 | DEBUG | DefaultMetadataResolver-3-1 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-14 >>
Host: repository.apache.org
...
2018-11-19T15:00:40,102 | DEBUG | DefaultMetadataResolver-3-1 | headers
| 4 - org.ops4j.pax.url.mvn - 2.5.4 | http-outgoing-14 <<
HTTP/1.1 404 Not Found
...
2018-11-19T15:00:40,110 | DEBUG | DefaultMetadataResolver-3-1 |
DefaultUpdateCheckManager| 4 - org.ops4j.pax.url.mvn - 2.5.4 | Writing
tracking file
/home/ggrzybek/.m2/repository/commons-io/commons-io2/resolver-status.properties
2018-11-19T15:00:40,271 | DEBUG | DefaultMetadataResolver-3-2 | headers
[jira] [Assigned] (KARAF-6005) Resolve of bundle with version range in a feature only works with ".m2" and not with "system" directory
[
https://issues.apache.org/jira/browse/KARAF-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-6005:
---
Assignee: Grzegorz Grzybek
> Resolve of bundle with version range in a feature only works with ".m2" and
> not with "system" directory
> ---
>
> Key: KARAF-6005
> URL: https://issues.apache.org/jira/browse/KARAF-6005
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Volker Althaus
>Assignee: Grzegorz Grzybek
>Priority: Critical
>
> I defined a feature with a ranged bundle version:
>
> mvn:de.some.api/api/[1,2)
>
> If a bundle within that range lies within the global/user Maven repo ".m2",
> the bundle gets resolved.
> If it resides only within the "system" folder of Karaf I get an exception:
> {noformat}
> karaf@root()> org.apache.karaf.features.internal.util.MultiException: Error:
> Error downloading mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.(MavenDownloadManager.java:91)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:457)
> at
> org.apache.karaf.features.internal.region.Subsystem.downloadBundles(Subsystem.java:452)
> at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:224)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:388)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1025)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:964)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Suppressed: java.io.IOException: Error downloading
> mvn:de.some.api/api/[1,2)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:77)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> ... 3 more
> Caused by: java.io.IOException: Error resolving artifact
> de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:729)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:659)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:600)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:567)
> at
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:47)
> at
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:60)
> ... 7 more
> Caused by:
> shaded.org.eclipse.aether.resolution.VersionRangeResolutionException: No
> highest version found for de.some.api:api:[1,2)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveLatestVersionRange(AetherBasedResolver.java:998)
> at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:703)
> ... 12 more
> {noformat}
> Setting the property org.ops4j.pax.url.mvn.defaultLocalRepoAsRemote = true as
> mentioned in the mailing list does not help.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6013) Setting node alias breaks synchonization
[ https://issues.apache.org/jira/browse/KARAF-6013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691716#comment-16691716 ] ASF GitHub Bot commented on KARAF-6013: --- nicolas-dutertry opened a new pull request #58: [KARAF-6013] Make node alias a transient field URL: https://github.com/apache/karaf-cellar/pull/58 Hazelcast relies on serialization to store object, thus changing a node alias will make it unable to find by HazelcastGroupManager in map named "org.apache.karaf.cellar.groups" if the field is not transient. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Setting node alias breaks synchonization > > > Key: KARAF-6013 > URL: https://issues.apache.org/jira/browse/KARAF-6013 > Project: Karaf > Issue Type: Bug > Components: cellar >Reporter: Nicolas Dutertry >Priority: Major > > I have activated config.listener in org.apache.karaf.cellar.node.cfg. > When an alias is given to the node with the commande node-alias, the local > configuration changes are not transmitted to the cluster anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6003) IllegalStateException: Need active coordination - cannot use JPA and Jasypt
[
https://issues.apache.org/jira/browse/KARAF-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691704#comment-16691704
]
Grzegorz Grzybek commented on KARAF-6003:
-
ARIES-1858 fixes some compatibility issue and the fix will be available in
blueprint.core 1.10.1 and blueprint.cm 1.3.1.
> IllegalStateException: Need active coordination - cannot use JPA and Jasypt
> ---
>
> Key: KARAF-6003
> URL: https://issues.apache.org/jira/browse/KARAF-6003
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.1
>Reporter: Marek Łuniewski
>Assignee: Jean-Baptiste Onofré
>Priority: Blocker
> Fix For: 4.2.2
>
>
> In version 4.2.1 one cannot use JPA because it causes
> java.lang.IllegalStateException: Need active coordination. After my
> investigation I have found that it is caused because proxy service is not
> created properly. When someone use JPA in the same bundle, as in Karaf tests,
> it works fine. But problem occurs when using osgi service and osgi reference.
> Downgrading to version 4.1.5 of Karaf results in no possibility of using
> Jasypt (to protect passwords) [using:
> org.jasypt.encryption.pbe.StandardPBEStringEncryptor]. It does not decrypt
> passwords having marks ENC(...).
> I found that upgrading Blueprint fixes problem, so that JPA and Jasypt works
> perfectly. I know that sometime ago ticket on Camel blocked Blueprint
> upgrade. It was: https://issues.apache.org/jira/browse/CAMEL-12570. Currently
> this ticket is closed.
> Patch (for current code, which is version 4.2.1) is:
> {code:java}
> diff --git a/pom.xml b/pom.xml
> index 3d314da48c..f049b7ff86 100644
> --- a/pom.xml
> +++ b/pom.xml
> @@ -218,10 +218,11 @@
> 1.0.0
>
> 1.0.0
> 1.0.1
> - 1.9.0
> + 1.10.0
>
> 1.0.0
> - 1.2.0
> - 1.0.1
> + 1.3.0
> + 1.1.1
> +
> 1.0.1
>
> 0.6.0
>
> 0.4.0
> 1.1.5
> {code}
> and
> {code:java}
> diff --git a/assemblies/features/standard/src/main/feature/feature.xml
> b/assemblies/features/standard/src/main/feature/feature.xml
> index d19b87eb00..1813b2a0a5 100644
> --- a/assemblies/features/standard/src/main/feature/feature.xml
> +++ b/assemblies/features/standard/src/main/feature/feature.xml
> @@ -1429,7 +1429,7 @@ org.apache.felix.eventadmin.AddSubject=true
> blueprint inside web-bundle containers" version="${project.version}">
> war
> aries-blueprint
> -
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.web.version}
> +
> mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.webosgi/${aries.blueprint.webosgi.version}
>
>
> version="${pax.url.version}">
> {code}
> Hope it helps.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-6013) Setting node alias breaks synchonization
Nicolas Dutertry created KARAF-6013: --- Summary: Setting node alias breaks synchonization Key: KARAF-6013 URL: https://issues.apache.org/jira/browse/KARAF-6013 Project: Karaf Issue Type: Bug Components: cellar Reporter: Nicolas Dutertry I have activated config.listener in org.apache.karaf.cellar.node.cfg. When an alias is given to the node with the commande node-alias, the local configuration changes are not transmitted to the cluster anymore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
