We are noticing slow processing of request in Production environment.
Release : 14.3
Component : IdentityMinder(Identity Manager)
unfortunately, your logs are in error with no debug statements.
in the server log we see this message a few times
2021-06-22 10:16:14,588 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016037: Could not find new XAResource to use for recovering non-serializable XAResource XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a824855:5b5a5d5f:60cedea4:b496, node_name=1, branch_uid=0:ffff0a824855:5b5a5d5f:60cedea4:b497, subordinatenodename=null, eis_name=unknown eis name >, heuristic: TwoPhaseOutcome.FINISH_OK co[email protected]621a1bee >
2021-06-22 10:16:14,588 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff0a824855:5b5a5d5f:60cedea4:b496, node_name=1, branch_uid=0:ffff0a824855:5b5a5d5f:60cedea4:b497, subordinatenodename=null, eis_name=unknown eis name >
And this message all through the 10 to 12 time frame
2021-06-22 10:16:18,417 WARN [org.hornetq.core.client] (Thread-8490 (HornetQ-client-global-threads-1359000088)) HQ212054: Destination address=jms.queue.iam.im.jms.queue.RuntimeStatusDetailQueue is blocked. If the system is configured to block make sure you consume messages on this configuration.
your JMS message queue being blocked would cause your system to go down as it is needed to move tasks in IM through the different modules of IM code.
So while I cannot tell you what happened to the JMS message queue, I can tell you that it was not identity manager that caused the issue and the reason the issue went away when you restarted was because the /data/ folder was deleted and that rebuilt the message queue when the server restarted.