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

James E. King, III resolved THRIFT-1849.
----------------------------------------
       Resolution: Not A Problem
    Fix Version/s: 0.9.3

I looked at the TSocket code and it is idempotent; if you call open() twice, 
the first call does something, and if the socket is open then the second open() 
call would simply return without an error.  I don't believe there is anything 
to do here and is behaving as designed, so I am resolving this not 
reproducible.  If you have an example that demonstrates the issue against the 
current master, please attach it and re-open the issue.

> after transport->open() throws its internal state set to "open", as result 
> isOpen returs true and next open() goes thru when it shall not
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-1849
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1849
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.9
>            Reporter: Igor Lesik
>            Assignee: James E. King, III
>             Fix For: 0.9.3
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Title tells it all.
> {noformat}
> m_rmt_socket = boost::shared_ptr<apache::thrift::transport::TSocket>
>        (new apache::thrift::transport::TSocket(m_rmt_socket_path));
> m_rmt_transport = boost::shared_ptr<apache::thrift::transport::TTransport>
>     (new apache::thrift::transport::TBufferedTransport(m_rmt_socket));
> m_rmt_protocol  = boost::shared_ptr<apache::thrift::protocol::TProtocol>
>     (new apache::thrift::protocol::TBinaryProtocol(m_rmt_transport));
> {noformat}
> I use Unix Domain sockets.
> Workaround: once thrown by transport->open exception is caught call 
> transport->close and then you can call transport->open again safely



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

Reply via email to