You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Dmitry Murashenkov (JIRA)" <ji...@apache.org> on 2009/12/08 16:46:18 UTC
[jira] Commented: (OPENEJB-1110) Lookup timeout setting for
HttpConnection
[ https://issues.apache.org/jira/browse/OPENEJB-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787510#action_12787510 ]
Dmitry Murashenkov commented on OPENEJB-1110:
---------------------------------------------
Further testing has shown that invoking setConnectTimeout is not enough. Also setReadTimeout should be used to set read timeout.
In synthetic test cases when target destination is blocked by firewall - connect simply fails after connect timeout. But in case when target destination is disabled by turning network interface off - connect seems to succeed and lookup process gets stuck on socket.read(). Setting concrete non-zero read timeout eliminates this problem.
> Lookup timeout setting for HttpConnection
> -----------------------------------------
>
> Key: OPENEJB-1110
> URL: https://issues.apache.org/jira/browse/OPENEJB-1110
> Project: OpenEJB
> Issue Type: New Feature
> Components: connectors
> Affects Versions: 3.1.2
> Reporter: Dmitry Murashenkov
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> There is no ability to configure lookup timeout setting. This sometimes leads to lookup() getting stuck for a indeterminate amount of time in case of remote server is non-reachable.
> For HttpConnection setConnectTimeout() may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.