The SAP native file does not get resolved, when container is running as a wrapper

Talend Version          6.2.1


 The SAP jobs work fine if the container is running standalone. though when container running as wrapper it throws
java.lang.NoClassDefFoundError: com/sap/conn/jco/ext/DestinationDataProvider
Additional Versions  All
Product Talend Data Integration
Component  Jobserver/Runtime
Problem Description  
The exception could be diff based on your job. Here from a route we are invoking a job which is in turn invoking SAP BAPI 

Caused by: java.lang.NoClassDefFoundError: com/sap/conn/jco/ext/DestinationDataProvider 
at esb_etl_agrom_flux.j_mdm_sap_main_0_1.J_MDM_SAP_Main.tSAPConnection_1Process(
at esb_etl_agrom_flux.j_mdm_sap_main_0_1.J_MDM_SAP_Main.tPrejob_1Process( 
at esb_etl_agrom_flux.j_mdm_sap_main_0_1.J_MDM_SAP_Main.runJobInTOS( 
at org.talend.camel.TalendProducer.invokeTalendJob( 
at org.talend.camel.TalendProducer.process( 
at org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process( 
... 21 more 
Caused by: java.lang.ClassNotFoundException: cannot be found by esb_etl_agrom_flux.J_MDM_SAP_Main_0.1.0 
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal( 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass( 
at org.eclipse.osgi.internal.loader.BundleLoader.findClass( 
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass( 
at java.lang.ClassLoader.loadClass( 
Problem root cause  When container is Environment variable LD_LIBRARY_PATH is not respected.
Solution or Workaround
In the wrapper configuration file, please check the variable named
java.library.path by default its pointing to container/lib/wrapper
You can directly put the .so file at this location. 
JIRA ticket number  
Version History
Revision #:
1 of 1
Last update:
‎05-17-2017 07:32 PM
Updated by:
Labels (1)