Ondra Chaloupka created JBTM-2815:
-------------------------------------
Summary: Transaction manager runtime configuration is not enriched with
system properties from standalone xml
Key: JBTM-2815
URL:
https://issues.jboss.org/browse/JBTM-2815
Project: JBoss Transaction Manager
Issue Type: Bug
Reporter: Ondra Chaloupka
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)