Why is my 'Available Features - Repository:' list empty?
komododave Nov 21, 2012 3:56 AMI've been trying to get this to work for the past few hours with no success.
After installing Fuse Fabric I entered the Fuse Fabric ESB command console via ..fabric/bin/fusefabric, which itself simply calls ..fabric/bin/karaf.
I then ran the fabric:create shell command to create an initial ensemble node named root as is the default.
We have a local network Nexus installation (Maven repo manager by Sonatype). For every original repository URL listed by the fabric agent and fabric maven proxy, a proxy repository has been created on Nexus.
I used
fabric:profile-edit --pid org.fusesource.fabric.agent/patch.repositories=... default
to set the fabric agent patch repository URLs for the default profile.
Likewise, I ran:
fabric:profile-edit --pid org.fusesource.fabric.agent/org.ops4j.pax.url.mvn.repositories=... default
to set the fabric agent feature/bundle repository URLs for the default profile.
Lastly, this command was used:
fabric:profile-edit --pid org.fusesource.fabric.maven/remoteRepositories=... fabric
to set the fabric maven proxy repository URLs for the fabric profile.
Following this the fabric agent has remote repo properties configured like so:
org.ops4j.pax.url.mvn.repositories=http\://maven/nexus/content/repositories/fusesource-m2,http\://maven/nexus/content/repositories/fusesource-nexus,http\://maven/nexus/content/repositories/fusesource-nexus-groups-ea,http\://maven/nexus/content/repositories/fusesource-nexus-public,http\://maven/nexus/content/repositories/springsource,http\://maven/nexus/content/repositories/springsource-external,http\://maven/nexus/content/repositories/scala-repo-releases,http\://maven/nexus/content/repositories/fusesource-features-releases,http\://maven/nexus/content/repositories/fusesource-features-snapshots
patch.repositories=http\://maven/nexus/content/repositories/fusesource-nexus,http\://maven/nexus/content/repositories/fusesource-nexus-groups-ea,http\://maven/nexus/content/repositories/fusesource-features-releases,http\://maven/nexus/content/repositories/fusesource-features-snapshots
These are all the Nexus proxies which have as remote URL the original repository locations, plus two additional repos for the top property which will contain our own releases and snapshots.
The fabric maven proxy has remote repo properties configured like so:
remoteRepositories=http\://maven/nexus/content/repositories/fusesource-m2,http\://maven/nexus/content/repositories/fusesource-nexus,http\://maven/nexus/content/repositories/fusesource-nexus-groups-ea,http\://maven/nexus/content/repositories/fusesource-nexus-public,http\://maven/nexus/content/repositories/springsource,http\://maven/nexus/content/repositories/springsource-external,http\://maven/nexus/content/repositories/scala-repo-releases,http\://maven/nexus/content/repositories/fusesource-features-releases,http\://maven/nexus/content/repositories/fusesource-features-snapshots
Fuse Management Console ("FMC") was installed on another Virtual IP ("VIP") on the same box. I chose Join for the root fabric. The SSH access had been tested manually already, and indeed the Join was successful.
Now the containers listed in FMC are Fuse Management Console and root.
After a few minutes the following error displayed for the default profile:
Error fetching features repository: URL mvn:org.fusesource.fabric/fuse-fabric/7.0.1.fuse-084/xml/features could not be resolved.
This profile has only the default feature repository defined, namely:
mvn:org.fusesource.fabric/fuse-fabric/7.0.1.fuse-084/xml/features
After running log:tail in the root ESB command console, I can see the following warnings:
2012-11-21 07:26:09,639 | WARN | -70-084-thread-2 | Activator | 18 - org.apache.karaf.diagnostic.common - 2.2.5.fuse-70-084 | Feature service is not present, Feature dump provider will be disabled
2012-11-21 07:26:09,704 | WARN | use-084-thread-2 | Activator | 97 - org.fusesource.fabric.fabric-commands - 7.0.1.fuse-084 | Feature service is not present, Feature / Repository completion will be disabled
Visiting the Features tab for default profile presents four installed features:
fabric-agent
karaf
fabric-jaas
fabric-core
Below these is the Available Features header, and just below that is the Repository: dropdown. This is empty when the page is refreshed, or else after a few minutes contains the lone feature repository specified earlier. It is in red and presents a red box containing the Error mentioned previously.
I tried uploading the fmc-pinger-example to our releases repository, then created the profiles described in that project's readme. I reconfigured the POM to deploy to our Nexus repo, and deployment of the artifacts was successful.
All three of the new profiles relating to this project also present an empty Repository: dropdown when selected in FMC.
However, if I try to create a new container in FMC that uses any of the new profiles, I can see the ping-features artifact has been successfully downloaded to the relevant container:
root@host:/home/my-user# find -regex '.ping.'
./containers/my-container/fuse-fabric-7.0.2.fuse-097/system/org/fusesource/examples/ping
./containers/my-container/fuse-fabric-7.0.2.fuse-097/system/org/fusesource/examples/ping/ping-features
./containers/my-container/fuse-fabric-7.0.2.fuse-097/system/org/fusesource/examples/ping/ping-features/1.0
./containers/my-container/fuse-fabric-7.0.2.fuse-097/system/org/fusesource/examples/ping/ping-features/1.0/ping-features-1.0-features.xml
I'd be tremendously grateful if someone could help me identify what's wrong. I've read every document available, watched all the webinars, yet seem to be having issues no-one else is experiencing.
The installation of both Fuse Fabric and Fuse Management Console was performed as prescribed, to the letter.
Would someone be kind enough to help me resolve this?