We are using a Servlet/JSP/Struts/Tomcat package for our web application. We have a number of servlets that start off by getting a connection to a MSSQL 7.0 Database via Tomcat connection pooling in the execute method of the Action Servlet.. Our database driver of choise is the Free TDS driver. The connection is passed to several Data Access Bean methods which perform all of our interaction with the DB. In our finally block, the connection is closed and set to null. When we have concurrent users it seems that when one instance of the servlet closes its connection, the other instance's connection is also closed or so it appears. At some point in the servlets life cycle we get a connection closed error. It does not happen every time. We can go 10 times without seeing it before it pops up and it doesn't pop up in the same place.
I've searched the list but haven't found any matches to this particular problem. Can anyone point us in the right direction. Thanks, Jon ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
