The threaded server uses one thread per connection. It does not get a request, and have an available thread process the request. This means that if you send 20 requests, and the 10th request takes a long time to process, the last ten requests will be stalled.
From: "Napolitano, Diane" <dnapolit...@ets.org> To: "user@thrift.apache.org" <user@thrift.apache.org>, Date: 04/05/2013 02:44 PM Subject: Question about Multithreaded Thrift Servers Hello, I have a Thrift server (just "NameOfServer" here) written in Java which is initialized with the following inside of an inner class called ServerThread: TThreadPoolServer.Args args = new TThreadPoolServer.Args(serverTransport); args.maxWorkerThreads(10); args.processor(processor); TServer server = new TThreadPoolServer(args); server.serve(); Then NameOfServer has two objects: public static NameOfServerHandler handler; public static NameOfServer.Processor processor; And then a ServerThread object is created in my server's main: handler = new NameOfServerHandler(); processor = new NameOfServer.Processor(handler); Runnable r = new ServerThread(processor, portNum); new Thread(r).start(); My question is: am I doing this right? Because when I send more than ten requests to the server, it throws an exception and dies, and all requests beyond the first 10 are stalled. Unless I'm misunderstanding threads, Java, and everything else, aren't these additional requests supposed to be queued and then served when one of the 10 threads becomes available? If you need more code/context than this, definitely let me know. Thanks, Diane
