2 Replies Latest reply on May 2, 2016 9:04 AM by Ashok Ramasamy

    Fabric Profile-edit --PID has no effect on the respective container

    Ashok Ramasamy Newbie

      I have a Camel context in Blueprint where PID property and default values are defined as follows.



        <cm:property-placeholder persistent-id="test.mq-producer" update-strategy="reload">



            <cm:property name="brokerURL" value="discovery:(fabric:notifMQGrp)"/>

            <cm:property name="topicName" value="TestNotification"/>






        <camelContext xmlns="http://camel.apache.org/schema/blueprint">


          <route id="timerToMQ">

            <from uri="timer:foo?period=5000"/>

            <log message="Calling direct-vm:producer"/>

            <to uri="direct-vm:producer"/>



          <route id="Producer">

            <from uri="direct-vm:producer"/>

              <setHeader headerName="createdBy">




                <simple>Notification Message from ACC ${date:now:yyyyMMddHHmmssSSS} </simple>


            <log message="Calling ActiveMQ ${body}"/>

            <to uri="activemq:topic:VirtualTopic.{{topicName}}"/>

            <log message="Topic Name is {{topicName}}"/>




      Camel-context is in a bundle and added in the profile which is assigned to the container. When the container is started, by default the topicName is mapped to TestNotification.


      I created a new version of the fabric and edited the profile to set the PID value of topicName as 'NewNotification', and upgrade the container with the new version. But, I don't see the changes are getting applied in the runtime camel-context. I still see the topicName as 'TestNotification' instead of 'NewNotification'.


      I do see the changed reflected in the profile.

      JBossFuse:admin@ESBRoot> fabric:profile-display test-mq-producer


      Profile id: test-mq-producer


      Version   : 1.3


              parents: mq-client-notifMQGrp jboss-fuse-full

      Containers: managedchild2

      Container settings


      Repositories :


      Features :


      Configuration details


      PID: test.mq-producer

        topicName NewNotification

      Other resources



      Could you please help to nail down the root cause of the issue?