Skip to Content
0

Axis Framework Conflict with JMS Drivers

Mar 02, 2017 at 04:35 AM

127

avatar image

Hello,

We had JMS drivers(Active MQ) deployed earlier on SAP PO 7.5 and is working in Production.

For a separate requirement, we have deployed Axis framework (used for custom SOAP header, SOAP 1.2 and Digital Signatures).

Axis is throwing Linkage error saying:

Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.apache.commons.logging.LogFactory.getLog

between class loader of the current class, com/sap/aii/adapter/axis/ra/handlers/soap/MTOMProcessingHandler

and the class loader 'library:com.sap.aii.adapter.lib (for the Active MQ Library)

-------------------------------------------------------------------------------------------------------------

The framework was initially working in Development, but after deploying in quality it is having this issue. We tried removing the commons-logging jar from development and see if Axis still works(wanted to try this in dev before attempting in Quality), but quickly understood that Axis would not start without the commons logging jar. So we included the commons-logging again and now getting the same error in development as well.

-------------------------------------------------------------------------------------------------------------

Raised OSS Message -- SAP is suggesting to have a separate host / decentral adapter engine or a separate AEX to host Axis libraries-- the intention is to separate the JMS and Axis at the host level. SAP is saying that both JMS drivers and the Axis will not be able to co exist together in the same host due to this conflict.

It is hard to digest, that every time we have a need for additional drivers, and if this problem is encountered, we need to have a separate host for another decentral adapter engine or AEX.

Did any one of you faced this issue and have any recommendations?

Thanks and Regards,

Himadri

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Himadri Chakraborty Mar 20, 2017 at 10:33 PM
1

This is resolved.

SAP finally provided a fix for this issue.

The Axis FAQ SAP Note : 1039369 is updated with the resolution. Please check point 8 under General Questions of the AXIS FAQ for the resolution.

Thanks,

Himadri

Share
10 |10000 characters needed characters left characters exceeded