Closed yaohf777 closed 1 year ago
I just found the issue was resolved after updating my pom.xml. My guess is that there is something strange in neo-java-web-api.
Below dependency reports above issue:
<dependency>
<groupId>com.sap.cloud</groupId>
<artifactId>neo-java-web-api</artifactId>
<version>3.43.12</version>
<scope>provided</scope>
</dependency>
Below dependency reports no issue:
<dependency>
<groupId>com.sap.conn.jco</groupId>
<artifactId>sapjco3</artifactId>
<version>3.1.7</version>
<scope>provided</scope>
</dependency>
Hi @yaohf777, none of your mentioned dependencies nor class paths from stack traces belong to our library. I'm glad you solved the problem, but this was not the right repository for the issue anyway 😉
Dear colleague,
Our application is a Cloud Foundry based SaaS application and we need to perform JCo call. I following SAP help - Calling JCo APIs from Newly Created Threads to call JCo in a new thread with code like below:
The strange thing is that getting JCoDestination & JCoRepository in orginal thread works fine and also getting JCoDestination works also fine in the new thread. However getting JCoRepository throw below exception:
It looks the JCoDestination .getRepository() works differently with JCoDestinationManager.getDestination(destinationName). Need your support here. We can have a call if needed. Thanks.
Best regards, Haifeng Yao