Re: AW: Tomcat 5.5.9 connection pooling
Hi Peter, i've had this problem in a project long ago. I left the company befor i solved this, but meanwhile i am quite sure this was not a problem of Tomcat, but of using ResultSet wrong. Maybe this is your problem too. ResultSet is a connection to the database- if you iterate over ResultSet when the connection has allready be closed you get this error. Check for this errors: db.getConnection(); ResultSet rs = Statement... db.closeConnection(): while(rs.hasNext()) Hope this helps, Chris [EMAIL PROTECTED] wrote: Here is the exception that is thrown. As you can see my connection seems to be already closed. But why? Can this be configured somewhere? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat 5.5.9 connection pooling
Here is the exception that is thrown. As you can see my connection seems to be already closed. But why? Can this be configured somewhere? -Ursprüngliche Nachricht- Von: Viorel Dragomir [mailto:[EMAIL PROTECTED] Gesendet: Montag, 18. Juli 2005 14:46 An: Tomcat Users List Betreff: Re: Tomcat 5.5.9 connection pooling Can you attach the exception thrown ? Viorel Dragomir . .. --- - Original Message - From: [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Monday, July 18, 2005 13:38 Subject: Tomcat 5.5.9 connection pooling Hi! I am using Tomcat 5.5.9 and I have established a DataSource for database connection pooling where I can get connections from. But when I try to close the connection via myConnection.close(), always an exception is thrown. Is it right to close the connection this way or do I have to return the connection to the pool in another way? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] java.sql.SQLException: Connection is closed. at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.checkOpen(PoolingDataSource.java:174) at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:179) at com.materna.buc.buildmanager.database.impl.BMDatabaseHandlerImpl.getUserList(Unknown Source) at com.materna.buc.buildmanager.actions.CreateLoginAction.execute(Unknown Source) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.materna.buc.buildmanager.controller.BMRequestProcessor.processPreprocess(Unknown Source) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:184) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:693) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:660) at org.apache.struts.taglib.logic.ForwardTag.doForward(ForwardTag.java:121) at org.apache.struts.taglib.logic.ForwardTag.doEndTag(ForwardTag.java:105) at org.apache.jsp.index_jsp._jspx_meth_logic_forward_0(org.apache.jsp.index_jsp:88) at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:61) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:291) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at
Re: Tomcat 5.5.9 connection pooling
Can you please write what exception do you get when you try to close the database connection? - Original Message - From: [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Monday, July 18, 2005 4:38 PM Subject: Tomcat 5.5.9 connection pooling Hi! I am using Tomcat 5.5.9 and I have established a DataSource for database connection pooling where I can get connections from. But when I try to close the connection via myConnection.close(), always an exception is thrown. Is it right to close the connection this way or do I have to return the connection to the pool in another way? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 5.5.9 connection pooling
Can you attach the exception thrown ? Viorel Dragomir . .. --- - Original Message - From: [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Monday, July 18, 2005 13:38 Subject: Tomcat 5.5.9 connection pooling Hi! I am using Tomcat 5.5.9 and I have established a DataSource for database connection pooling where I can get connections from. But when I try to close the connection via myConnection.close(), always an exception is thrown. Is it right to close the connection this way or do I have to return the connection to the pool in another way? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5.5.9 connection pooling
Hi! I am using Tomcat 5.5.9 and I have established a DataSource for database connection pooling where I can get connections from. But when I try to close the connection via myConnection.close(), always an exception is thrown. Is it right to close the connection this way or do I have to return the connection to the pool in another way? Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]