[
http://jira.codehaus.org/browse/XFIRE-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99401
]
Alex Ranous commented on XFIRE-1037:
------------------------------------
Opps, this should have been filed against the core component, not generator.
> XFire needs a way to set the client http connection timeout
> -----------------------------------------------------------
>
> Key: XFIRE-1037
> URL: http://jira.codehaus.org/browse/XFIRE-1037
> Project: XFire
> Issue Type: Improvement
> Components: Generator
> Affects Versions: 1.2.6
> Reporter: Alex Ranous
> Assignee: Dan Diephouse
> Attachments: CommonsHttpMessageSender.java.patch
>
>
> When using XFire as a client, we would notice very long timeouts before
> failure if the remote server was unreachable. It seems that, there is no way
> to set the TCP connection timeout when making calls on an HTTP connection.
> You can set the TCP socket timeout by calling:
> client.setProperty(CommonsHttpMessageSender.HTTP_TIMEOUT, timeout);
> This only is used once you have a TCP connection. I had thought by trying
> something like this might work:
> params.setIntParameter(HttpConnectionParams.CONNECTION_TIMEOUT,
> mConnectionTimeout);
> client.setProperty(CommonsHttpMessageSender.HTTP_CLIENT_PARAMS, params);
> Apparently, due to the way the HTTPClient is initialized, this doesn't work
> either. Eventually, I had to create a new HTTP_CONNECTION_TIMEOUT value in
> CommonsHttpMessageSender and add code to explicitly set the connection
> timeout value appropriately. I've attached a patch for 1.2.6.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
