java.io.IOException

Couldn't get connection because we are at maximum connection count (10/10) and there are none available

Solutions on the web10477

  • Couldn't get connection because we are at maximum connection count (10/10) and there are none available
  • Couldn't get connection because we are at maximum connection count (10/10) and there are none available
  • via quickfixj.org by Unknown author, 10 months ago
    Couldn't get connection because we are at maximum connection count (10/10) and there are none available
  • Stack trace

    • java.io.IOException: Couldn't get connection because we are at maximum connection count (10/10) and there are none available at quickfix.JdbcStore.storeSequenceNumbers(JdbcStore.java:286) at quickfix.JdbcStore.setNextTargetMsgSeqNum(JdbcStore.java:272) at quickfix.JdbcStore.incrNextTargetMsgSeqNum(JdbcStore.java:173) at quickfix.SessionState.incrNextTargetMsgSeqNum(SessionState.java:359) at quickfix.Session.next(Session.java:799) at quickfix.mina.ThreadPerSessionEventHandlingStrategy$MessageDispatchingThread.run(ThreadPerSessionEventHandlingStrategy.java:85) Caused by: java.sql.SQLException: Couldn't get connection because we are at maximum connection count (10/10) and there are none available at org.logicalcobwebs.proxool.Prototyper.quickRefuse(Prototyper.java:309) at org.logicalcobwebs.proxool.ConnectionPool.getConnection(ConnectionPool.java:152) at org.logicalcobwebs.proxool.ProxoolDataSource.getConnection(ProxoolDataSource.java:97) at quickfix.JdbcStore.storeSequenceNumbers(JdbcStore.java:279) ... 5 more

    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

    4 times, 1 month ago