Recently we are facing a issue where all BPM transport import is failing in PO JAVA system with below error –<\/p>\n
WS Execution Error in CDTDEPLOY_DI (cx_ai_system_fault)
\nSOAP:1007 SRT: Unsupported xstream found: (HTTP Code 500 : Internal Server Error)
\nError when processing Web Service Call<\/p>\n
Connectivity for PO Java system is as below – <\/p>\n
Solution Manager ——–> NWDS ———> SAP PO (JAVA)<\/p>\n
Transport import from Solution Manager (CTS+)<\/p>\n
The above transport is failing on Pre Prod system but it’s successfully completing in QA system so with same configuration & same NWDS system.<\/p>\n
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.<\/p>\n
we again trigger the transport & saw the below error in Developer Trace while transport is running.<\/p>\n
ClientServerException exception:Write object <> There is an standard SAP note for the same issue – 2023974 – Write object failed – Cannot lock as it is in use by another owner.<\/p>\n 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.<\/p>\n Reference note for JAVA system performance 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 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[8],"tags":[418,548,546,545,547,550,549,544,241,551],"class_list":["post-648","post","type-post","status-publish","format-standard","hentry","category-sap-updates","tag-cts","tag-http-code-500","tag-internal-server-error","tag-lock-collision","tag-nwds","tag-sap-note-1139406","tag-sap-note-2023974","tag-sap-note-2579836","tag-solman","tag-write-object-failed"],"_links":{"self":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/648","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/comments?post=648"}],"version-history":[{"count":1,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/648\/revisions"}],"predecessor-version":[{"id":649,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/posts\/648\/revisions\/649"}],"wp:attachment":[{"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/media?parent=648"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/categories?post=648"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adilfahim.com\/myblog\/wp-json\/wp\/v2\/tags?post=648"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n2579836 – AS Java system has performance problem – FCAException – Best practices and tuning recommendations<\/p>\n","protected":false},"excerpt":{"rendered":"