Policy Xpress (PX) Policy Multiple Triggering Due to Duplicate Jar Files
search cancel

Policy Xpress (PX) Policy Multiple Triggering Due to Duplicate Jar Files

book

Article ID: 190691

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

Identity Manager may trigger the same Policy Xpress (PX) policy multiple times for a single task. This results in duplicate actions such as multiple emails being sent to users, tripled REST API calls to external systems (e.g., ServiceNow), or redundant database entries. This behavior is typically observed after patching or upgrades where backup jar files are incorrectly retained in the deployment library.

Environment

Identity Manager

Cause

This issue is caused by the Java classloader. When multiple versions of the same classes exist within the library path—even if renamed with a suffix—the application server may load both, causing the Policy Xpress engine to register and execute the same policy logic multiple times.

Resolution

To resolve this issue, remove all duplicate or backup jar files from the Identity Manager deployment directories. The application server's classloader may still attempt to load files even if their extensions have been modified.

  1. Identify problematic directories:
    • \\iam_im.ear\\library
    • \\iam_im.ear\\user_console.war\\WEB-INF\\lib
  2. Locate duplicate files: Look for files that have been renamed for backup purposes, such as:
    • identitymanager.jar_5_12
    • identitymanager.jar_old
    • user_console.jar_bak
  3. Perform cleanup:
    • Move these files completely out of the Identity Manager deployment directory (e.g., to a temporary folder on the desktop or a non-application path).
    • Do not simply rename them within the same directory.
  4. Restart Services: Restart the Identity Manager / JBoss / Wildfly service to clear the classloader cache.