Email Notifications Fail for Secondary Approval Due to JTA Transaction Error - Identity Manager

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

When using the "Workflow Pending" trigger in an Email Policy, notifications are generated successfully for the first approver but fail for the secondary (Business Owner) approver. In the task logs and View Submitted Tasks (VST), the secondary email remains in "In Progress" status indefinitely. Additionally, the WebSphere System.Out log reports the following error: java.sql.SQLException: DSRA9350E: Operation setAutoCommit is not allowed during a global transaction.

Environment

Identity Manager 14.5

Cause

The issue occurs because the task persistence data source is enlisted in a global transaction (JTA). When the application attempts to perform a non-transactional commit, the transaction manager blocks the operation to prevent data integrity issues, as the task persistence requires a non-transactional context.

Resolution

To resolve this, configure the task persistence data source as non-transactional within the WebSphere Application Server:

1. Log in to the WebSphere Application Server console.
2. Navigate to Resources > JDBC > Data sources.
3. Select the data source used for task persistence.
4. Under the Additional Properties heading, select WebSphere Application Server data source properties.
5. Select the Non-transactional data source checkbox.
6. Click OK to save the changes.
7. Restart the WebSphere Application Server to apply the configuration.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.