Uploaded image for project: 'WildFly WIP'
  1. WildFly WIP
  2. WFWIP-54

[JDBC HA] Artemis system properties override model configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • JMS
    • None
    • Hide 
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/57//artifact/jboss-eap.zip PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/

mvn clean test -Dtest=JdbcHAConfigTestCase#testConfiguringUsingSystemPropertiesHasPriorityBeforeConfiguration -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531466290-SNAPSHOT -DfailIfNoTests=false -Deap=7x | tee log
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ groovy -DEAP_ZIP_URL=https: //eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-messaging-testing-prepare/57//artifact/jboss-eap.zip PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=JdbcHAConfigTestCase#testConfiguringUsingSystemPropertiesHasPriorityBeforeConfiguration -Deap7.org.jboss.qa.hornetq.apps.clients.version=7.1531466290-SNAPSHOT -DfailIfNoTests= false -Deap=7x | tee log

      This issue is related to https://github.com/wildfly/wildfly/pull/11355.

      Based on the Analysis document [1] and because of backward compatibility, new JDBC HA configuration parameters can be configured in two ways. Using the system properties and using the management model. It was decided that values defined in management model has higher priority than values defined by system properties. However this rule is not applied.

      I found out that although integration code passes correct values to Artemis configuration, they are replaced by a method [2]. I think that integration code should unset the system properties so Artemis cannot read them.

      [1] https://github.com/wildfly/wildfly-proposals/pull/87/
      [2] https://github.com/rh-messaging/jboss-activemq-artemis/blob/1.5.5.jbossorg-012/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/ActiveMQServerImpl.java#L507

              jmesnil1@redhat.com Jeff Mesnil
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: