harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruth Cao (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-2503) [classlib][net]ServerSocket refuses connection on after successful connection on localhost
Date Mon, 16 Apr 2007 08:59:15 GMT

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

Ruth Cao updated HARMONY-2503:

    Attachment: Harmony-2503-2.diff

No, the issue still exists. It passes just because the exception is thrown in a client thread
rather than the main thread of the test case. Thus, the test case passes but prints the stack
trace in the console. 

I'll upload a new patch to fix it. Would you pls check it again? Thanks.

> [classlib][net]ServerSocket refuses connection on after successful connection
on localhost
> --------------------------------------------------------------------------------------------------
>                 Key: HARMONY-2503
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2503
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: WinXP
>            Reporter: Nikolay Kuznetsov
>         Assigned To: Nathan Beyer
>         Attachments: Harmony-2503-2.diff, Harmony-2503.diff, test.java
> ServerSocket listening on (any_address) refuses connection to if prior
to this successful connection was established on localhost:8080 inside same JVM i.e. the following
sequence of accept/connect actions results in Connection Refused exception
> ServerSocket(localhost:8080).accept()
> Socket.connect(localhost:8080
> ServerSocket(0:8080).accept()
> Socket.connect(0:8080) -> Connection refused
> while reverse set of actions(first connect to 0 and localhost afterwards) works fine:
> ServerSocket(0:8080).accept()
> Socket.connect(0:8080) 
> ServerSocket(localhost:8080).accept()
> Socket.connect(localhost:8080)
> RI works fine in both cases, attached test demonstrates this problem.

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

View raw message