You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by asookazian2 <as...@gmail.com> on 2014/07/21 21:54:42 UTC

Re: Cellar for karaf 3.0.1 active/active and failover clustering

I just tried to setup a brand new 2 node horz cluster on 2 windows VMs.  Both
nodes are joining the default group/cluster.

However, when I run our installer script with both karaf nodes (3.0.1)
running, the bundles install successfully on node A but not on node B. 
These are the actual bundles for our custom software, not the previous web
service example I had deployed.  

Here are the exceptions for node B.  Please note that we have
directories/files in the system directory (such as features XML which have
the bundle install info) that are not being sync'd with the node B.

This is how I installed cellar on both nodes:

karaf@root()> feature:repo-add
mvn:org.apache.karaf.cellar/apache-karaf-cellar/3.0.0/xml/features
karaf@root()> feature:install cellar

20140721 12:30:56.860 [INFO ]
hz._hzInstance_1_cellar.global-operation.thread-1 | 241:com.hazelcast |
com.hazelcast.cluster.ClusterService | [192.168.172.219]:5701 [cellar]
[3.2.3]

Members [2] {
        Member [192.a.b.c]:5701
        Member [192.a.b.d]:5701 this
}

20140721 12:30:58.389 [INFO ] hz._hzInstance_1_cellar.cached.thread-18 |
241:com.hazelcast | com.hazelcast.core.LifecycleService |
[192.168.172.219]:5701 [cellar] [3.2.3] Address[192.168.172.219]:5701 is
MERGED
20140721 12:39:57.560 [ERROR] pool-14-thread-71 |
248:org.apache.karaf.cellar.features |
org.apache.karaf.cellar.features.RepositoryEventHandler | CELLAR FEATURES:
failed to add/remove repository URL
mvn:com.nextgate.am/ngam-features/9.0.0-SNAPSHOT/xml/features
java.lang.NullPointerException
        at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[248:org.apache.karaf.cellar.features:3.0.0]
        at
org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[248:org.apache.karaf.cellar.features:3.0.0]
        at Proxy816e4134_52be_45a8_9a8d_f2b4b7585c2a.handle(Unknown
Source)[:]
        at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
Source)[:]
        at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
20140721 12:39:58.496 [WARN ] pool-14-thread-71 | 5:org.ops4j.pax.url.mvn |
org.ops4j.pax.url.maven.commons.MavenRepositoryURL | Repository spec
https://repository.apache.org/content/repositories/orgapachekaraf-1006/ does
not contain an identifier. This is deprecated & discouraged & just evil.
20140721 12:39:59.729 [WARN ] pool-14-thread-71 | 5:org.ops4j.pax.url.mvn |
org.ops4j.pax.url.mvn.internal.AetherBasedResolver | Error resolving
artifactcom.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT:Could not find
artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in defaultlocal
(file:/C:/sw/ngs/current/ngs/data/repo/)
org.sonatype.aether.resolution.ArtifactResolutionException: Could not find
artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in defaultlocal
(file:/C:/sw/ngs/current/ngs/data/repo/)
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:250)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:239)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:223)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:122)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:524)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:165)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:77)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:878)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.<init>(BundleArchive.java:153)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:277)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.Felix.installBundle(Felix.java:2866)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.karaf.cellar.bundle.BundleSupport.installBundleFromLocation(BundleSupport.java:42)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at
org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:80)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at
org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:34)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at Proxy9bb3c0d2_751d_4de2_8365_07ee95ece489.handle(Unknown
Source)[:]
        at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
Source)[:]
        at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not
find artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in
defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:947)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)[5:org.ops4j.pax.url.mvn:1.6.0]
        ... 3 more
20140721 12:39:59.729 [ERROR] pool-14-thread-71 |
247:org.apache.karaf.cellar.bundle |
org.apache.karaf.cellar.bundle.BundleEventHandler | CELLAR BUNDLE: failed to
install bundle [com.nextgate.am.ngam-webservice,
9.0.0.SNAPSHOT]/org.osgi.framework.BundleException: Unable to cache bundle:
mvn:com.nextgate.am/ngam-webservice/9.0.0-SNAPSHOT.
20140721 12:40:00.337 [WARN ] pool-14-thread-72 | 5:org.ops4j.pax.url.mvn |
org.ops4j.pax.url.mvn.internal.AetherBasedResolver | Error resolving
artifactcom.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT:Could not
find artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
org.sonatype.aether.resolution.ArtifactResolutionException: Could not find
artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:250)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:239)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:223)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:122)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:524)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:165)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:77)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:878)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleArchive.<init>(BundleArchive.java:153)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:277)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.Felix.installBundle(Felix.java:2866)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138)[org.apache.felix.framework-4.2.1.jar:]
        at
org.apache.karaf.cellar.bundle.BundleSupport.installBundleFromLocation(BundleSupport.java:42)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at
org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:80)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at
org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:34)[247:org.apache.karaf.cellar.bundle:3.0.0]
        at Proxy9bb3c0d2_751d_4de2_8365_07ee95ece489.handle(Unknown
Source)[:]
        at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
Source)[:]
        at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not
find artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:947)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)[5:org.ops4j.pax.url.mvn:1.6.0]
        at
org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)[5:org.ops4j.pax.url.mvn:1.6.0]
        ... 3 more
20140721 12:40:00.337 [ERROR] pool-14-thread-72 |
247:org.apache.karaf.cellar.bundle |
org.apache.karaf.cellar.bundle.BundleEventHandler | CELLAR BUNDLE: failed to
install bundle [com.nextgate.am.deploys.ngam-manager,
9.0.0.SNAPSHOT]/org.osgi.framework.BundleException: Unable to cache bundle:
mvn:com.nextgate.am.deploys/ngam-manager/9.0.0-SNAPSHOT/war.
20140721 12:40:00.665 [ERROR] pool-14-thread-72 |
248:org.apache.karaf.cellar.features |
org.apache.karaf.cellar.features.FeaturesSynchronizer | CELLAR FEATURES:
failed to handle cluster feature event
java.lang.Exception: No feature named 'ngam' with version '9.0.0-SNAPSHOT'
available
        at
org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:359)[24:org.apache.karaf.features.core:3.0.1]
        at Proxyf201eba7_6d8c_413b_aa34_2075952c9960.installFeature(Unknown
Source)[:]
        at Proxyb20d3a85_01a5_4e00_9550_a67b2332c5b8.installFeature(Unknown
Source)[:]
        at
org.apache.karaf.cellar.features.FeaturesEventHandler.handle(FeaturesEventHandler.java:97)[248:org.apache.karaf.cellar.features:3.0.0]
        at
org.apache.karaf.cellar.features.FeaturesEventHandler.handle(FeaturesEventHandler.java:33)[248:org.apache.karaf.cellar.features:3.0.0]
        at Proxy816e4134_52be_45a8_9a8d_f2b4b7585c2a.handle(Unknown
Source)[:]
        at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
Source)[:]
        at
org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]





--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034347.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by ch...@kiffer.ltd.uk.
Don't let's forget <http://www.osgi.org/Download/HomePage> where you can
download the original service specifications, which are both very clear
about how the service has to behave and completely abstract concerning the
means employed. And as Achim points out, there are a lot of tutorials etc.
about this fundamental OSGi service.

ConfigurationAdmin defines the behaviour of a service which accepts
parcels of name-value pairs (called "configurations") and delivers them to
the destination identified by a PID. The destination must register with
the framework as a ManagedService with that PID; most often the
destination will be a service object (hence the name), so this is a way to
dynamically configure services. One of the features of Cellar is that it
will propagate a configuration created in one node to all the other nodes.

The /etc/config.properties file defines default values for some "framework
properties" which will be set up when Karaf is launched. It provides a way
to statically define properties which are then available to all bundles
via the BundleContext - see
<http://www.osgi.org/javadoc/r4v43/core/org/osgi/framework/BundleContext.html#getProperty%28java.lang.String%29>.

Basically the only thing that ConfigurationAdmin and etc/config.properties
have in common is the six letters 'c,o,n,f,i,g' - alas some of the
most-used letters in IT, and the cause of many confusions. But expecting
ConfigurationAdmin to propagate /etc/config.properties files is a bit like
expecting Santa to distribute chocolate ants because he has 'a,n,t' in his
name ...

Greetings,

Chris Gray


> A quick google gave me this result [1], and the first entry is for
> configuration admin service [2].
> As the Fileinstaller does take care of parsing the cfg files and therefore
> transfering those to the config admin service, find the documentation for
> the FileInstaller at [3]
>
>
>
> regards, Achim
>
> [1] -
> https://www.google.de/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=felix%20config%20admin%20service
> [2] -
> http://felix.apache.org/documentation/subprojects/apache-felix-config-admin.html
> [3] - http://felix.apache.org/site/apache-felix-file-install.html
>
>
>
> 2014-07-22 18:12 GMT+02:00 asookazian2 <as...@gmail.com>:
>
>> Where is the documentation on how the ConfigAdmin works???
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034378.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>



Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Achim Nierbeck <bc...@googlemail.com>.
A quick google gave me this result [1], and the first entry is for
configuration admin service [2].
As the Fileinstaller does take care of parsing the cfg files and therefore
transfering those to the config admin service, find the documentation for
the FileInstaller at [3]



regards, Achim

[1] -
https://www.google.de/webhp?sourceid=chrome-instant&ion=1&espv=2&es_th=1&ie=UTF-8#q=felix%20config%20admin%20service
[2] -
http://felix.apache.org/documentation/subprojects/apache-felix-config-admin.html
[3] - http://felix.apache.org/site/apache-felix-file-install.html



2014-07-22 18:12 GMT+02:00 asookazian2 <as...@gmail.com>:

> Where is the documentation on how the ConfigAdmin works???
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034378.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>



-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>

Software Architect / Project Manager / Scrum Master

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
Where is the documentation on how the ConfigAdmin works???



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034378.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
Thanks for replying.  There is only one reference to "configadmin" in the
cellar docs:

http://karaf.apache.org/manual/cellar/latest/user-guide/index.html

How would I modify the etc/config.properties to be able to sync
etc/a/b/c/foo.properties?

Also, it would be nice if the Cellar docs was in one HTML page if possible.



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034377.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Ouah, too much question in a row ;)

It's the file which are replicated, it's the ConfigAdmin: so a comment 
won't be replicated, just a key/value change.

Regards
JB

On 07/21/2014 11:40 PM, asookazian2 wrote:
> In fact I made a change to etc/org.ops4j.pax.url.mvn.cfg and it did not
> replicate either (only a comment I tried).
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034356.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
In fact I made a change to etc/org.ops4j.pax.url.mvn.cfg and it did not
replicate either (only a comment I tried).



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034356.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
No, again Cellar doesn't mind about the files and folders, it replicated 
ConfigAdmin. etc/a/b/c won't be pulled to ConfigAdmin (or you have to 
modify etc/config.properties).

Regards
JB

On 07/21/2014 11:37 PM, asookazian2 wrote:
> If I make a change to a file in /etc/a/b/c dir, will it replicate to the same
> dir structure in the other nodes?  I just tried that with both nodes running
> and it doesn't seem to do anything...
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034355.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
If I make a change to a file in /etc/a/b/c dir, will it replicate to the same
dir structure in the other nodes?  I just tried that with both nodes running
and it doesn't seem to do anything...



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034355.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I think you misunderstood me.

It's replicate repo (if you talk about features:repo-add).

Again, did you read the Cellar user guide ?

Regards
JB

On 07/21/2014 10:51 PM, asookazian2 wrote:
> Is it possible to replicate data/repo?  We are considering running
> feature:repo-add and install bundles on each node which defeats the purpose
> of Cellar which replicates bundles, features and configs...
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034354.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
Is it possible to replicate data/repo?  We are considering running
feature:repo-add and install bundles on each node which defeats the purpose
of Cellar which replicates bundles, features and configs...



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034354.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
If the bundles/features are in those repositories, it will work.

Regards
JB

On 07/21/2014 10:36 PM, asookazian2 wrote:
> I don't believe so, here is our config:
>
> org.ops4j.pax.url.mvn.repositories =
> http://repo1.maven.org/maven2@id=central,
> http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release,
> http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external,
> file:C:\\sw\\ngs\\current\\ngs/system@id=system.repository,
> file:C:\\sw\\ngs\\current\\ngs\\data/kar@id=kar.repository@multi,
> https://repository.apache.org/content/repositories/orgapachekaraf-1006/
>
> I was able to replicate bundle installs with the web service POC project I
> was working on recently.  Round robin from httpd and failover worked as well
> prior.
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034353.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
I don't believe so, here is our config:

org.ops4j.pax.url.mvn.repositories =
http://repo1.maven.org/maven2@id=central,
http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release,
http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external,
file:C:\\sw\\ngs\\current\\ngs/system@id=system.repository,
file:C:\\sw\\ngs\\current\\ngs\\data/kar@id=kar.repository@multi,
https://repository.apache.org/content/repositories/orgapachekaraf-1006/

I was able to replicate bundle installs with the web service POC project I
was working on recently.  Round robin from httpd and failover worked as well
prior.



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034353.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
On Windows, I can't write this cmd properly for it to work:

cave:repository-create cave-repo -l C:/sw/ngs/current/ngs/data/repo data
Error executing command cave:repository-create: too many arguments specified

Example from blog: 

cave:create-repository -l /home/jbonofre/.m2/repository m2



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034352.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
No, it's not what I meant.

Cellar just broadcast the instructions to do.

So, feature:repo-add on one node will be done on the other node.
To do that, the nodes have to share a repository (Cave is not necessary).

So, all nodes have to share the same Maven repository (as defined in 
etc/org.ops4j.pax.url.mvn.cfg).

Is it the case ?

Forget about Cave for now.

Regards
JB

On 07/21/2014 10:15 PM, asookazian2 wrote:
> Populate from an external repository
> If you have a bunch of artifacts to upload, it’s not very efficient to use
> the cave:upload-artifact command.
> The cave:populate-repository command allows you to upload a set of artifacts
> from an “external” repository:
>
> karaf@root> cave:populate-repository cave-repo
> file:/home/jbonofre/.m2/repository
> In this example, Cave will browse the file:/home/jbonofre/.m2/repository
> location, looking for OSGi bundles, and will copy the artifacts in your Cave
> Repository storage location.
>
> http://blog.nanthrax.net/2011/08/apache-karaf-cave-preview/
> <http://blog.nanthrax.net/2011/08/apache-karaf-cave-preview/>
>
> Do I need to install Cave on all the nodes?  and then do I need to do the
> above (cave:populate-repository) for both nodes or just one?
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034350.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
Populate from an external repository
If you have a bunch of artifacts to upload, it’s not very efficient to use
the cave:upload-artifact command.
The cave:populate-repository command allows you to upload a set of artifacts
from an “external” repository:

karaf@root> cave:populate-repository cave-repo
file:/home/jbonofre/.m2/repository
In this example, Cave will browse the file:/home/jbonofre/.m2/repository
location, looking for OSGi bundles, and will copy the artifacts in your Cave
Repository storage location.

http://blog.nanthrax.net/2011/08/apache-karaf-cave-preview/
<http://blog.nanthrax.net/2011/08/apache-karaf-cave-preview/>  

Do I need to install Cave on all the nodes?  and then do I need to do the
above (cave:populate-repository) for both nodes or just one?



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034350.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by asookazian2 <as...@gmail.com>.
No, they are using data/repo.

http://karaf.apache.org/index/subprojects/cave/download/karaf-cave-3.0.0-release.html

Do I need to use Karaf Cave?  We probably cannot setup/install/config
Artifactory at the client sites.  Please advise link to the Cave docs.  thx.



--
View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034349.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Cellar for karaf 3.0.1 active/active and failover clustering

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi

the nodes share the same repository ?

Regards
JB

On 07/21/2014 09:54 PM, asookazian2 wrote:
> I just tried to setup a brand new 2 node horz cluster on 2 windows VMs.  Both
> nodes are joining the default group/cluster.
>
> However, when I run our installer script with both karaf nodes (3.0.1)
> running, the bundles install successfully on node A but not on node B.
> These are the actual bundles for our custom software, not the previous web
> service example I had deployed.
>
> Here are the exceptions for node B.  Please note that we have
> directories/files in the system directory (such as features XML which have
> the bundle install info) that are not being sync'd with the node B.
>
> This is how I installed cellar on both nodes:
>
> karaf@root()> feature:repo-add
> mvn:org.apache.karaf.cellar/apache-karaf-cellar/3.0.0/xml/features
> karaf@root()> feature:install cellar
>
> 20140721 12:30:56.860 [INFO ]
> hz._hzInstance_1_cellar.global-operation.thread-1 | 241:com.hazelcast |
> com.hazelcast.cluster.ClusterService | [192.168.172.219]:5701 [cellar]
> [3.2.3]
>
> Members [2] {
>          Member [192.a.b.c]:5701
>          Member [192.a.b.d]:5701 this
> }
>
> 20140721 12:30:58.389 [INFO ] hz._hzInstance_1_cellar.cached.thread-18 |
> 241:com.hazelcast | com.hazelcast.core.LifecycleService |
> [192.168.172.219]:5701 [cellar] [3.2.3] Address[192.168.172.219]:5701 is
> MERGED
> 20140721 12:39:57.560 [ERROR] pool-14-thread-71 |
> 248:org.apache.karaf.cellar.features |
> org.apache.karaf.cellar.features.RepositoryEventHandler | CELLAR FEATURES:
> failed to add/remove repository URL
> mvn:com.nextgate.am/ngam-features/9.0.0-SNAPSHOT/xml/features
> java.lang.NullPointerException
>          at
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:80)[248:org.apache.karaf.cellar.features:3.0.0]
>          at
> org.apache.karaf.cellar.features.RepositoryEventHandler.handle(RepositoryEventHandler.java:29)[248:org.apache.karaf.cellar.features:3.0.0]
>          at Proxy816e4134_52be_45a8_9a8d_f2b4b7585c2a.handle(Unknown
> Source)[:]
>          at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
> Source)[:]
>          at
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
>          at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
>          at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
>          at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
> 20140721 12:39:58.496 [WARN ] pool-14-thread-71 | 5:org.ops4j.pax.url.mvn |
> org.ops4j.pax.url.maven.commons.MavenRepositoryURL | Repository spec
> https://repository.apache.org/content/repositories/orgapachekaraf-1006/ does
> not contain an identifier. This is deprecated & discouraged & just evil.
> 20140721 12:39:59.729 [WARN ] pool-14-thread-71 | 5:org.ops4j.pax.url.mvn |
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver | Error resolving
> artifactcom.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT:Could not find
> artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in defaultlocal
> (file:/C:/sw/ngs/current/ngs/data/repo/)
> org.sonatype.aether.resolution.ArtifactResolutionException: Could not find
> artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in defaultlocal
> (file:/C:/sw/ngs/current/ngs/data/repo/)
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:250)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:239)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:223)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:122)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:524)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:165)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:77)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:878)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.<init>(BundleArchive.java:153)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:277)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.Felix.installBundle(Felix.java:2866)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.karaf.cellar.bundle.BundleSupport.installBundleFromLocation(BundleSupport.java:42)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at
> org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:80)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at
> org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:34)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at Proxy9bb3c0d2_751d_4de2_8365_07ee95ece489.handle(Unknown
> Source)[:]
>          at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
> Source)[:]
>          at
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
>          at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
>          at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
>          at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not
> find artifact com.nextgate.am:ngam-webservice:jar:9.0.0-SNAPSHOT in
> defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:947)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)[5:org.ops4j.pax.url.mvn:1.6.0]
>          ... 3 more
> 20140721 12:39:59.729 [ERROR] pool-14-thread-71 |
> 247:org.apache.karaf.cellar.bundle |
> org.apache.karaf.cellar.bundle.BundleEventHandler | CELLAR BUNDLE: failed to
> install bundle [com.nextgate.am.ngam-webservice,
> 9.0.0.SNAPSHOT]/org.osgi.framework.BundleException: Unable to cache bundle:
> mvn:com.nextgate.am/ngam-webservice/9.0.0-SNAPSHOT.
> 20140721 12:40:00.337 [WARN ] pool-14-thread-72 | 5:org.ops4j.pax.url.mvn |
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver | Error resolving
> artifactcom.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT:Could not
> find artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
> defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
> org.sonatype.aether.resolution.ArtifactResolutionException: Could not find
> artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
> defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:250)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolveFile(AetherBasedResolver.java:239)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:223)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:122)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.apache.felix.framework.util.SecureAction.getURLConnectionInputStream(SecureAction.java:524)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:165)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:77)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:878)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleArchive.<init>(BundleArchive.java:153)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.cache.BundleCache.create(BundleCache.java:277)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.Felix.installBundle(Felix.java:2866)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:138)[org.apache.felix.framework-4.2.1.jar:]
>          at
> org.apache.karaf.cellar.bundle.BundleSupport.installBundleFromLocation(BundleSupport.java:42)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at
> org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:80)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at
> org.apache.karaf.cellar.bundle.BundleEventHandler.handle(BundleEventHandler.java:34)[247:org.apache.karaf.cellar.bundle:3.0.0]
>          at Proxy9bb3c0d2_751d_4de2_8365_07ee95ece489.handle(Unknown
> Source)[:]
>          at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
> Source)[:]
>          at
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
>          at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
>          at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
>          at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
> Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not
> find artifact com.nextgate.am.deploys:ngam-manager:war:9.0.0-SNAPSHOT in
> defaultlocal (file:/C:/sw/ngs/current/ngs/data/repo/)
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:947)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$4.wrap(WagonRepositoryConnector.java:941)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.connector.wagon.WagonRepositoryConnector$GetTask.run(WagonRepositoryConnector.java:669)[5:org.ops4j.pax.url.mvn:1.6.0]
>          at
> org.sonatype.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:60)[5:org.ops4j.pax.url.mvn:1.6.0]
>          ... 3 more
> 20140721 12:40:00.337 [ERROR] pool-14-thread-72 |
> 247:org.apache.karaf.cellar.bundle |
> org.apache.karaf.cellar.bundle.BundleEventHandler | CELLAR BUNDLE: failed to
> install bundle [com.nextgate.am.deploys.ngam-manager,
> 9.0.0.SNAPSHOT]/org.osgi.framework.BundleException: Unable to cache bundle:
> mvn:com.nextgate.am.deploys/ngam-manager/9.0.0-SNAPSHOT/war.
> 20140721 12:40:00.665 [ERROR] pool-14-thread-72 |
> 248:org.apache.karaf.cellar.features |
> org.apache.karaf.cellar.features.FeaturesSynchronizer | CELLAR FEATURES:
> failed to handle cluster feature event
> java.lang.Exception: No feature named 'ngam' with version '9.0.0-SNAPSHOT'
> available
>          at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:359)[24:org.apache.karaf.features.core:3.0.1]
>          at Proxyf201eba7_6d8c_413b_aa34_2075952c9960.installFeature(Unknown
> Source)[:]
>          at Proxyb20d3a85_01a5_4e00_9550_a67b2332c5b8.installFeature(Unknown
> Source)[:]
>          at
> org.apache.karaf.cellar.features.FeaturesEventHandler.handle(FeaturesEventHandler.java:97)[248:org.apache.karaf.cellar.features:3.0.0]
>          at
> org.apache.karaf.cellar.features.FeaturesEventHandler.handle(FeaturesEventHandler.java:33)[248:org.apache.karaf.cellar.features:3.0.0]
>          at Proxy816e4134_52be_45a8_9a8d_f2b4b7585c2a.handle(Unknown
> Source)[:]
>          at Proxyd66f100e_e050_4991_b1e8_898982523878.handle(Unknown
> Source)[:]
>          at
> org.apache.karaf.cellar.core.event.EventDispatchTask.run(EventDispatchTask.java:57)[242:org.apache.karaf.cellar.core:3.0.0]
>          at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_60]
>          at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_60]
>          at java.lang.Thread.run(Thread.java:745)[:1.7.0_60]
>
>
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Cellar-for-karaf-3-0-1-active-active-and-failover-clustering-tp4033204p4034347.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com