GitHub user muthukrishnang1100 edited a comment on the discussion: OOBM Issue during KVM HA
Yes, I tried all the things but still we get an same error. But this is my major issue now Caused by: java.sql.SQLException: Cannot get a connection, pool error Timeout waiting for idle object at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:147) at com.cloud.utils.db.TransactionLegacy.getConnection(TransactionLegacy.java:557) at com.cloud.utils.db.TransactionLegacy.prepareStatement(TransactionLegacy.java:468) ... 30 more Caused by: java.util.NoSuchElementException: Timeout waiting for idle object at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:446) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:356) at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:141) ... 32 more 2025-12-30 12:51:49,231 ERROR [c.c.s.StatsCollector] (StatsCollector-1:ctx-2c2139dd) (logid:e41447a0) Error trying to monitor autoscaling com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:433) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:362) at com.cloud.utils.db.GenericDaoBase.listIncludingRemovedBy(GenericDaoBase.java:960) at com.cloud.utils.db.GenericDaoBase.listBy(GenericDaoBase.java:939) at com.cloud.cluster.dao.ManagementServerHostDaoImpl.findOneInUpState(ManagementServerHostDaoImpl.java:270) at jdk.internal.reflect.GeneratedMethodAccessor284.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) at com.cloud.utils.db.TransactionContextInterceptor.invoke(TransactionContextInterceptor.java:34) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215) at com.sun.proxy.$Proxy161.findOneInUpState(Unknown Source) at com.cloud.server.StatsCollector$AutoScaleMonitor.runInContext(StatsCollector.java:1766) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) 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:829) Caused by: java.sql.SQLException: Cannot get a connection, pool error Timeout waiting for idle object at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:147) at com.cloud.utils.db.TransactionLegacy.getConnection(TransactionLegacy.java:557) at com.cloud.utils.db.TransactionLegacy.prepareStatement(TransactionLegacy.java:468) ... 30 more Caused by: java.util.NoSuchElementException: Timeout waiting for idle object at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:446) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:356) at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:141) ... 32 more 2025-12-30 12:51:49,240 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:ctx-8d4322d8) (logid:dcafa96b) Fail to complete the CheckRouterTask! com.cloud.utils.exception.CloudRuntimeException: DB Exception on: null at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:433) at com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:362) why this error comes sometimes again and again 1 or 2 days how to solve this permanantly what is exact problem for this. ------------------------------------------------------------------------------------------------------------------------------------------------- And also i found this for web some others really this is the cause? The Exact Problem: "The Silent Kill" The error Timeout waiting for idle object happens because of a 3-way conflict: CloudStack Pool: Keeps connections open in a "pool" to save time. It expects these to stay alive for hours. HAProxy (The Culprit): By default, HAProxy often has a timeout client and timeout server of 50 seconds. If a connection is idle for 51 seconds, HAProxy kills the "pipe" but doesn't tell CloudStack. The Error: When CloudStack finally tries to use that connection, it finds a "dead pipe." It then tries to get a new connection from the pool, but because so many connections are now in this "broken" state, the pool becomes exhausted, leading to the java.util.NoSuchElementException: Timeout waiting for idle object. Please check and give me exact solution GitHub link: https://github.com/apache/cloudstack/discussions/12353#discussioncomment-15423103 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
