On 24/07/2012 17:16, Daniel Kulp wrote:
On Tuesday, July 24, 2012 10:56:47 AM James Talbut wrote:
Hi,
I've calling a SOAP service that I expect to take a while to complete.
I've using the code below to prepare the proxy.
But it keeps generating a SocketTimeoutException after two minutes.
Have I missed something?
Bizzarre. CXF's default is one minute. Thus, something definitely is
changing it if it's getting up to 2 minutes. Maybe it's the first default
timeout of 60 secs and then another 60 seconds on an alternate URL from
LoadDistributorFeature? No idea really.
However, it's likely that it's an issue in the LoadDistributorFeature. I
believe the LoadDistributorFeature creates a new conduit and thus the
original conduit (that you configured) might be gone. You may be able to
try setting the feature prior to calling the client.getConduit().... that
might work.
That sorted it.
I can't account for the 2m vs 1m issue, but setting the timeout after
the LoadDistributorFeature sorted it.
I also added a log of the timeout before changing the other code and it
was 60000, so really no answer for the 2m delay.
Thanks
Jim
