How to configure timeouts in wls 9.2?

Question

Hello,
i have two problems i cannot resolve by myself or simply browsing through the net and I hope you can help me.
Both the questions are about web applications on WeblogicServer 9.2
1)
I have a web application with a web service client inside. I use axis 2 and Http Client for the transport.
I need to configure the connection timeout (not the socket timeout) but i cannot find any method to do this.
The SSLSocketFactory does not expose a method to create the socket with a connection timeout as input parameter. The only way I figured out is to use the method without input parameters to obtain an unconnected socket, configure it as i wish and establish the connection:
Socket socket = socketfactory.createSocket();
SocketAddress localaddr = new InetSocketAddress(localAddress, localPort);
SocketAddress remoteaddr = new InetSocketAddress(host, port);
socket.bind(localaddr);
socket.connect(remoteaddr, timeout);
Unfortunately the methos createSocket() is not implemented by any socketFactory implementation i have available.
What can I do?
2)
I have a web application with an EJB client inside. I need to configure a sort of timeout to break the connection if the server is taking too long.
I have no control on the server side, so I can't use the <remote-client-timeout> to get the point.
Is there any way to configure connection and socket timeout for the RMI call of an EJB client?
Alternatively I have wrapped the client call in a separate thread, launched by a Timeout Controller.
The controller waits for some time, then, if the Task is still alive , send it an interrupt and continue. The trick seems work fine, but the thread executing the task remains waiting for the EJB response and i risk to saturate the application server.
Which is the best way to overcome the problem?
Thank you.

Answer 1

For the first question, have you tried using this:
options.setProperty(HTTPConstants.CONNECTION_TIMEOUT, new Integer(timeOutInMilliSeconds));
It seems to be explained well over here:
http://ws.apache.org/axis2/1_3/http-transport.html#timeout_config
This uses the axis2 http transport and not the jakarta commons httpclient.
I have used some other properties of the axis2 http transport- but have not specifically used the connection_timeout property before.
Is there a reason why you would use the httpclient over the axis2 http transport for a web service client?