on 07-19-2010 4:40 PM
Hello,
We have a scenario which is running in production since last 5 years.
Now,suddenly we have started receiving this error:
SOAP: call failed: java.net.SocketTimeoutException: Read timed out
There have been no changes in our system.
It works for some messages when our partner restarts their SOAP server and then again we start getting these errors.
Can someone please suggest what could be the reason?
Thanks.
Regards,
Shweta
Hi Shweta,
I think you can refer to note:
#893713 - XI 3.0 SOAP receiver adapter with explicit timeout
Also check this one:
#856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter
question "Can I configure the timeout value of my receiver adapter?"
Regards,
Caio Cagnani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello All,
I would like to apologize for the delay in response but we have been trying to cope up with this problem day and night for last three days.
The reason was,we had a change in our R/3 system because of which huge number of IDocs were being generated.
SOAP server at partner side was not able to handle such heavy load and hence,it was failing every now and then.
Now we have changed maxThreads count to 20 and they have increased maximum number of database connections at their end and it seems to work at the moment.
We are looking for a change in R/3 to reduce the number of IDocs generated.
Thanks to all for helping in this.
Regards,
Shweta
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Increase the folowing timeout parameter as given in SAP note Note 824554 - ICM and SAP Web Dispatcher Timeout Parameter
icm/server_port_ < n > = ...,TIMEOUT= sec
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Shweta,
If I am not wrong, is this a sync scenario, where a response is coming back from web service?
This error message indicates that the problem is with the web service. Please check with your receiving partner and ask them to review their service. As you have indicated, the messages are processed when the web server is re-started, so the issue is with the partner system.
Regards,
Neetesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.