Hi,
Does anyone know if there is a default/max number of threads that are
spawned to handle incoming requests? we are seeing a pattern where if there
are too many client requests being made, then the following error occurs on
the client and the api server doesnt even see the corresponding request.
are there any best practices around connection pooling or using the right
threadpool server to address this scenario?

No version identifier, old protocol client?
/usr/local/rvm/gems/ruby-1.9.3-p0/gems/thrift-0.6.0/lib/
thrift/protocol/binary_protocol.rb:122:in `read_message_begin'
/usr/local/rvm/gems/ruby-1.9.3-p0/gems/thrift-0.6.0/lib/thrift/client.rb:45:in
`receive_message'

thanks

Reply via email to