Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5557

Duplicating agent repository in maven proxy cause long artifact provision delay

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • jboss-fuse-6.3
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • Fabric8 v1
    • None
    • % %
    • Hide

      1. create 1 machine for root container and 1 for proxy server (squid)
      2. set up squid proxy server on second machine
      3. extract fuse, uncomment admin user in etc/users.properties, bin/start, fabric:create
      4. 

      profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.settings='file:/home/fuse/http-proxy-settings.xml' default
profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories='+http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-snapshots@snapshots' default

      5. 

      profile-create test1
profile-create test2
profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1-SNAPSHOT test1
profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.2-SNAPSHOT test2

      6. container-add-profile root test1
      7. artifact is provisioned immediately
      8. container-add-profile root test2
      9. artifact provisioning is hanging for about 10 minutes and then provisioned

      Show
      1. create 1 machine for root container and 1 for proxy server (squid) 2. set up squid proxy server on second machine 3. extract fuse, uncomment admin user in etc/users.properties, bin/start, fabric:create 4. profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.settings= 'file:/home/fuse/http-proxy-settings.xml' default profile-edit --pid io.fabric8.agent/org.ops4j.pax.url.mvn.repositories= '+http: //fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-snapshots@snapshots' default 5. profile-create test1 profile-create test2 profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.1-SNAPSHOT test1 profile-edit --bundle mvn:org.jboss.fuse.qa.test/useless-artifact/1.2-SNAPSHOT test2 6. container-add-profile root test1 7. artifact is provisioned immediately 8. container-add-profile root test2 9. artifact provisioning is hanging for about 10 minutes and then provisioned

      Usage of Fabric agent maven configuration specified in settings.xml file with HTTP proxy alongside with fabric agent PID 

      io.fabric8.agent/org.ops4j.pax.url.mvn.repositories = +http://fusewin.tpb.lab.eng.brq.redhat.com:8081/nexus/content/repositories/fuse-qe-snapshots@snapshots

      and fabric maven proxy default PID configuration

      io.fabric8.maven/io.fabric8.maven.repositories = ${profile:io.fabric8.agent/org.ops4j.pax.url.mvn.repositories}

      causes long artifact resolution delays.

      To hit the issue you need to set 4 settings:
      1. agent custom settings.xml file
      2. HTTP proxy set in settings.xml
      3. repository with + symbol in agents PID io.fabric8.agent/org.ops4j.pax.url.mvn.repositories
      4. Fabric maven proxy should have specified same repository as in 3. (by default there is substitution by variable from agent pid)

      Behaviour is same for snapshots or releases. Or you can edit one profile and adding or removing bundles with different versions.

      Removing HTTP proxy config from settings.xml or setting io.fabric8.maven/io.fabric8.maven.repositories to 

      ${profile:io.fabric8.agent/org.ops4j.pax.url.mvn.defaultRepositories}

      (agent and proxy does not share same repository) will fix the problem.

        1. 6.3.0.069.log
          195 kB
        2. 6.3.0.069.tdump
          96 kB
        3. http-proxy-settings.xml
          1 kB

            pantinor@redhat.com Paolo Antinori
            ecervena@redhat.com Emil Cervenan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: