Socket timeout calling long-running SOAP web service

[wesk...@optonline.net]

I have a SOAP-based web service that I have developed running on WebSphere 6.0. I have also developed a simple web-based interface to test the web service. It interfaces with the web service using SAAJ. <br />
<br />
The problem I'm having is that some of my longer running transactions take more than 5 minutes to complete. However, in these cases, I am getting back a SOAP response at or around the 5 minute mark that includes the message...<br />
<br />
java.net.SocketTimeoutException: Socket operation timed out before it could be completed<br />
<br />
Meanwhile, I can see that the service is still processing and appears to complete successfully about a minute later.<br />
<br />
I'm not quite sure if this is a problem with the client or the server. So far, I've tried setting custom HTTP transport properties for the following (both defailt to 300 sec = 5 min) <br />
<br />
com.ibm.websphere.webservices.http.connectionTimeout <br />
com.ibm.websphere.webservices.http.SocketTimeout <br />
<br />
Neither of these seemed to matter. Any guidance would be greatly appreciated.

[wesk...@optonline.net]

I'm bumping this one again, in hopes that someone who may have an answer might have just missed this the first time.<br />
<br />
Thanks in advance.

[Ken Hygh]

I suspect it's an underlying TCP/IP timeout, and there's nothing in the
WebSphere config that'll help.

Ken