You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Eran Chinthaka (JIRA)" <ji...@apache.org> on 2007/06/11 20:19:31 UTC
[jira] Updated: (AXIS2-2022) setting HTTPConstants.SO_TIMEOUT
option doesnt seems to work
[ https://issues.apache.org/jira/browse/AXIS2-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eran Chinthaka updated AXIS2-2022:
----------------------------------
Priority: Blocker (was: Major)
Fix Version/s: 1.3
I think we should fix this too for the next release.
> setting HTTPConstants.SO_TIMEOUT option doesnt seems to work
> ------------------------------------------------------------
>
> Key: AXIS2-2022
> URL: https://issues.apache.org/jira/browse/AXIS2-2022
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2
> Environment: jdk1.5 windows XP
> Reporter: Arnaud Louet
> Assignee: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.3
>
>
> on a genrated stub at construction time, the following code doesn't seems to change the default timeout:
> _serviceClient.getOptions().setProperty(HTTPConstants.SO_TIMEOUT,new Integer(5*60*1000));
> the following call works though
> _serviceClient.getOptions().setTimeOutInMilliSeconds(5*60*1000);
> the documentation ( http://ws.apache.org/axis2/1_1_1/http-transport.html#timeout_config ) implies that both methods should work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org