We get timeouts on big "async" message of 2 M or so we send to remote system over SOAP receiver adapter. The backend process takes over 40 mts which we really don't care since we have Exactly Once as QOS. And the does message get there.
We timeout at the end of 5 mts. I'm thinking of using XMBWS parameter but not sure what good it will be.
The overall status of the message is "not delivered". Here's what's in the audit message. And each message has 3 retries (4 failures) - though the remote system received it and too forever to process it.
2007-11-06 12:47:16 Success SOAP: request message entering the adapter with user PIISUSER
2007-11-06 12:52:19 Error SOAP: call failed: java.net.SocketTimeoutException: Read timed out
2007-11-06 12:52:20 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Read timed out: java.net.SocketTimeoutException: Read timed out
2007-11-06 12:52:20 Error Exception caught by adapter framework: Read timed out
I need to accomplish the following -
1. Not have the "not delivered" status.
2. Several retries - which might get fixed if the status is "delivered"
By the way, the FAQ for SOAP is going through some modifications and therefore not available on the service marketplace.