Mule cannot configure JBOSS TM properties - defaultTimeout & txReaperTimeout

Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

The jbossts schema allows arbitrary properties to be configured on the transaction manager. This creates the expectation that the TM can be fully configured that way, but only two such properties (node id and object store directory) are honored. The rest are ignored.

It is impossible to set, for instance, default TX timeout via Mule configuration.

Issue Links

is a piece of

Bug - A problem which impairs or prevents the functions of the product. MULE-6554 Unable to configure all Core, Environment and ObjectStore JBoss TM Properties

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mike Schilling added a comment -

The simplest workaround is to specify the TM properties as system properties when running Mule. Another option is to create a file jbossts-properties.xml that contains the desired propertis, and place it in the user.home or user.dir directories, or as a resource in the classpath.

Because these propertied are stored as static variables in the JBoss TM classes, it is not possible for different Mule applications in the same Mule instance to have different values for them.

Show
Mike Schilling added a comment - The simplest workaround is to specify the TM properties as system properties when running Mule. Another option is to create a file jbossts-properties.xml that contains the desired propertis, and place it in the user.home or user.dir directories, or as a resource in the classpath. Because these propertied are stored as static variables in the JBoss TM classes, it is not possible for different Mule applications in the same Mule instance to have different values for them.
Hide
Permalink
Raphael Jammart added a comment -

I was not able to use the workaround by placing this file in the resource of the project but by placing it in the others directories the TM ran as expected.

I also patched the class org.mule.module.jboss.transaction.JBossArjunaTransactionManagerFactory like this to let the behavior consistent with the documentation:

if (properties.containsKey(PROPERTY_TX_TRANSACTION_TIMEOUT))

{ arjPropertyManager.getCoordinatorEnvironmentBean().setDefaultTimeout(new Integer(properties.get(PROPERTY_TX_TRANSACTION_TIMEOUT))); }

if (properties.containsKey(PROPERTY_TX_TRANSACTION_REAPER_TIMEOUT))

{ arjPropertyManager.getCoordinatorEnvironmentBean().setTxReaperTimeout(new Integer(properties.get(PROPERTY_TX_TRANSACTION_REAPER_TIMEOUT))); }

With theses few lines of codes, the old way to configure TM run as expected:
<jbossts:transaction-manager >
<property key="com.arjuna.ats.arjuna.coordinator.defaultTimeout" value="60" /><!-- this is in seconds -->
<property key="com.arjuna.ats.arjuna.coordinator.txReaperTimeout" value="108000"/><!-- this is in milliseconds -->
</jbossts:transaction-manager>

But I don't know if it is the good way.
Any comment is welcome.

Show
Raphael Jammart added a comment - I was not able to use the workaround by placing this file in the resource of the project but by placing it in the others directories the TM ran as expected. I also patched the class org.mule.module.jboss.transaction.JBossArjunaTransactionManagerFactory like this to let the behavior consistent with the documentation: if (properties.containsKey(PROPERTY_TX_TRANSACTION_TIMEOUT)) { arjPropertyManager.getCoordinatorEnvironmentBean().setDefaultTimeout(new Integer(properties.get(PROPERTY_TX_TRANSACTION_TIMEOUT))); } if (properties.containsKey(PROPERTY_TX_TRANSACTION_REAPER_TIMEOUT)) { arjPropertyManager.getCoordinatorEnvironmentBean().setTxReaperTimeout(new Integer(properties.get(PROPERTY_TX_TRANSACTION_REAPER_TIMEOUT))); } With theses few lines of codes, the old way to configure TM run as expected: <jbossts:transaction-manager > <property key="com.arjuna.ats.arjuna.coordinator.defaultTimeout" value="60" /><!-- this is in seconds --> <property key="com.arjuna.ats.arjuna.coordinator.txReaperTimeout" value="108000"/><!-- this is in milliseconds --> </jbossts:transaction-manager> But I don't know if it is the good way. Any comment is welcome.
Hide
Permalink
Christopher Mordue added a comment -

There are three environment beans used for configuring the transaction manager: CoreEnvironmentBean, CoordinatorEnvironmentBean and ObjectStoreEnvironmentBean. Because the beans contain an annotation with the property key, we should introspect each of them to get a list of possible properties. We can then iterate through each of these. If the property was provided, we can call the appropriate setter on the appropriate bean.

Show
Christopher Mordue added a comment - There are three environment beans used for configuring the transaction manager: CoreEnvironmentBean, CoordinatorEnvironmentBean and ObjectStoreEnvironmentBean. Because the beans contain an annotation with the property key, we should introspect each of them to get a list of possible properties. We can then iterate through each of these. If the property was provided, we can call the appropriate setter on the appropriate bean.
Hide
Permalink
Christopher Mordue added a comment -

Made com.arjuna.ats.arjuna.coordinator.defaultTimeout and com.arjuna.ats.arjuna.coordinator.txReaperTimeout exposed. This issue did not exist in 3.1.4. Added this fix in 3.2.4, 3.3.2, 3.4.

Show
Christopher Mordue added a comment - Made com.arjuna.ats.arjuna.coordinator.defaultTimeout and com.arjuna.ats.arjuna.coordinator.txReaperTimeout exposed. This issue did not exist in 3.1.4. Added this fix in 3.2.4, 3.3.2, 3.4.
Hide
Permalink
Christopher Mordue added a comment -

Created a new issue: MULE-6554 to keep track that I've committed only a partial fix for this issue. The new jira will be used for a more complete fix.

Show
Christopher Mordue added a comment - Created a new issue: MULE-6554 to keep track that I've committed only a partial fix for this issue. The new jira will be used for a more complete fix.

People

  • Assignee:
    Christopher Mordue
    Reporter:
    Mike Schilling
Vote (2)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: