Generic REST Collector ignores the Response Timeout Setting configured in the Collector Definition in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-22
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.2.0
Issue
In the example below, the Response Timeout is set to 10000 milliseconds (10 seconds). A test of the collector that fails to connect to the endpoint is expected to timeout after 10 seconds. Instead it takes four to five minutes to timeout.
Go to Collectors > Collector Type > {Collector Name} > Test button
Collector test failed:
com.aveksa.server.runtime.ServerException: Test request failed with response: Request timed out
com.aveksa.server.runtime.ServerException: Test request failed with response: Request timed out
Cause
Resolution
Related Articles
Timeout when editing a collector in RSA Governance & Lifecycle 148Number of Views Salesforce Collector is throwing 'Invalid Credentials' error after patching to RSA Governance & Lifecycle 8.0.0 P06 8Number of Views Generic REST Collector Test Authentication Token fails with 'Error encountered while fetching token, Status Code: 4… 251Number of Views RSA Via Lifecycle and Governance - How to set up an environment to run WebServices with Turkish Characters 14Number of Views Change Requests in Pending Submission state are not being deleted by the daily scheduled task in RSA Identity Governance &… 73Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?