river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Jones (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (RIVER-223) test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout fails on Linux
Date Tue, 08 Apr 2008 01:15:24 GMT

     [ https://issues.apache.org/jira/browse/RIVER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Peter Jones resolved RIVER-223.

    Resolution: Cannot Reproduce

It appears that this issue was already fixed in the originally-contributed version of this

> test: jtreg/net/jini/jeri/tcp/connectTimeout/TestConnectTimeout fails on Linux
> ------------------------------------------------------------------------------
>                 Key: RIVER-223
>                 URL: https://issues.apache.org/jira/browse/RIVER-223
>             Project: River
>          Issue Type: Bug
>          Components: other
>    Affects Versions: jtsk_2.1
>         Environment: Linux only
>            Reporter: Thomas Vinod Johnson
>            Assignee: Peter Jones
>            Priority: Minor
>             Fix For: AR2
> Bugtraq ID [6391265|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391265]
> The failure of TestConnectTimeout (Linux only, both RH AS3 & SuSE 9.1) are test problems:
the test is assuming that a call to a certain bogus address will hang for a while, but it
fails quickly with a NoRouteToHostException on those platforms.
> Suggested Fix:
> Fixed by having the test use a socket factory that creates sockets that when a connect
timeout is specified, always simulates the appropriate timeout failure mode, even if the connect
attempt would have failed for some other reason like NoRouteToHostException.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message