Maybe. But I don't understand how it is possible in general with
XAResources supporting transaction interleaving - multiple transactions
linked to XAResource (only one active).
Which timeout should be used and when? What are the affects?
This ain't in the spec.
i was thinking of a much simpler fix than this. i was thinking purely at the configuration level. when you configure an xa-datasource, you can (now) alter the xaresource timeout. however, if you leave the config setting out, a default (5 min or something) is used. however, our application has long running transactions, so our transaction manager configuration timeout is very long. this turned out to be meaningless because the xaresource timeout was very low. all i was asking for in the bug report was that when the xa-datasource is configured, if it has no explicit xa-resource-timeout value in the config file, then it should use the transactionmanager timeout for it's default. i realize that the actual timeouts can very at runtime due to tweaking other values, however i'm just referring to the initial values.
That can be done with a system property reference in the configuration(s).