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

Although profile-import and profile-refresh download the latest snapshot, it takes more than 4 min

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2.1
    • Fabric8 v1
    • None
    • % %
    • Hide
      1. Clean install and start fuse
      2. Install and Start fabric
        patch:add file:///root/Downloads/jboss-fuse-full-6.2.1.redhat-090.zip
        patch:install jboss-fuse-full-6.2.1.redhat-090
        fabric:create --clean --zookeeper-password admin --zookeeper-data-dir zkdata --wait-for-provisioning
        
      3. shutdown
      4. edit bin/setenv
        export EXTRA_JAVA_OPTS="-Daether.updateCheckManager.sessionState=bypass"
        
      5. bootup
      6. In the different machine, deploy bundle using fabric8-maven-plugin
        mvn clean install
        mvn fabric8:deploy
        // profile name, sample_profile, is specified in the pom.xml
        
      7. Create child container
        fabric:container-create-child --profile sample_profile root child
        
      8. check jvm options for root container
        jinfo $JAVA_PID | grep bypass 
        
      9. Check the child container's log from deployed bundle
      10. Fix the application(fix the output message) and do mvn clean install and mvn fabric8:deploy. The artifact ID for the bundle is still same
        <log message="Hello again 2. The message contains ${body}"/>
        
        mvn clean install
        mvn fabric8:deploy
        
      11. Check the child container's log from deployed bundle
      Show
      Clean install and start fuse Install and Start fabric patch:add file: ///root/Downloads/jboss-fuse-full-6.2.1.redhat-090.zip patch:install jboss-fuse-full-6.2.1.redhat-090 fabric:create --clean --zookeeper-password admin --zookeeper-data-dir zkdata --wait- for -provisioning shutdown edit bin/setenv export EXTRA_JAVA_OPTS= "-Daether.updateCheckManager.sessionState=bypass" bootup In the different machine, deploy bundle using fabric8-maven-plugin mvn clean install mvn fabric8:deploy // profile name, sample_profile, is specified in the pom.xml Create child container fabric:container-create-child --profile sample_profile root child check jvm options for root container jinfo $JAVA_PID | grep bypass Check the child container's log from deployed bundle Fix the application(fix the output message) and do mvn clean install and mvn fabric8:deploy . The artifact ID for the bundle is still same <log message= "Hello again 2. The message contains ${body}" /> mvn clean install mvn fabric8:deploy Check the child container's log from deployed bundle

      This bug is found in ENTESB-4012
      Although profile-import and profile-refresh download the latest snapshot, it takes more than 4 min

              pantinor@redhat.com Paolo Antinori
              rhn-support-hfuruich Hisao Furuichi
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: