COM.ibm.db2.jdbc.DB2Exception: CLI0600E Invalid connection handle or connection is closed. SQLSTATE=S1000

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

Do you know how to solve this issue? Write a tip to help other users and build your expert profile.

Solutions on the web

via ibm.com by Unknown author, 1 year ago
CLI0600E Invalid connection handle or connection is closed. SQLSTATE=S1000
COM.ibm.db2.jdbc.DB2Exception: CLI0600E Invalid connection handle or connection is closed. SQLSTATE=S1000
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:601)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:460)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:233)
at com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java:180)
at com.wiree.dao.DAOUtils.getConnection(DAOUtils.java:83)
at components.DB.connect(DB.java:172)
at ian.Login.doPost(Login.java:187)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:787)
at ian.RapideBaseServlet.service(RapideBaseServlet.java:696)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:854)
at com.ibm.ws.webcontainer.servlet.SingleThreadModelServlet.service(SingleThreadModelServlet.java:127)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:145)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:215)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:314)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:117)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:306)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:43)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:41)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:941)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:351)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:135)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:227)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:72)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:190)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:406)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:57)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:461)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:414)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:614)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:227)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:72)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:190)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:406)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:57)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:614)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.