This is a known issue in the following versions.

• SecurID Governance & Lifecycle 7.5.2
• RSA Governance & Lifecycle 8.0.0

The system may experience high CPU usages and slow response times for user requests. 

If a proxy server is in use the proxy server may generate the following error due to a response timeout. 

 "504 error bad gateway" 

The following error message may occur in the aveksaserver.log file indicating a timeout in a request form.

06/30/2023 17:11:27.597 ERROR (default task-120127) [com.aveksa.gui.pages.PageManager] 
java.lang.IllegalArgumentException: form required

Thread dumps taken during a performance event may show he RequestFormWizard thread blocking requests. 

"default task-12" #410 prio=5 os_prio=0 tid=0x00005621be77f800 nid=0x559a waiting for monitor entry [0x00007f7ac0d61000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at com.aveksa.gui.pages.PageManager.forwardRequest(PageManager.java:603)
	- waiting to lock <0x000000031f48a6e8> (a com.aveksa.gui.pages.changeRequest.edit.submit.RequestFormWizard)

If the response time for request forms that contain a "Drop Down Select with Web Service" control type exceeds the session  timeout it can cause deadlocks that prevent Wildly from servicing requests in a timely manner.  

This is resolved in the following versions which introduces a timeout (default 5 minutes) on the WebServices calls from the "Drop Down Select with Web Service" control type in custom forms.  

• SecurID Governance & Lifecycle 7.5.2 P09
• RSA Governance & Lifecycle 8.0.0 P01