SAP IDC and EDC collectors fail with "Error getting the version of the native layer: java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path" in RSA Governance & Lifecycle
2 years ago
Article Number
000068662
Applies To

This is a known issue in the following versions:

  • RSA Governance & Lifecycle 8.0.0
Issue
SAP IDC and EDC collectors fail with the following error in aveksaServer.log:
10/03/2023 15:04:48.187 ERROR (ApplyChangesChangeDataRequest-1696337497020-1696337497020) [SystemErr] 
java.lang.ExceptionInInitializerError: Error getting the version of the native layer: java.lang.UnsatisfiedLinkError: no sapjco3 in java.library.path
	at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:210) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:75) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at java.lang.Class.forName0(Native Method) ~[?:1.8.0_362]
	at java.lang.Class.forName(Class.java:264) ~[?:1.8.0_362]
	at com.sap.conn.jco.JCo.createJCo(JCo.java:52) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at com.sap.conn.jco.JCo.<clinit>(JCo.java:26) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:77) ~[sapjco3-1.4.0.jar:20111129 0022 [3.0.8 (2011-11-28)]]
	at com.aveksa.collector.sap.edc.SapHanaConnector.connect(SapHanaConnector.java:127) ~[classes/:?]
	at com.aveksa.collector.sap.edc.SapHanaEntitlementDataIterator.<init>(SapHanaEntitlementDataIterator.java:78) ~[classes/:?]
	at com.aveksa.collector.sap.edc.SapHanaEntitlementDataReader.getEntitlementIteratorForTestData(SapHanaEntitlementDataReader.java:67) ~[classes/:?]
	at com.aveksa.client.datacollector.collectors.entitlementdatacollectors.EntitlementDataCollector.collectData(EntitlementDataCollector.java:336) ~[datacollectors.jar:?]
	at com.aveksa.client.datacollector.collectors.entitlementdatacollectors.EntitlementDataCollector.collect(EntitlementDataCollector.java:285) ~[datacollectors.jar:?]
	at com.aveksa.client.datacollector.collectors.entitlementdatacollectors.EntitlementDataCollector.collectTestData(EntitlementDataCollector.java:260) ~[datacollectors.jar:?]
	at com.aveksa.client.datacollector.framework.DataCollectorManager.collect(DataCollectorManager.java:580) ~[datacollectorframework.jar:?]
	at com.aveksa.client.component.collector.DefaultCollectorManager.actUpon(DefaultCollectorManager.java:205) ~[components.jar:?]
	at com.aveksa.client.component.collector.DefaultCollectorManager.handle(DefaultCollectorManager.java:103) ~[components.jar:?]
	at com.aveksa.client.component.event.DefaultEventManager.handle(DefaultEventManager.java:70) ~[components.jar:?]
	at com.aveksa.client.datacollector.framework.SimpleEventSource.notifyListeners(SimpleEventSource.java:67) ~[datacollectorframework.jar:?]
	at com.aveksa.client.component.communication.DefaultCommunicationManager.notifyEvent(DefaultCommunicationManager.java:378) ~[components.jar:?]
	at com.aveksa.client.component.communication.ChangeListHandler.applyChanges(ChangeListHandler.java:358) ~[components.jar:?]
	at com.aveksa.client.component.communication.ChangeListHandler.access$100(ChangeListHandler.java:46) ~[components.jar:?]
	at com.aveksa.client.component.communication.ChangeListHandler$ChangeApplyingRunnable.run(ChangeListHandler.java:276) ~[components.jar:?]
	at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_362]
 
Cause
The sapjco3-1.4.0.jar and other related jars are available in that path location but with different names (with jar name extension as -1.4.0), hence unable to find the sapjco3 jar and causing failure in the SAP collection.
Resolution
This issue is resolved in the following version/patch:
  • RSA Governance & Lifecycle 8.0.0 P01
Workaround
For a work around please contact RSA Customer Support and quote this article.