Hi Thaluru, As I looked into the source code, python TNonblockingServer is written based on an assumption that is valid for raw sockets but does not hold for SSL sockets. A good news is that I could easily fix this issue https://issues.apache.org/jira/browse/THRIFT-3938 <https://github.com/nsuke/thrift/commit/e0e108cf72c48adf98715abd5ac042be26798239> https://github.com/apache/thrift/pull/1100
I'll submit this with some automated tests enabled on CI later, but note that as our next release process is already in progress (many thanks to Jake !), it's not likely that the next release have this patch. Still it would be great if you could test this patch with your use case. Aki On Wed, Sep 28, 2016 at 10:07 AM Thaluru Divya <[email protected]> wrote: > Hi, > > I am currently using Python Thrift 0.9.3. > > I have created Python nonblocking ssl server and Python blocking ssl > client. > And my client is not able to receive data from server, even though I see > server writing response to client. This scenario works for me if I turned > off ssl in server as well as client. And I also see, ssl testing is turned > off for non blocking server. Is there any particular reason, why this is > turned off? > > Is this scenario is supported in Thrift? > > > Thanks > Divya >
