Skip to main content
Krzysztof Zimny ha fatto una domanda in * MuleSoft *

Hi, the current version of the SAP JCo connector enforces the name of the containing jar at runtime. 

This will lead to exceptions, if it doesn't match the name (sapjco3.jar).

JCo initialization failed with java.lang.ExceptionInInitializerError: Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar".

It is not allowed to rename or repackage the original archive "sapjco3.jar".

Caused by: java.lang.ExceptionInInitializerError: JCo initialization failed with java.lang.ExceptionInInitializerError:

Illegal JCo archive "com.sap.conn.jco.sapjco3-3.1.13.jar". It is not allowed to rename or repackage the original archive "sapjco3.jar".

 

This is a known issue described in the documentation: 

-

https://docs.mulesoft.com/sap-connector/latest/sap-connector-troubleshooting#jco-renaming-conflicts

 

-

https://help.salesforce.com/s/articleView?id=001117810&type=1

 

 

To resolve this error, the maven-shade-plugin should be added to pom.xml which relocate (rewrite) packages to avoid classpath conflicts. Unfortunately, this approach works only at runtime, but not for MUnit tests. Does anyone know how to configure the pom.xml file for the MUnit tests?  

 

3 risposte
  1. 13 mar, 14:55

    Is there truly no working solution to this issue? I would be grateful for any assistance that someone might be able to provide.

0/9000