You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Kyle Johnson (JIRA)" <ji...@apache.org> on 2016/04/19 01:44:25 UTC

[jira] [Updated] (THRIFT-3790) Fix Delphi named pipe client to use timeout even when pipe doesn't yet exist

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

Kyle Johnson updated THRIFT-3790:
---------------------------------
    Attachment: THRIFT-3790-fix-for-closing-and-reopening-client-pipe-connection.patch

Here is the patch that fixes the closing and immediate reopening issue exposed by the Delphi test client.  This causes the entire timeout to be used in attempting to connect to the named pipe server, even if the pipe hasn't yet been created by the server.

> Fix Delphi named pipe client to use timeout even when pipe doesn't yet exist
> ----------------------------------------------------------------------------
>
>                 Key: THRIFT-3790
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3790
>             Project: Thrift
>          Issue Type: Bug
>          Components: Delphi - Library
>    Affects Versions: 1.0
>            Reporter: Kyle Johnson
>            Priority: Minor
>         Attachments: THRIFT-3790-fix-for-closing-and-reopening-client-pipe-connection.patch
>
>
> In the Delphi test code, the test client closes the connection and then immediately reopens it.  However, it takes a small amount of time for the server to tear down the connection and then rebuild it.  In that time, the client has issued an Open() call on the pipe client when the server hasn't yet recreated the pipe.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)