You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Lukas Fittl (JIRA)" <ji...@apache.org> on 2011/04/12 12:30:05 UTC

[jira] [Created] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
-----------------------------------------------------------------------------------

                 Key: THRIFT-1140
                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
             Project: Thrift
          Issue Type: Bug
          Components: C glib - Library
    Affects Versions: 0.6.1
         Environment: Debian 6.0, 64-bit
            Reporter: Lukas Fittl


When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.

This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.

The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046868#comment-13046868 ] 

Hudson commented on THRIFT-1140:
--------------------------------

Integrated in Thrift #162 (See [https://builds.apache.org/job/Thrift/162/])
    

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>            Assignee: Lukas Fittl
>             Fix For: 0.7
>
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury closed THRIFT-1140.
---------------------------------

    Resolution: Fixed
      Assignee: Lukas Fittl

I just committed this to TRUNK.

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>            Assignee: Lukas Fittl
>             Fix For: 0.7
>
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury updated THRIFT-1140:
----------------------------------

    Fix Version/s: 0.7

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>             Fix For: 0.7
>
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018825#comment-13018825 ] 

Bryan Duxbury commented on THRIFT-1140:
---------------------------------------

This patch seems to make sense to me, but I'd love if you included some test code. Any chance you'd be willing to add that?

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Lukas Fittl (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Fittl updated THRIFT-1140:
--------------------------------

    Attachment: thrift-1140.patch

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>    Affects Versions: 0.6.1
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (THRIFT-1140) Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server

Posted by "Lukas Fittl (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/THRIFT-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukas Fittl updated THRIFT-1140:
--------------------------------

    Affects Version/s:     (was: 0.6.1)

> Framed Transport Client using C (Glib) Library hangs when connecting to Ruby Server
> -----------------------------------------------------------------------------------
>
>                 Key: THRIFT-1140
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1140
>             Project: Thrift
>          Issue Type: Bug
>          Components: C glib - Library
>         Environment: Debian 6.0, 64-bit
>            Reporter: Lukas Fittl
>         Attachments: thrift-1140.patch
>
>
> When using the C (Glib) library to connect using the framed transport and binary protocol to connect to a Ruby-based server, the connection just hangs during the write phase.
> This is due to a too big size being set in the Thrift header, so the server waits for 4 bytes more than are actually being sent.
> The same issue happens the other way around, when the server sends a response, but the client thinks it needs 4 more bytes of data.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira