[jira] Commented: (THRIFT-522) TSocket::open not being called in some cases

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/THRIFT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717005#action_12717005 ] 

Todd Lipcon commented on THRIFT-522:
------------------------------------

According to tutorial/php/PhpClient.php it's expected that the user will call $transport->open(). Given that no one has changed this code in months, I don't think this is a regression.

> TSocket::open not being called in some cases
> --------------------------------------------
>
>                 Key: THRIFT-522
>                 URL: https://issues.apache.org/jira/browse/THRIFT-522
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (PHP)
>    Affects Versions: 0.2
>         Environment: CentOS 5.2, php 5.2.9, gcc toolchain, etc
>            Reporter: Max Hodak
>
> Service calls were failing with a "Uncaught exception 'TException' with message 'TSocket: Could not write X bytes <host>:<port>" error.  It turned out that TSocket::open was never being called, so $this->handle_ in TSocket::write wasn't a valid resource.  Adding self::open() to the end of the TSocket constructor fixed the problem, but I don't fully understand the logic flow up to that point given that in most circumstances the resource is created properly.  Where is TSocket::open() normally called?

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