You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by beni_it2003 <be...@yahoo.co.in> on 2009/09/24 13:18:56 UTC

options.setTimeOutInMilliSeconds is not working in AIX system

Hi All :

       I am facing a strange issue with the connection timeout in Axis2
client. I have set the time out period as 120 sec. If the axis2 client takes
more than this, it would probably throw an exception saying that Connection
Timed out. But this is not timing out even after 120 sec.( It is working
perfectly with less time out period like 5 sec ).   I have set the
appropriate properties like SO_TIMEOUT, CONNECTION_TIMEOUT. 

Environment : 

Application Server : Websphere
Axis                    :  Axis 2 1.4.1
Transaction          : application transactions are managed Websphere
transaction manager
System                : IBM AIX Machine

Please see the below code snippet to see the way option parameters are set.

            options.setTimeOutInMilliSeconds(wsTimeOut);
            options.setProperty(HTTPConstants.SO_TIMEOUT,
Integer.parseInt(timeout) );
            options.setProperty(HTTPConstants.CONNECTION_TIMEOUT,
Integer.parseInt(timeout) );
            options.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, "true");
            options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
            sender.setOptions(options);

But really don't know why this is not timing out. Axis Client keeps trying
for more than 300 sec....

Is there any Websphere level or Machine setting which is overriding this
timeout? 
or
Is there any parameters need to set to get this working?


Thanks,
Beni .M

-- 
View this message in context: http://www.nabble.com/options.setTimeOutInMilliSeconds-is-not-working-in-AIX-system-tp25557509p25557509.html
Sent from the Axis - User mailing list archive at Nabble.com.