4 Replies Latest reply on Dec 19, 2012 4:05 AM by komododave

Fuse Fabric 7.1.0-041 - Adding process-manager feature => exception

komododave Dec 18, 2012 1:12 PM

EDIT: Ignore this post for now please, I'd delete it were that an option. I just tried grabbing the fmc pinger example feature and received the same exception so something more fundamental is wrong. I've specified maven proxies for the fabric agent and maven proxy, and then refreshed the pax mvn bundle but still artifacts can't be resolved. Will investigate further.

After creating a new single ensemble node (root) as my fabric, I created a profile test-procman with parent default. Through FMC I added to this the process-manager feature.

Next I created a child container servlets under root. I applied to this the test-procman profile.

Provisioning fails almost immediately with the following exception. Any suggestions how to overcome this?

Provision Exception Trace: java.lang.IllegalArgumentException: Unable to find feature http/2.3.0.fuse-71-041

at org.fusesource.fabric.agent.DeploymentAgent.addFeatures(DeploymentAgent.java:501)

at org.fusesource.fabric.agent.DeploymentAgent.addFeatures(DeploymentAgent.java:491)

at org.fusesource.fabric.agent.DeploymentAgent.updateDeployment(DeploymentAgent.java:529)

at org.fusesource.fabric.agent.DeploymentAgent.doUpdate(DeploymentAgent.java:428)

at org.fusesource.fabric.agent.DeploymentAgent$1.run(DeploymentAgent.java:238)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:662)

1. Re: Fuse Fabric 7.1.0-041 - Adding process-manager feature => exception

stlewis Dec 18, 2012 1:19 PM (in response to komododave)

Should be a matter of making your profile a child of either the "fabric" profile or the "karaf" profile, think the "karaf" profile should do it.
Actions
2. Re: Fuse Fabric 7.1.0-041 - Adding process-manager feature => exception

komododave Dec 18, 2012 1:39 PM (in response to stlewis)

Hi Stan - thanks for your response, I'm a little confused though.

So are you saying any custom profile needs to extend karaf now instead of default in order to resolve mvn URIs? Is this explained anywhere, or is it the new modus operandi?

Or is your response specifically relating to process-manager - i.e. in order to add that feature in particular it must be applied to a profile whose parent is karaf?
Actions
3. Re: Fuse Fabric 7.1.0-041 - Adding process-manager feature => exception

stlewis Dec 18, 2012 1:41 PM (in response to komododave)

No, if I recall correctly "karaf" has the features repositories defined that contain that missing feature, while default doesn't. You'll find that "karaf" ultimately inherits from "default" anyway, at least out of the box it does.
Actions
4. Re: Fuse Fabric 7.1.0-041 - Adding process-manager feature => exception

komododave Dec 19, 2012 4:05 AM (in response to stlewis)

Thanks for the info, Stan.

I saw process-manager in the features list in FMC though. I believe this is because the repository containing it is in our hosted Nexus proxy, so actually my problem lies elsewhere. I'd like to know whether what I'm saying makes sense - I'll try to resolve the problem on my own, but just want to have a clear understanding if you could acknowledge the above?
Actions

Go to original post