Generic REST Collector ignores the Response Timeout Setting configured in the Collector Definition in RSA Identity Governance & Lifecycle
Originally Published: 2020-04-22
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
Generic REST Collector does not URL-encode Query Parameters in RSA Identity Governance & Lifecycle 35Number of Views Generic REST Collector "Unexpected response content type" in RSA Governance & Lifecycle 62Number of Views Generic REST Collector ignores Proxy setting in RSA Identity Governance & Lifecycle 73Number of Views Generic REST Collector fails with 'jsonpath.PathNotFoundException:Missing property in path $['members']' error collecting … 80Number of Views Segregation of Duties (SOD) Rule fails with error 'ORA-30926: unable to get a stable set of rows in the source tables' err… 229Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle RSA Authenticator 6.2.2 for Windows Administrator Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?