Recently I was testing my own custom APIs built over flowable engine 6.2. I was using Jmeter for testing. i was able to handle around 500 requests each of type
1)creating a user in idm,
2) initiating a process with some process variable
3) then submitting the form fields, validating that all fields with proper values are available and closing the task and in return quering the next user task and form attached to that task and sending it in response.
in ramp up time of 10 sec. But when i did the same for 1000 requestswith same rampup time, i started getting tomcat exceptions
Unable to acquire JDBC Connection Pool empty. Unable to fetch a connection in 30 seconds, none available[size:100; busy:100; idle:0; lastwait:30000].
when i hit the 3rd Api mentioned above.
This seems like a tomcat issue, but since we can configure the same setting in flowable database configuration also, so asking it here. Can someone tell me how i can configure this( tomcat or flowable side) to handle the above load? Any leads will be appreciated.