- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] Is there a maximum limit to a request that the HTTP trigger can accept?
Search via FAQ No.
NEW
[DataSpider Servista] Is there a maximum limit to a request that the HTTP trigger can accept?
I use the HTTP triggers and the web service triggers to create a process to receive requests from clients.
Multiple requests may be sent to us at once, but is there a limit to the requests that the HTTP triggers can accept? Also, if there is an upper limit, can I change it?
- Category :
Answer
■Specification
The HTTP triggers and the web service triggers execute scripts in response to the HTTP requests.
The number of the HTTP communication that can be received is limited by DataSpiderServer and up to 300 requests can be received.
Please note that up to 200 requests will be executed immediately upon the receipt. Subsequent requests (100 requests that are after the 200 requests) will be in wait states when it exceeds 200.
This upper limit is a specification of DataSpiderServer. (You cannot change it by environment settings, etc.) It is currently not possible to change this limit.
■Note
Besides the HTTP triggers and the web service triggers, the HTTP communication is also performed when logging into DataSpider Studio and ScriptRunner.
For this reason, the actual upper limit will be less than the above described.
Also, for the above reasons, if there are many requests of the HTTP communication by the HTTP trigger or Web service trigger, the login process such as DataSpider Studio may turn into a wait state and might take some time.
■Supplementary
If the number of the simultaneous HTTP communication connections has been reached, the following log is output to server.log only on the first time during the DataSpiderServer startup:
| ERROR | org.apache.tomcat.util.threads.ThreadPool | All threads (200) are currently running and waiting. Please increase maxThreads (200) or check the status of the servlet
If the number of requests received exceeds 300, the client will generate the following error:
java.net.ConnectException: Connection refused: connect