search cancel

Request Instrumental IM Jar Files to isolate JMS queue / DB challenges


Article ID: 201765


Updated On:


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


ENV:  Target IM r14.1 cp8 (plus hotfixes) on Wildfly 8.2.1 with five (5) J2EE Nodes.

Challenge:   Daily (or more often) IME nodes need to be restarted (Wildfly stop if possible/killed if needed), to address stuck JMS queue.

JMS queue is monitored every 5 minutes (automated), and when growth does not decrease after 60 minutes, the IME VST is checked to confirm no progress for IM tasks,  the Wildfly nodes are restarted (manually/rolling restart) to allow the JMS queue to progress.   We see this issue on all 

Using the native Wildfly logging features and additional JMS features via process, we can pause the JMS queue to review which IM tasks are in progress.

However,  any JMS event that is stuck, does not maintain this information about the IM tasks.

As such, we are not able to progress RCA.

Request:   Debug / Instrumental IM jar that will produce additionally logging for the JMS queue with full JSON or similar information that can be used for RCA for any JMS/DB challenges.

This would be placed on one (1) of the five (5) J2EE nodes to help isolate this issue.  

This would be a temporary process.

Would like to have a properties file or configuration switch (JVM) or similar to allow adjustments for verbose for features that this would provide.

This process will also help resolve other CA support cases related to DB locks.


Release : 14.1

Component : IdentityMinder(Identity Manager)


There is very little information available about JMS transactions because we rely on 3rd party jars to process this type of information.

Sustaining engineering is unavailable at this time to provide this information.