Affects Version/s: 0.12.0
Fix Version/s: None
Python 3 Thrift Client
Java Thrift Server
File Transport using Named Pipes
TJSONProtocol | TBinaryProtocol
Starting with Python tutorial from https://thrift.apache.org/tutorial/py
Switch the transport layer from sockets to Named Pipes using:
Then use many body of py tutorial to verify Name Pipes work in sunny day cases, then (before closing the transport):
The exceptions generated are one of the following:
Depending if you are using JSON or Binary protocol.
After both cases, the communication layer is unusable even if the exception is caught.
Is it possible to recover the communication layer after a Type Error?
Or have Thrift verify|check the types before it tries to put the call into the communication layer?
I would like to avoid restarting the client-server relationship if possible.
I assume the issue is on the Python Client side, however I've also noticed that when using the JSON protocol that some type errors can actually break the named pipe on the Java Server side.
I've also noticed that negative numbers (i64) can cause problems, but suspect that issue is actually unrelated (and only happens with Binary protocol), but mentioning it just in case.
Any help or advice would be greatly appreciated! Thanks!