0 Replies Latest reply on Nov 22, 2013 4:33 PM by Vladimir Tomenko

    JBoss EAP 6.1 Management API: system property not seen after remove followed by add

    Vladimir Tomenko Newbie

      I have the following property in standalone.xml:

       

          <system-properties>

              <property name="foo" value="test1"/>

          </system-properties>

         

      Executing the following composite operation:

          {

          "operation" => "composite",

          "address" => [],

          "operation-headers" => {

          "rollback-on-runtime-failure" => "true",

          "allow-resource-service-restart" => "false"

          },

          "steps" => [

          {"operation" => "remove","address" => [("system-property" => "foo")]},

          {"operation" => "add","address" => [("system-property" => "foo")],"value" => "test2"},

          ]

          }

      results in response:

          {

              "outcome" => "success",

              "result" => {

                  "step-1" => {"outcome" => "success"},

                  "step-2" => {"outcome" => "success"}

              }

          }   

       

      However, neither my deployed application "sees" the system property "foo" (System.getProperty("foo")) nor it is in the result list of the following command executed in CLI:

          /core-service=platform-mbean/type=runtime:read-attribute(name=system-properties)

       

      Strangely, no "reload-required" is seen in response either.

      standalone.xml, however, contains the property with the correct value:

          <system-properties>

              <property name="foo" value="test2"/>

          </system-properties>

       

      Is there any way to update system property so that changes are effective without explicit reload?