Originally posted by David O'Meara: Is it the actual WSDL2Java part which is timing out? If so, you can provide a "-T 600" to extend the default timeout, as we have had to do.
Thanks.. Its not the WSDL2java thats timing out but when i access a webservice on a remote server this happens sometimes. I wanted to know if this is happening because the server has too much traffic on it or is it some other reason.
Will the timeout property help me solve the problem. Another thing when i invoked the geTimeout() on the application i got 0. what does that mean.
Is there any way to test the timeout property. Because the webservice is a live service i have no was to see if the setTimeout will actually resolve my problem.