[QFJ-313] Couldn't get connection because we are at maximum connection count (10/10) and there are none available Created: 29/May/08  Updated: 15/Nov/12  Resolved: 17/Jun/08

Status: Closed
Project: QuickFIX/J
Component/s: None
Affects Version/s: 1.3.1
Fix Version/s: None

Type: Other Priority: Default
Reporter: Kanupriya Dhingra Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Windows XP
S/W : JAVA1.5



 Description   

Hi,

I am trying to use JDBC log Factory. In Acceptor configuration file, i am using 5 FIX versions(4.0 to 4.4) . I used JDBC store factory. it is working properly, But while logging in Jdbc it gives me error, maximum connection count has reached, there r none connection available.... If I tries to log with Single FIX version in Acceptor coniguration, it works fine. is there any limitation on the number of connections?

Following is expection trace for your reference...

JdbcLog cannot log SQLException due to recursive log errors!
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:158)
at org.logicalcobwebs.proxool.ProxoolDataSource.getConnection(ProxoolDataSource.java:97)
at quickfix.JdbcLog.insert(JdbcLog.java:147)
at quickfix.JdbcLog.onEvent(JdbcLog.java:119)
at quickfix.CompositeLog.onEvent(CompositeLog.java:79)
at quickfix.Session.<init>(Session.java:348)
at quickfix.DefaultSessionFactory.create(DefaultSessionFactory.java:159)
at quickfix.mina.acceptor.AbstractSocketAcceptor.createSessions(AbstractSocketAcceptor.java:254)
at quickfix.mina.acceptor.AbstractSocketAcceptor.<init>(AbstractSocketAcceptor.java:83)
at quickfix.mina.acceptor.AbstractSocketAcceptor.<init>(AbstractSocketAcceptor.java:100)
at quickfix.ThreadedSocketAcceptor.<init>(ThreadedSocketAcceptor.java:32)

Please reply as soon as possible.
Thanks and Regards,
Kanupriya.



 Comments   
Comment by Steve Bate [ 17/Jun/08 ]

There have been a few reports of this in the past, but it's very uncommon. If I remember correctly, it may have been related to a specific JDBC driver, but I'm not sure.

Generated at Sat May 04 15:39:52 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.