java.sql.SQLException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Customer reports seeing the following in the log: 2012-01-03 11:25:53,578 DEBUG [mondrian.server.Execution] mondrian.olap.MondrianException: Mondrian Error:An exception was encountered while trying to cleanup an execution context. A statement failed to cancel gracefully. Locus was : "Error while loading segment". java.sql.SQLException: org.apache.commons.dbcp.DelegatingStatement is closed. at org.apache.commons.dbcp.DelegatingStatement.checkOpen(DelegatingStatement.java:136) at org.apache.commons.dbcp.DelegatingStatement.cancel(DelegatingStatement.java:249) at mondrian.server.Execution.cleanStatements(Execution.java:147) at mondrian.server.Execution.end(Execution.java:168) at mondrian.server.StatementImpl.end(StatementImpl.java:98) at mondrian.rolap.RolapConnection.executeInternal(RolapConnection.java:644) at mondrian.rolap.RolapConnection.access$000(RolapConnection.java:52) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:586) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:585) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Note that "A statement failed to cancel gracefully" occurs when an MDX statement times out, and Mondrian tries to cancel the running SQL statements. In this case, it looks as if the statements have already finished, but Mondrian still tries to cancel them. I think this bug is harmless, but it points to problems in the SQL statement lifecycle management.
    via by Julian Hyde,
  • Customer reports seeing the following in the log: 2012-01-03 11:25:53,578 DEBUG [mondrian.server.Execution] mondrian.olap.MondrianException: Mondrian Error:An exception was encountered while trying to cleanup an execution context. A statement failed to cancel gracefully. Locus was : "Error while loading segment". java.sql.SQLException: org.apache.commons.dbcp.DelegatingStatement is closed. at org.apache.commons.dbcp.DelegatingStatement.checkOpen(DelegatingStatement.java:136) at org.apache.commons.dbcp.DelegatingStatement.cancel(DelegatingStatement.java:249) at mondrian.server.Execution.cleanStatements(Execution.java:147) at mondrian.server.Execution.end(Execution.java:168) at mondrian.server.StatementImpl.end(StatementImpl.java:98) at mondrian.rolap.RolapConnection.executeInternal(RolapConnection.java:644) at mondrian.rolap.RolapConnection.access$000(RolapConnection.java:52) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:586) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:585) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Note that "A statement failed to cancel gracefully" occurs when an MDX statement times out, and Mondrian tries to cancel the running SQL statements. In this case, it looks as if the statements have already finished, but Mondrian still tries to cancel them. I think this bug is harmless, but it points to problems in the SQL statement lifecycle management.
    via by Julian Hyde,
  • Grails maxRows/queryTimeout warning
    via Stack Overflow by ubiquibacon
    ,
  • Translation XML files are empty
    via openbravo by eisler
    ,
    • java.sql.SQLException: org.apache.commons.dbcp.DelegatingStatement is closed. at org.apache.commons.dbcp.DelegatingStatement.checkOpen(DelegatingStatement.java:136) at org.apache.commons.dbcp.DelegatingStatement.cancel(DelegatingStatement.java:249) at mondrian.server.Execution.cleanStatements(Execution.java:147) at mondrian.server.Execution.end(Execution.java:168) at mondrian.server.StatementImpl.end(StatementImpl.java:98) at mondrian.rolap.RolapConnection.executeInternal(RolapConnection.java:644) at mondrian.rolap.RolapConnection.access$000(RolapConnection.java:52) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:586) at mondrian.rolap.RolapConnection$1.call(RolapConnection.java:585) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662)

    Users with the same issue

    Unknown visitor1 times, last one,