You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Kevin Ballard (JIRA)" <ji...@apache.org> on 2008/07/11 02:01:31 UTC

[jira] Created: (THRIFT-75) While sending a message, if a struct serialization raises an exception, the transport should be closed

While sending a message, if a struct serialization raises an exception, the transport should be closed
------------------------------------------------------------------------------------------------------

                 Key: THRIFT-75
                 URL: https://issues.apache.org/jira/browse/THRIFT-75
             Project: Thrift
          Issue Type: Bug
          Components: Library (Ruby)
            Reporter: Kevin Ballard


If a struct contains a field with the wrong type (say, 5 in a string field), it will blow up while serializing. If this happens while sending a message, the client itself blows up. If this exception doesn't take down the application, the transport is now left in a state where half of a message has been written. If another message is then sent, the transport is flushed with a malformed message.

In this scenario, the client should close the transport if it encounters an error serializing the struct.

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

[jira] Assigned: (THRIFT-75) While sending a message, if a struct serialization raises an exception, the transport should be closed

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

Bryan Duxbury reassigned THRIFT-75:
-----------------------------------

    Assignee: Kevin Ballard

> While sending a message, if a struct serialization raises an exception, the transport should be closed
> ------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-75
>                 URL: https://issues.apache.org/jira/browse/THRIFT-75
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Ruby)
>            Reporter: Kevin Ballard
>            Assignee: Kevin Ballard
>         Attachments: 0001-rb-Ensure-the-transport-is-closed-if-an-exception-i.patch
>
>
> If a struct contains a field with the wrong type (say, 5 in a string field), it will blow up while serializing. If this happens while sending a message, the client itself blows up. If this exception doesn't take down the application, the transport is now left in a state where half of a message has been written. If another message is then sent, the transport is flushed with a malformed message.
> In this scenario, the client should close the transport if it encounters an error serializing the struct.

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

[jira] Updated: (THRIFT-75) While sending a message, if a struct serialization raises an exception, the transport should be closed

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

Kevin Ballard updated THRIFT-75:
--------------------------------

    Patch Info: [Patch Available]

> While sending a message, if a struct serialization raises an exception, the transport should be closed
> ------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-75
>                 URL: https://issues.apache.org/jira/browse/THRIFT-75
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Ruby)
>            Reporter: Kevin Ballard
>         Attachments: 0001-rb-Ensure-the-transport-is-closed-if-an-exception-i.patch
>
>
> If a struct contains a field with the wrong type (say, 5 in a string field), it will blow up while serializing. If this happens while sending a message, the client itself blows up. If this exception doesn't take down the application, the transport is now left in a state where half of a message has been written. If another message is then sent, the transport is flushed with a malformed message.
> In this scenario, the client should close the transport if it encounters an error serializing the struct.

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

[jira] Closed: (THRIFT-75) While sending a message, if a struct serialization raises an exception, the transport should be closed

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

Kevin Clark closed THRIFT-75.
-----------------------------

    Resolution: Fixed

In r680538

> While sending a message, if a struct serialization raises an exception, the transport should be closed
> ------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-75
>                 URL: https://issues.apache.org/jira/browse/THRIFT-75
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Ruby)
>            Reporter: Kevin Ballard
>         Attachments: 0001-rb-Ensure-the-transport-is-closed-if-an-exception-i.patch
>
>
> If a struct contains a field with the wrong type (say, 5 in a string field), it will blow up while serializing. If this happens while sending a message, the client itself blows up. If this exception doesn't take down the application, the transport is now left in a state where half of a message has been written. If another message is then sent, the transport is flushed with a malformed message.
> In this scenario, the client should close the transport if it encounters an error serializing the struct.

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

[jira] Updated: (THRIFT-75) While sending a message, if a struct serialization raises an exception, the transport should be closed

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

Kevin Ballard updated THRIFT-75:
--------------------------------

    Attachment: 0001-rb-Ensure-the-transport-is-closed-if-an-exception-i.patch

> While sending a message, if a struct serialization raises an exception, the transport should be closed
> ------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-75
>                 URL: https://issues.apache.org/jira/browse/THRIFT-75
>             Project: Thrift
>          Issue Type: Bug
>          Components: Library (Ruby)
>            Reporter: Kevin Ballard
>         Attachments: 0001-rb-Ensure-the-transport-is-closed-if-an-exception-i.patch
>
>
> If a struct contains a field with the wrong type (say, 5 in a string field), it will blow up while serializing. If this happens while sending a message, the client itself blows up. If this exception doesn't take down the application, the transport is now left in a state where half of a message has been written. If another message is then sent, the transport is flushed with a malformed message.
> In this scenario, the client should close the transport if it encounters an error serializing the struct.

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