TApplicationException: Missing result

[JennyHui]

using thriftpy in my test code, in server the log has return the result but raise this 'TApplicationException: Missing result'

[lxyu]

@JennyHui may you please provide a detailed reproduce script or steps?

[JennyHui]

@lxyu here ~

fake code:

1. set up the test data

YODA_THRIFT = thriftpy.load(dirname+"/resource/thrift/yoda.thrift", module_name="yoda_thrift")
client = make_client(config.YODA_THRIFT.YodaService, config.THRIFT_HOST, config.THRIFT_PORT)
direct_strategy = YODA_THRIFT.DirectStrategy() //the struct

1. testing

result = client.create_direct_strategy(direct_strategy)

i've run a lot of time of this, and some of time it works but most of the time the "result" just turn out to be error:

query_grids_contain_point_result(system_exception=None, user_exception=None, success=None, unknown_exception=None) // print this result 
Error
Traceback (most recent call last):
  File "/Users/jennyhui/PycharmProjects/ClairSoaClient/lib/python2.7/site-packages/thriftpy/thrift.py", line 160, in _req
    return self._recv(_api)
  File "/Users/jennyhui/PycharmProjects/ClairSoaClient/lib/python2.7/site-packages/thriftpy/thrift.py", line 197, in _recv
    raise TApplicationException(TApplicationException.MISSING_RESULT)
TApplicationException: Missing result

[lxyu]

You're calling create_direct_strategy api and the traceback shows query_grids_contain_point_result api. It do not match.

Can you try to minimize the reproduce script and post one here?

[tonyzhu]

I get the same error.

[guangbaowan]

I get the same error.

[CanoeFZH]

I get the same error.

[ghost]

I get the same error.

[AlexKeepLearning]

I get the same error

[wooparadog]

Everybody here. Please provide detailed reproduction steps, including server and client code. We have also encountered this error, but all of those are network/server implantation related problems, well outside the scope of thriftpy.

And the client implementation in thriftpy is not ready for heavy production, please use github.com/eleme/thrift_connector instead.

[vEpiphyte]

And the client implementation in thriftpy is not ready for heavy production

@wooparadog Is there still a concern about the stability of the client implementation in thriftpy?

cc: @jnwatson

[wooparadog]

There's no problem with client implementation in thriftpy itself, just that it's too bare for production use. It's ok if your work load is not so great, but if it is, take a look at thrift connector(connection pool etc..)

On Wed, Aug 15, 2018 at 10:06 PM vEpiphyte [email protected] wrote:

And the client implementation in thriftpy is not ready for heavy production

@wooparadog https://github.com/wooparadog Is there still a concern about the stability of the client implementation in thriftpy?

cc: @jnwatson https://github.com/jnwatson

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eleme/thriftpy/issues/235#issuecomment-413208153, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFB6CeocTn48q8buPctEy9IlqTDQj3hks5uRCrXgaJpZM4JzhxP .