SAP : JAVA Transport failing with Internal Server Error HTTP Code 500

Recently we are facing a issue where all BPM transport import is failing in PO JAVA system with below error –

WS Execution Error in CDTDEPLOY_DI (cx_ai_system_fault)
SOAP:1007 SRT: Unsupported xstream found: (HTTP Code 500 : Internal Server Error)
Error when processing Web Service Call

Connectivity for PO Java system is as below –

Solution Manager ——–> NWDS ———> SAP PO (JAVA)

Transport import from Solution Manager (CTS+)

The above transport is failing on Pre Prod system but it’s successfully completing in QA system so with same configuration & same NWDS system.

We followed SAP note – 1139406 but it didn’t help us there was no configuration change in the system because it’s deploying successfully in QA. We did restart PO multiple times but that also not help us.

we again trigger the transport & saw the below error in Developer Trace while transport is running.

ClientServerException exception:Write object <> failed! Caused by: com.sap.engine.frame.core.locking.LockException:Cannot lock 14051311214586500000pwdf5674……………….18228850,J2EE_CONFIGURATION_MANAGER,22352127/cb1c722f/30c4e431/18064/2dca72/6f336575/573c0b09/abe4c6a3/8f4414e3…]; it is in use by another owner. The lock collision occurred with user .

There is an standard SAP note for the same issue – 2023974 – Write object failed – Cannot lock as it is in use by another owner.

We followed the SAP note as it’s saying to delete the JAVA locks from PO system & re import, after deleting locks from PO system we again restart the PO & NWDS system again & then import the same, now this time it’s successfully imported in the system.

Reference note for JAVA system performance
2579836 – AS Java system has performance problem – FCAException – Best practices and tuning recommendations

Create Dummy Project for local transport

We have CHARM implemented in our landscape & all the local creation of TR’s are prohibited as per policy. During upgrade of Solution Manager 7.2 it’s asking for perform some change in Shadow System. Change is Shadow System asking TR & which we are not able to save as LOCAL due to CTS enabled.

Alternative Solution for the same is.

Create dummy project in system directly via SA38 – RSWBO_AUX_PROJECT

This new dummy project will visible in system & you can save the local TR & continue with the change or upgrade.