This is happening as the slow responding service keeps a worker thread from the web server thread pool busy ... present in servlet API that would allow for asynchronous delivery of data to the client.

The studio aims to help developers with multiplayer implementation and design. This can include dealing with server/client architecture, working on synchronous or asynchronous multiplayer and rolling ...

and we need one request per client, thread exhaustion in the application server can occur very quickly. The Java EE specification is poised to address this problem in the Servlet 3.0 specification ...