Closed aaujayasena closed 4 weeks ago
@aaujayasena Can this be reproduced always ? If so we can try to drop long running connections and see whether there's a connection leak
@omindu This is a intermittent issue and error reported percentage is nearly 0.04% . Heap size: 2G No of cores : 4 cores Concurrency users: 500 So your proposing to execute long running test with 500 concurrency or create a peak time of 500 concurrency in the middle of long running execution?
@aaujayasena I'm proposing to execute long running test with 500 concurrency and check for connection leaks.
Also, what's the maxActive connection count for identity data source ?
@omindu maxActive connection count is 300
We should increase the connection count for IDN DB to 500
This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!
product version: 5.8.0 /5.6.0 Severity: medium Priority: high
Exception, 'PoolExhaustedException' found in the performance test execution for 500 concurrency in below scenarios.
DB: mysql OS: ubuntu
Issue is linked with issue [1]
[1] https://github.com/wso2/product-is/issues/1830 [2] https://stackoverflow.com/questions/29368032/tomcat-connection-pool-exhausted