Web Service SOAP Adapter Error

[former_member411599]

Hi all

We just upgraded from PI7.0SP13 to SP18. We have a couple of Web Services running that worked fine in SP13. Now, after the upgrade they don't work anymore, and we get the following error when trying to execute the SOAP request:

com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve binding for the given channelId: Binding:CID=a1a08d8558de39c691a8c80a4f524b1c;

at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBindingByChannelId(AbstractLookupManager.java:361)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:424)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

I've tried all the things that I have found in the forum, e.g. CPA cache refresh, restart the system, make channel inactive and active again in ID, stop and start in channel monitoring, but nothing appears to be helping.

Can anybody help?

Thank you,

Daniel

[agasthuri_doss]

Hey,

1) Check - AI_RUNTIME_JCOSERVER & NTEGRATION_DIRECTORY_HMI is good

2) Refresh Adapter Engine Cache

Cheers

Agasthuri

[prateek]

By any chance, do your scenario involves secure communication like HTTPS? What is the complete scenario?

Regards,

Prateek

[former_member411599]

Hi Prateek

We do not use HTTPS. It is a simple Web Service that is called via HTTP with a request that calls a BAPI using the RFC adapter and returns the answer from the BAPI via the Web Service.

<wsdl:service name="MI_GETACCOUNTADDRTOWRITE_OU_SYService">

<wsdl:port name="MI_GETACCOUNTADDRTOWRITE_OU_SYPort" binding="p1:MI_GETACCOUNTADDRTOWRITE_OU_SYBinding" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

<soap:address location="http://<domain.name>:50000/XISOAPAdapter/MessageServlet?channel=:BS_GETACCOUNTADDRTOWRITE:CC_S_SOAP_GETACCOUNTADDRTOWRITE&amp;version=3.0&amp;Sender.Service=BS_GETACCOUNTADDRTOWRITE&amp;Interface=http%3A%2F%2Fxxxxxx.com%2Fxi%2Faccount%5EMI_GETACCOUNTADDRTOWRITE_OU_SY" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>

</wsdl:port>

</wsdl:service>

Thank you,

Daniel

[prateek]

Could you try regenrating your WSDL and using it to send data to PI?

Regards,

Prateek

[former_member411599]

Yes, just did again, but still the same.

[Former Member]

Hi,

Does testing the scenario in ID test configuration give any error?

[MichalKrawczyk]

hi Daniel,

>>>I've tried all the things that I have found in the forum, e.g. CPA cache refresh, restart the system, make channel inactive and active again in ID, stop and start in channel monitoring, but nothing appears to be helping.

this should work for sure - check if the CPA refresh was successful

Regards,

Michal Krawczyk

[former_member411599]

Hi Michal

Did it again: CPA cache refresh (mode=full) successfully executed in 16828 milliseconds.

Still no luck. Any other ideas.

Thank you,

Daniel