rhtyd opened a new issue #3987: Exception in long running Java11/MySQL8 management server URL: https://github.com/apache/cloudstack/issues/3987 For a long-running Java11 management server (based on simulator) running latest master/4.14 with mysql 8.x library the following was seen: http://primate-qa.cloudstack.cloud:8080/client/ ``` 2020-03-24 00:50:17,751 ERROR [c.c.u.d.T.Transaction] (Network-Scavenger-1:ctx-7e038324) (logid:eee53f1b) Unexpected exception: java.sql.SQLException: Cannot get a connection, pool error Timeout waiting for idle object at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:142) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnectionWithException(TransactionLegacy.java:213) at com.cloud.utils.db.TransactionLegacy.getStandaloneConnection(TransactionLegacy.java:222) at com.cloud.utils.db.DbUtil.getConnectionForGlobalLocks(DbUtil.java:61) at com.cloud.utils.db.DbUtil.getGlobalLock(DbUtil.java:199) at com.cloud.utils.db.GlobalLock.lock(GlobalLock.java:154) at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$NetworkGarbageCollector.runInContext(NetworkOrchestrator.java:2887) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.util.NoSuchElementException: Timeout waiting for idle object at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:439) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:349) at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:134) ``` This could hint at an potential long running GC/leak issue or could be solely env issue (in which case could be closed). ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Management server ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ master/4.14-snapshot ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
