Hello Maxime, I think it depends on the server. Threads consume memory and of course CPU. 10 req/sec is not a huge value, however if each request requires a thread to write a huge entity or an entity whose content is delivered slowly, the thread pool will be at a time full and unable to process incoming requests.
Best regards, Thierry Boileau > Maxime Bégnis a écrit : > > Hi again, > > We increased the maximum number of threads to 512, it seems to solve the > problem for good. > Is this number too high and may cause some other problem elsewhere? > > Thanks. > > Maxime Bégnis. > >> Hello, >> >> Thanks a lot for you answer. >> I'll keep you informed about the resolution of this problem(It didn't >> happen since a while). >> >> cheers. >> >> Maxime Bégnis >> >> Thierry Boileau a écrit : >> >> >>> Hello Maxime, >>> >>> when the connector is unable to process new request due to congestion, >>> it refuses them. >>> You can consider to increase the number of thread or connections. >>> You can have a look here for the available parameters: >>> http://www.restlet.org/documentation/snapshot/jse/engine/org/restlet/engine/http/connector/BaseHelper.html >>> >>> In order to set them, proceed as follow: >>> Server server = new Server(Protocol.HTTP, 8182); >>> component.getServers().add(server); >>> server.getContext().getParameters().add("maxTotalConnections", "50"); >>> >>> >>> I hope this will help you. >>> >>> Best regards, >>> Thierry Boileau >>> NB: at this time, we focused on the available features provided by the >>> framework. The first candidate release (which freezes the API) is >>> planned for mid-march. At this time, we will focus on bug and >>> performance issues. >>> >>> >>> >>>> Hi, >>>> >>>> We are using Restlet 2.0M7 with the default HTTP server. We have some >>>> kind of robot making a lot of HTTP requests(about 10/seconds) during, >>>> for big jobs, approximately 1 minute. Sometimes, when the server is busy >>>> with other requests(from users) during this big storm, the server fails >>>> with this log: >>>> >>>> Feb 4, 2010 1:56:31 PM org.restlet.engine.http.connector.BaseHelper$1 >>>> rejectedExecution >>>> WARNING: Unable to run the following server-side task: Read connection >>>> messages: true >>>> <#camil>Feb 4, 2010 1:56:31 PM >>>> org.restlet.engine.http.connector.BaseHelper$1 rejectedExecution >>>> <#camil>INFO: Worker service state: Full >>>> <#camil>Feb 4, 2010 1:56:31 PM >>>> org.restlet.engine.http.connector.BaseHelper$1 rejectedExecution >>>> <#camil>INFO: Worker service tasks: 0 queued, 255 active, 5500 >>>> completed, 5755 scheduled. >>>> <#camil> Feb 4, 2010 1:56:31 PM >>>> org.restlet.engine.http.connector.BaseHelper$1 rejectedExecution >>>> <#camil> INFO: Worker service thread pool: 1 core size, 255 largest >>>> size, 255 maximum size, 255 current size >>>> <#camil> Feb 4, 2010 1:56:31 PM >>>> org.restlet.engine.http.connector.ControllerTask run >>>> <#camil> INFO: Stop accepting new connections and transactions. Consider >>>> increasing the maximum number of threads. >>>> >>>> >>>> >>>> Do you know the reasons of this, what can be done? >>>> >>>> Thanks in advance. >>>> >>>> Maxime Bégnis. >>>> >>>> ------------------------------------------------------ >>>> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2444851 >>>> >>>> >>>> >>>> >> ------------------------------------------------------ >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2448670 >> >> >> > ------------------------------------------------------ > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2448761 > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2448793
