on Apr 23, 2020Article Content
| Article Number | 000038763 |
| Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.2.0 |
| Issue | A test of a Generic REST Entitlement Collector that collects roles and their membership fails with the following error (Collectors > Entitlement Collectors > {Entitlement Collector Name} > Test button): Collector test failed: com.aveksa.server.runtimeServerException: Test request failed with response:com.aveksa.server.runtime.ServerException:com.jayway.jsonpath.PathNotFoundException:Missing property in path $['members'] Caused by Stack com.jayway.jsonpath.PathNotFoundException:Missing property in path $['members'] at com.jayway.jsonpath.internal.path.PathToken.handleObjectProperty(PathToken.java:72) at com.jayway.jsonpath.internal.path.PropertyPathToken.evaluate(PropertyPathToken.java:79 at com.jayway.jsonpath.internal.path.RootPathToken.evaluate(RootPathToken.java:62) (...) The full stack trace is shown here:  The following error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log): 03/31/2020 12:17:51.924 ERROR (ApplyChangesRegularThread-342) [com.aveksa.client.datacollector.framework.DataCollectorManager] DCM281: Collection Failed: CollectionFailedEvent[cmi = CollectionMetaInfo[\{ID=44, run_id=2232, collector_id=302, test-run=false, collector_name=Test REST EDC, data_file=/home/oracle/wildfly-10.1.0.Final/standalone/tmp/vfs/temp/tempac7863ba68d66b4e/content-c7e7073e23e990ed/contents/aveksa.war/WEB-INF/LocalAgent/collected_data/44.data}] message = null cause = com.jayway.jsonpath.PathNotFoundException: Missing property in path $['members']] com.jayway.jsonpath.PathNotFoundException: Missing property in path $['members'] Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.) |
| Cause | This is a known issue reported in engineering ticket ACM-104961. |
| Resolution | This issue is being investigated by the Engineering team in order to provide a permanent resolution in a future release. |