The Local Transaction Manager does not support transactions with definite timeouts. If you set the timeout-in-seconds attribute in the transaction-service element to a value that is greater than 0, all local transactions are processed as global transactions. A timeout value of 0 means that the transaction manager waits indefinitely if there is no response from a participating data source.
If the Data source driver does not support global transactions, a local transaction might fail.
Workaround: Reset the timeout-in-seconds value to the default of 0.