In RF v2.3 the internal HTTP server (based on JDK's basic HTTP server) now also contains a thread pool, so that might help. However, as pointed by Fabian, using a production ready connector such as Jetty is recommended for serious loads.
Jerome On Fri, Sep 26, 2014 at 12:24 PM, Fabian Mandelbaum <fmandelb...@gmail.com> wrote: > Hello, > > did you try adding one of the proven production-ready HTTP server > connector jars on your class-path? for example Jetty. We use Restlet with > Jetty HTTP(S) server connector in production without a problem and with > many concurrent clients accessing our server/services. > > > On Fri, Sep 26, 2014 at 3:33 PM, Audumbar Pujari <audumbarpuj...@gmail.com > > wrote: > >> Scenario : >> >> - >> >> I have implemented simple restlet server. >> - >> >> One client(RestClient / wget) or more than one client sending >> GET/POST requests to server at same time. (eg: wget >> http://mymachine.com:8182) >> >> Expected Behavior : >> >> - Server needs to handle all requests concurrently. >> >> Actual Behavior : >> >> - Server is handling all requests one by one (sequentially). >> >> Project link: >> >> I have created project on github. >> >> Link for project : https://github.com/paudumbar/TestRESTServer >> >> Am I missing any step in server creation? >> >> Thanks. >> >> Regards, >> >> Audumbar >> > > > > -- > Fabián Mandelbaum > IS Engineer > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3099824
