In Fuse 6.1 Fabric profile communication goes via Maven Proxy

Solution Verified - Updated -


We setup a Maven proxy (see step 3 below) on the fabric profile, then used Maven to deploy a jar to the fabric Maven repository, eg:

mvn deploy:deploy-file -DartifactId=ojdbc6 -Dversion= -Dpackaging=jar -Dfile=ojdbc6.jar -DgeneratePom=true -Durl=http://admin:admin@

we found that fabric profile updates go through the proxy server. This is not a an acceptable situation because it means that the maven proxy is a single point of failure.

1. Setup a forward proxy using mod_proxy, ie:

<IfModule mod_proxy.c>

ProxyRequests On
ProxyVia On

AllowCONNECT 443

<Proxy *>
    Allow from all
2. Create a 3 node fabric ensemble
3. Add a fabric maven proxy to the 'fabric' profile:
fabric:profile-edit --pid io.fabric8.maven/ fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.port=9001 fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.protocol=http fabric
fabric:profile-edit --pid io.fabric8.maven/proxy.nonProxyHosts= fabric
4. Upload a file to the Fabric Maven repository, ie:
mvn deploy:deploy-file -DartifactId=ojdbc6 -Dversion= -Dpackaging=jar -Dfile=ojdbc6.jar -DgeneratePom=true -Durl=http://admin:admin@localhost:8181/maven/upload
5. On one of the ensemble servers, do a 'fabric:create-profile'
6. Tail the forward proxy logs and observe that traffic goes through the proxy server


Red Hat JBoss Fuse 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content