Post reply

Receiving Error - [SQLServer 2000 Driver for JDBC]Object has been closed

  • January 22, 2010 at 12:33 pm

    #140902

    We have a Java web application that uses Connection Pooling and a JDBC driver to query a SQL 2000 database. We have been receiving the following message and Stack Trace more frequently recently. The errors seem to occur on long running queries where users put in a double wildcards. The table has multiple years of history in it, so it is rather large. When I ran this query and timed it, It took almost exactly 15 minutes before the page returned this error. Does anyone have any ideas as to what may be causing this.

    Thanks

    TJP8

    ERROR MESSAGE

    java.lang.Exception: Error running query 'SELECT TOP 1000 * FROM HC_ARP40H_V

    WHERE ([Company] LIKE '%ASCO%') ', Message: [Microsoft][SQLServer 2000 Driver for JDBC]Object has been closed.

    STACK TRACE

    com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)

    com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)

    com.microsoft.jdbc.base.BaseConnection.validateClosedState(Unknown Source)

    com.microsoft.jdbc.base.BaseStatement.validateClosedState(Unknown Source)

    com.microsoft.jdbc.base.BaseResultSet.validateClosedState(Unknown Source)

    com.microsoft.jdbc.base.BaseResultSetMetaData.validateClosedState(Unknown Source)

    com.microsoft.jdbc.base.BaseResultSetMetaData.getColumnType(Unknown Source)

    app.data.ApplicationDao.doSearch(ApplicationDao.java:211)

    app.controllers.ViewReport.doPost(ViewReport.java:138)

    javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

    javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    core.app.controllers.ApplicationAlertFilter.doFilter(ApplicationAlertFilter.java:92)

    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    core.app.controllers.SessionCheckFilter.doFilter(SessionCheckFilter.java:52)

    org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

    org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

    org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)

    org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

    org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

    org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

    org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

    org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)

    org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

    org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

    org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)

    java.lang.Thread.run(Thread.java:735)

  • January 26, 2010 at 6:47 am

    #1108625

    One More piece of information. At times we have had all connections in the connection pool busy at the same time, does anyone know what happens when it runs out of connections and gets another request?

    TJP8

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply