Ok guys, we are at a loss here and hoping you may shed some light on this total show stopper!
We are using CQL v. 1.0.5 and are experiencing problems using jdbc pooling from a thrift server.
In our Core module, we have import jobs and calculation jobs using the thread pool without problems, reading and writing tens of thousands of records lightning fast.
However; we are also using a Server module (based on org.apache.thrift.server.TServer) which is in turn using the same code from Core for connections to Cassandra. When we use this server, it seems connections are not released and reused, but the pool is constantly growing until reaching a roof at <16.000 connections, after which we get a
Error in thread "Thread-3"
message on the server, and a timeout on the client.
What beats us is why this works fine when running the import and calculation jobs, but not when the same dao classes are used from the server (imported as a maven artifact).
Any ideas whatsoever would be greatly appreciated!