Meghana Reddy wrote:
baseUrl = com.order.process.gen.OrderService_Service.class.getResource(".");
//Here is where the CONNECT_TIMEOUT comes into picture
//since metro uses JDK's URLConnection class to obtain the WSDL.
//Since this is a generated class, we don't want to modify this and set a CONNECT_TIMEOUT here
url = new URL(baseUrl, "http://r8kmrzv:8080/orderweb/orderservice?wsdl");
1) Good to see now you are loading the WSDL from http instead of file.
2) Setting the following system properties will help you to provide timeouts when accessing the WSDL
sun.net.client.defaultConnectTimeout
sun.net.client.defaultReadTimeout
Meghana Reddy wrote:
Are you sure? I think when the web service client sends requests , the "com.sun.xml.internal.ws.request.timeout" (which is the BindingProvider.REQUEST_TIMEOUT) setting controls this.
Hope this gives you a better picture between the two:
CONNECT_TIMEOUT: It is the time taken to establish a (socket) connection
REQUEST_TIMEOUT: Maximum time between establishing a connection and receiving data from the connection.
--
Regards,
Abhijit.