|Applies To||RSA Product Set: Identity Management & Governance, RSA Identity Governance & Lifecycle|
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 6.8.1.,6.9, 6.9.1, 7.0.0, 7.0.1, 7.0.2
Platform: WebSphere, WebLogic, Wildfly
|Issue||WebSphere generates a large number of errors associated with the XA transaction rollback tables in the WebSphere system.out log.|
Wildfly generates a large number of errors associated with the XA transaction rollback tables in the server.log located in /home/oracle/jboss-4.2.2.GA/server/default/deploy/aveksa.ear/aveksa.war/log (6.9.1) or /home/oracle/wildfly-8.2.0.Final/standalone/log (7.0.0 and later).
In addition systems where the transaction rollback is not configured correctly the system may experience slow performance and high CPU loads when a large number of failed transactions are pending such as may occur if there is a workflow that is failing due to a fault. This can lead to other workflows that are configured correctly to fail.
|Cause||This issue may occur on if the RSA Identity Governance and Lifecycle user AVUSER is not configured with permission to access the Oracle XA transaction rollback tables. This can also cause the transaction tables to fill up.|
XA transaction database grants are already present if you are using a hardware appliance with local database, but these grants need to be manually added for WebSphere and WebLogic servers or Wildfly appliances with external databases. The 6.8.1 and 6.9.1 installation guides for WebSphere and WebLogic do not include this information. This is corrected in the RSA Via L&G 7.0 installation guide.
|Resolution||1. For Hardware and Software appliances with a local database the setup will install the correct grants. |
2. For Hardware and Software Appliances based on Wildfly the instructions for applying the correct database grants for a remote database are covered starting on page 28 of the Database Setup and Management Guide for 7.0.1 in the chapter “Configure the User Schema Privilege Grants”.
3. For older Oracle or WebSphere instances apply the following Oracle grants for AVUSER to the following XA transaction tables:
grant select on pending_trans$ to avuser;
grant select on dba_2pc_pending to avuser;
grant select on dba_pending_transactions to avuser;
grant execute on dbms_xa to avuser;
On WebSphere the transaction logs can also take up considerable disk space. If the grants were not applied correctly you should also clean up the old transaction logs.
See the following IBM article for more information for XA transaction configuration for WebSphere.
See the following Oracle Article for more information for XA transaction configuration for WebLogic.