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

[OSE] [6.2] Removing a CXF profile keeps a broken record in API registry

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • jboss-fuse-6.2
    • jboss-fuse-6.2
    • Fuse on Openshift
    • None
    • % %
    • Hide
      1. create Fuse OSE container (fuse)
      2. create 2 additional OSE fuse containers from hawtio (fuse1, fuse2)
      3. deploy example-camel-cxf on fuse1 and fuse2
      4. notice the URLs in the API registry are OK
      5. remove example-camel-cxf profile from fuse1
      6. notice the URL in the API registry for fuse1 still exists and has changed ports from a PROXY port to the original internal port (to 9090 in my case)
      Show
      create Fuse OSE container (fuse) create 2 additional OSE fuse containers from hawtio (fuse1, fuse2) deploy example-camel-cxf on fuse1 and fuse2 notice the URLs in the API registry are OK remove example-camel-cxf profile from fuse1 notice the URL in the API registry for fuse1 still exists and has changed ports from a PROXY port to the original internal port (to 9090 in my case)

      Deploying and undeploying a CXF application (such as example-camel-cxf from a container) on OSE leaves a broken record in the zookeeper API registry.

            ggrzybek Grzegorz Grzybek
            maschmid@redhat.com Marek Schmidt
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: