Setting JTA And Application Server Timeouts Correctly To Prevent XAResource.XAER_RMFAIL Errors In Oracle Commerce
Last updated on JANUARY 05, 2017
Applies to:Oracle Commerce Platform - Version 9.4 and later
Information in this document applies to any platform.
Oracle Commerce server can freeze or fail with errors on the data sources. These are frequently attributed to Oracle Commerce because the data sources are for use with Oracle Commerce schemas.
The errors are similar to this:
Oracle Commerce uses XA Data Sources defined on the application server, in this case Weblogic Server. The sources used are just wrappers to a JNDI connection so although defined to be used by Oracle Commerce for it's schemas there is no specific configuration within them that will likely cause XA errors, and in most if not all cases, XA errors of this kind can always be traced back to how they are defined on the application server or database. All Oracle Commerce really needs is a valid connection to the database, how it is configured beyond that is irrelevant and that is where these errors occur.
The same error can occur with JBoss for the same reason, the timeouts are misconfigured between the database and application server.
Users often mistake this as an Oracle Commerce problem because the error appears when using Oracle Commerce.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms