Transaction manager runtime configuration is not enriched with system properties from standalone xml ---------------------------------------------------------------------------------------------------- Key: WFLY-7785 URL: https://issues.jboss.org/browse/WFLY-7785 Project: WildFly Issue Type: Bug Components: Transactions Reporter: Ondra Chaloupka Assignee: Tom Jenkinson Priority: Critical I can see trouble and regression against behavior of 7.0.0.GA (and other prior 7.1.0 DR versions) where configuration of transaction manager which is defined inside of setting MBeans is not enriched from system properties which are defined as part of standalone .xm file. When system property is set in standalone xml file as {code} <system-properties> <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/> </system-properties> {code} then it's not propagated to {{RecoveryEnvironmentBean}} when container is started. I could see that method loading system properties at AbstractPropertiesFactory (https://github.com/jbosstm/narayana/blob/master/common/classes/com/arjuna...) does not provide those which are part of the container config. That worked with DR8 fine. I didn't go deeper if this is really issue of TM/integration or some change in container.