After restarting WAS 6.0.2.5, I get ConnectionWaitTimeoutException - Websphere

This is a discussion on After restarting WAS 6.0.2.5, I get ConnectionWaitTimeoutException - Websphere ; Hi, I have the following problem with WAS 6.0.2.5. on linux (don't know the linux version) Every time, after server restart, applications on server are not able to use connections from connection pool. I can find a lot of "*com.ibm.websphere.ce.cm.ConnectionWaitTimeoutExce ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: After restarting WAS 6.0.2.5, I get ConnectionWaitTimeoutException

  1. After restarting WAS 6.0.2.5, I get ConnectionWaitTimeoutException

    Hi,
    I have the following problem with WAS 6.0.2.5. on linux (don't know the linux version)
    Every time, after server restart, applications on server are not able to use connections from connection pool. I can find a lot of "*com.ibm.websphere.ce.cm.ConnectionWaitTimeoutExce ption: Connection not available, Timed out waiting for 1800xx*" exceptions. Connection pool is using DB2 Universal JDBC Driver Provider data source, and DB2 v8.1.1.88 database. After some time, applications start to work normally without any intervention. Time period till applications normal work can be up to one hour.
    Within the application, connections are regularly closed. Server is not in cluster. Database doesn't have performance issues. There are about 300 users.
    Here are data source properties:
    Connection timeout: 180 seconds
    Maximum connections: 20 connections
    Minimum connections: 1 connections
    Reap time: 180 seconds
    Unused timeout: 1800 seconds
    Aged timeout: 0 seconds
    Purge policy: EntirePool

    Here is a log snippet:
    com.ibm.websphere.ce.cm.ConnectionWaitTimeoutExcep tion: Connection not available, Timed out waiting for 180015
    at com.ibm.ws.rsadapter.AdapterUtil.toSQLException(Ad apterUtil.java:1146)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConn ection(WSJdbcDataSource.java(Compiled Code))
    at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConn ection(WSJdbcDataSource.java(Compiled Code))
    ...
    at sun.reflect.GeneratedMethodAccessor1204.invoke(Unk nown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java(Compiled Code))
    at java.lang.reflect.Method.invoke(Method.java(Compil ed Code))
    at org.springframework.ejb.access.LocalSlsbInvokerInt erceptor.invoke(LocalSlsbInvokerInterceptor.java(C ompiled Code))
    at org.springframework.aop.framework.ReflectiveMethod Invocation.proceed(ReflectiveMethodInvocation.java (Compiled Code))
    at org.springframework.aop.framework.JdkDynamicAopPro xy.invoke(JdkDynamicAopProxy.java(Compiled Code))
    at $Proxy1.processRequest(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor1204.invoke(Unk nown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java(Compiled Code))
    at java.lang.reflect.Method.invoke(Method.java(Compil ed Code))
    at org.springframework.aop.support.AopUtils.invokeJoi npointUsingReflection(AopUtils.java:284)
    at org.springframework.aop.framework.JdkDynamicAopPro xy.invoke(JdkDynamicAopProxy.java(Compiled Code))
    at $Proxy1.processRequest(Unknown Source)
    at sun.reflect.GeneratedMethodAccessor1280.invoke(Unk nown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java(Compiled Code))
    at java.lang.reflect.Method.invoke(Method.java(Compil ed Code))
    at org.springframework.remoting.support.RemoteInvocat ion.invoke(RemoteInvocation.java:179)
    at org.springframework.remoting.support.DefaultRemote InvocationExecutor.invoke(DefaultRemoteInvocationE xecutor.java:32)
    at org.springframework.remoting.support.RemoteInvocat ionBasedExporter.invoke(RemoteInvocationBasedExpor ter.java:70)
    at org.springframework.remoting.support.RemoteInvocat ionBasedExporter.invokeAndCreateResult(RemoteInvoc ationBasedExporter.java:106)
    at org.springframework.remoting.httpinvoker.HttpInvok erServiceExporter.handleRequest(HttpInvokerService Exporter.java:78)
    at org.springframework.web.servlet.mvc.SimpleControll erHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:44)
    at org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:675)
    at org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:623)
    at org.springframework.web.servlet.FrameworkServlet.s erviceWrapper(FrameworkServlet.java:384)
    at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:353)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1282)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:673)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrappe r.handleRequest(CacheServletWrapper.java:89)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:1878)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:84)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:472)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:411)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCa llback.complete(HttpICLReadCallback.java:101)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.reque stComplete(WorkQueueManager.java(Compiled Code))
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attem ptIO(WorkQueueManager.java(Compiled Code))
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.worke rRun(WorkQueueManager.java(Compiled Code))
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worke r.run(WorkQueueManager.java(Compiled Code))
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava(Compiled Code))
    Caused by: com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutExce ption: Connection not available, Timed out waiting for 180015
    at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitF orConnection(FreePool.java:1297)
    at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(Po olManager.java(Compiled Code))
    at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrappe r(ConnectionManager.java(Compiled Code))
    at com.ibm.ejs.j2c.ConnectionManager.allocateConnecti on(ConnectionManager.java(Compiled Code))
    ... 49 more

    This problem happens every time after server restart, and sometimes, but rarely, during regular work. The problem always disappears without any intervention from WAS admins.
    Thanks in advance

    is.

  2. Re: After restarting WAS 6.0.2.5, I getConnectionWaitTimeoutException

    Is there a firewall in between ? Change Minimum connections to 0 or 10. Use TPV to gather info.

  3. Re: After restarting WAS 6.0.2.5, I getConnectionWaitTimeoutException

    There is no firewall in between. I will change minimum conn. parameter and trace connection pool. I will try also with TPV

+ Reply to Thread