You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-auto@ws.apache.org by "Juho Yli-Krekola (JIRA)" <xm...@ws.apache.org> on 2006/11/01 14:25:16 UTC
[jira] Created: (XMLRPC-120) XmlRpcCommonsTransport replyTimeout
bug
XmlRpcCommonsTransport replyTimeout bug
---------------------------------------
Key: XMLRPC-120
URL: http://issues.apache.org/jira/browse/XMLRPC-120
Project: XML-RPC
Issue Type: Bug
Components: Source
Affects Versions: 3.0
Reporter: Juho Yli-Krekola
Priority: Minor
XmlRpcCommonsTransport.initHttpHeaders tries to set replyTimeout to soTimeout like this:
if (config.getReplyTimeout() != 0)
client.getHttpConnectionManager().getParams().setSoTimeout(config.getConnectionTimeout());
Shouldn't the second line be config.getReplyTimeout() instead of config.getConnectionTimeout()? I have not tested this in any way, but I just saw this line when reading the code and the bug seems obvious.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (XMLRPC-120) XmlRpcCommonsTransport replyTimeout
bug
Posted by "Jochen Wiedmann (JIRA)" <xm...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/XMLRPC-120?page=all ]
Jochen Wiedmann resolved XMLRPC-120.
------------------------------------
Resolution: Fixed
Applies to 3.0 branch and trunk, thank you!
> XmlRpcCommonsTransport replyTimeout bug
> ---------------------------------------
>
> Key: XMLRPC-120
> URL: http://issues.apache.org/jira/browse/XMLRPC-120
> Project: XML-RPC
> Issue Type: Bug
> Components: Source
> Affects Versions: 3.0
> Reporter: Juho Yli-Krekola
> Priority: Minor
>
> XmlRpcCommonsTransport.initHttpHeaders tries to set replyTimeout to soTimeout like this:
> if (config.getReplyTimeout() != 0)
> client.getHttpConnectionManager().getParams().setSoTimeout(config.getConnectionTimeout());
> Shouldn't the second line be config.getReplyTimeout() instead of config.getConnectionTimeout()? I have not tested this in any way, but I just saw this line when reading the code and the bug seems obvious.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira