I have a SOAP-PI-Proxy scenario and publish the service interface as a web service, unfortunately the inbound ABAP codes may need about 3 minutes, when I test the scenario with client codes or XMLSpy tool, we both get the time out issue.
From my understanding, this problem may happen in the following 2 phases:
1. from client to adapter engine (Java engine)
2. from adapter engine to integration engine via ICM service
Firstly I checked the log of the adapter engine and found that the time out happens after 1 minute after setting up the connection between adapter engine and integration engine (http://host:icmport/xi/engine.....), after some investigation it's because of the ICM processing time out limitation (60 seconds by default), therefore I changed the value from 60 seconds to 300 seconds, there is no error in the adapter engine.
But we still get the time out issue from the client side, I guess there also has the problem in the phase 1, it's due to some Java engine connection or processing time out settings, could anybody tell me which parameters should I change?
Any advice will be very appreciated.
Thanks and regards,
Does that mean your scenario is synchronous?
Did you check in sxmb_moni whether the Proxy returned some response?
It is possible the error is still not on the sender side. Incase if the proxy has given back the response and it comes till IE stack, you should be able to see it in sxmb_moni and then the failure should happen. I think, you should try and check the response and see where it fails in the end.
That will give a better clarity about the component which is throwing the error.