You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2010/09/14 17:32:33 UTC
[jira] Issue Comment Edited: (AVRO-664) Ruby server takes a long
time to start in interop tests
[ https://issues.apache.org/jira/browse/AVRO-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909220#action_12909220 ]
Thiruvalluvan M. G. edited comment on AVRO-664 at 9/14/10 11:31 AM:
--------------------------------------------------------------------
Thanks Doug for reviewing the patch.
Increasing from 1 second time-out previously to 60 seconds in the patch appears too excessive. As Doug pointed out some serious problems may go unnoticed. I set the limit to 10 seconds in steps of 1-second and then committed revision 996877.
was (Author: thiru_mg):
Committed revision 996877.
> Ruby server takes a long time to start in interop tests
> -------------------------------------------------------
>
> Key: AVRO-664
> URL: https://issues.apache.org/jira/browse/AVRO-664
> Project: Avro
> Issue Type: Bug
> Components: ruby
> Affects Versions: 1.4.0
> Environment: Ubuntu Lucid Lynx
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.4.1
>
> Attachments: AVRO-664.patch
>
>
> The ruby server uses a wrong key in the config (:Host instead of :BindAddress) which cause Socket::getaddrinfo() take up to 15 seconds. The shell script which starts the server waits for jist 1 second and test fails abruptly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.