java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs).

QuickFIX/J JIRA | Vid Cheruvu | 6 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Hi, I have configured QuickFixJ to use JDBC store. In doing so, we have seen an issue with Proxool where it kills active thread that are longer than 5 minutes. We have no way to change the proxool's maximum-active-time property in Quickfixj configuration. When proxool kills the thread, QFJ failed to perform Scheduled Session reset. Please see the error log as shown below. 2010-12-18 09:32:07,312 WARN [HouseKeeper] HouseKeeper.sweep:149 - #0007 was active for 5559 milliseconds and has been removed automaticaly. Th e Thread responsible was named 'QFJ Timer', but the last SQL it performed is unknown because the trace property is not enabled. 2010-12-18 09:32:07,316 ERROR [QFJ Timer] SessionConnector$SessionTimerTask.run:257 - Error during timer processing quickfix.RuntimeError: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs). at quickfix.SessionState.reset(SessionState.java:373) at quickfix.Session.resetState(Session.java:2191) at quickfix.Session.reset(Session.java:759) at quickfix.Session.next(Session.java:1699) at quickfix.mina.SessionConnector$SessionTimerTask.run(SessionConnector.java:251) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) 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:619) Caused by: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection. It has bee n automatically closed by Proxool for some reason (see logs). at quickfix.JdbcStore.reset(JdbcStore.java:195) at quickfix.SessionState.reset(SessionState.java:370) ... 13 more Caused by: java.sql.SQLException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection. It has b een automatically closed by Proxool for some reason (see logs). at org.logicalcobwebs.proxool.WrappedConnection.invoke(WrappedConnection.java:207) at org.logicalcobwebs.proxool.WrappedConnection.intercept(WrappedConnection.java:87) at com.sybase.jdbcx.SybConnection$$EnhancerByProxool$$ace6c3d2.prepareStatement(<generated>) at quickfix.JdbcStore.reset(JdbcStore.java:187) ... 14 more Kind Regards, -Vid-

    QuickFIX/J JIRA | 6 years ago | Vid Cheruvu
    java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs).
  2. 0

    QuickFIX/J Jira

    quickfixj.org | 11 months ago
    quickfix.RuntimeError: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs).
  3. 0

    QuickFIX/J Jira

    quickfixj.org | 8 months ago
    quickfix.RuntimeError: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs).
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Hi, I have configured QuickFixJ to use JDBC store. In doing so, we have seen an issue with Proxool where it kills active thread that are longer than 5 minutes. We have no way to change the proxool's maximum-active-time property in Quickfixj configuration. When proxool kills the thread, QFJ failed to perform Scheduled Session reset. Please see the error log as shown below. 2010-12-18 09:32:07,312 WARN [HouseKeeper] HouseKeeper.sweep:149 - #0007 was active for 5559 milliseconds and has been removed automaticaly. Th e Thread responsible was named 'QFJ Timer', but the last SQL it performed is unknown because the trace property is not enabled. 2010-12-18 09:32:07,316 ERROR [QFJ Timer] SessionConnector$SessionTimerTask.run:257 - Error during timer processing quickfix.RuntimeError: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs). at quickfix.SessionState.reset(SessionState.java:373) at quickfix.Session.resetState(Session.java:2191) at quickfix.Session.reset(Session.java:759) at quickfix.Session.next(Session.java:1699) at quickfix.mina.SessionConnector$SessionTimerTask.run(SessionConnector.java:251) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) 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:619) Caused by: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection. It has bee n automatically closed by Proxool for some reason (see logs). at quickfix.JdbcStore.reset(JdbcStore.java:195) at quickfix.SessionState.reset(SessionState.java:370) ... 13 more Caused by: java.sql.SQLException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection. It has b een automatically closed by Proxool for some reason (see logs). at org.logicalcobwebs.proxool.WrappedConnection.invoke(WrappedConnection.java:207) at org.logicalcobwebs.proxool.WrappedConnection.intercept(WrappedConnection.java:87) at com.sybase.jdbcx.SybConnection$$EnhancerByProxool$$ace6c3d2.prepareStatement(<generated>) at quickfix.JdbcStore.reset(JdbcStore.java:187) ... 14 more Kind Regards, -Vid-

    QuickFIX/J JIRA | 6 years ago | Vid Cheruvu
    quickfix.RuntimeError: java.io.IOException: Couldn't perform the operation prepareStatement: You can't perform any operations on this connection . It has been automatically closed by Proxool for some reason (see logs).
  6. 0

    java , 数据库高手请进, 求解!

    sogou.com | 2 years ago
    org.hibernate.exception.GenericJDBCException: could not inspect JDBC autocommit mode
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.sql.SQLException

    Couldn't perform the operation prepareStatement: You can't perform any operations on this connection. It has b een automatically closed by Proxool for some reason (see logs).

    at org.logicalcobwebs.proxool.WrappedConnection.invoke()
  2. org.logicalcobwebs.proxool
    WrappedConnection.intercept
    1. org.logicalcobwebs.proxool.WrappedConnection.invoke(WrappedConnection.java:207)
    2. org.logicalcobwebs.proxool.WrappedConnection.intercept(WrappedConnection.java:87)
    2 frames
  3. com.sybase.jdbcx
    SybConnection$$EnhancerByProxool$$ace6c3d2.prepareStatement
    1. com.sybase.jdbcx.SybConnection$$EnhancerByProxool$$ace6c3d2.prepareStatement(<generated>)
    1 frame
  4. Apache ServiceMix :: Bundles :: ${pkgArtifactId}
    SessionConnector$SessionTimerTask.run
    1. quickfix.JdbcStore.reset(JdbcStore.java:187)
    2. quickfix.SessionState.reset(SessionState.java:370)
    3. quickfix.Session.resetState(Session.java:2191)
    4. quickfix.Session.reset(Session.java:759)
    5. quickfix.Session.next(Session.java:1699)
    6. quickfix.mina.SessionConnector$SessionTimerTask.run(SessionConnector.java:251)
    6 frames
  5. Java RT
    Thread.run
    1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    2. java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
    3. java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
    4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
    5. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
    6. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
    7. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    8. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    9. java.lang.Thread.run(Thread.java:619)
    9 frames