You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Max Hodak (JIRA)" <ji...@apache.org> on 2009/06/07 04:42:07 UTC
[jira] Created: (THRIFT-522) TSocket::open not being called in some
cases
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.
[jira] Commented: (THRIFT-522) TSocket::open not being called in
some cases
Posted by "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.
[jira] Closed: (THRIFT-522) TSocket::open not being called in some
cases
Posted by "Max Hodak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Hodak closed THRIFT-522.
----------------------------
Resolution: Invalid
Not a bug.
> 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.
[jira] Issue Comment Edited: (THRIFT-522) TSocket::open not being
called in some cases
Posted by "Max Hodak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717006#action_12717006 ]
Max Hodak edited comment on THRIFT-522 at 6/6/09 7:46 PM:
----------------------------------------------------------
You're right. Missed the $transport->open() call.
was (Author: maxh):
Not a bug.
> 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.