java.sql.SQLException

Connection has already been closed.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web6155

  • Connection has already been closed.
  • via Coderanch by Piyush Jain, 8 months ago
    Connection has already been closed.
  • via Oracle Community by 967958, 2 weeks ago
    Connection has already been closed.
  • Stack trace

    • java.sql.SQLException: Connection has already been closed. at weblogic.jdbc.wrapper.PoolConnection.checkConnection(PoolConnection.java:62) at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:100) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:545) at COM.FutureTense.Servlet.JDBCTable.executeUpdate_trans_logic(JDBCTable.java:1382) at COM.FutureTense.Servlet.JDBCTable.executeUpdate_trans(JDBCTable.java:1357) at COM.FutureTense.Servlet.JDBCTable.executeUpdate(JDBCTable.java:1231) at COM.FutureTense.Servlet.JDBCTable.DeleteRow(JDBCTable.java:980) at COM.FutureTense.Common.ftDBTable.deleteRow(ftDBTable.java:1117) at COM.FutureTense.Cache.EHCacheInvalidationMemory.deleteInvalidationsBefore(EHCacheInvalidationMemory.java:255) at COM.FutureTense.Common.CacheServer._purgeInvalidationmemory(CacheServer.java:210) at COM.FutureTense.Common.CacheServer.flushPages(CacheServer.java:193) at COM.FutureTense.Common.CacheServer.execute(CacheServer.java:79) at COM.FutureTense.Servlet.FTServlet.doPost(FTServlet.java:61) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:821) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at com.fatwire.auth.RequestAuthenticationFilter.doFilter(RequestAuthenticationFilter.java:192) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:695) at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57) at com.fatwire.gst.foundation.httpstatus.HttpResponseStatusFilter.doFilter(HttpResponseStatusFilter.java:83) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago