> when I use disconnectTopool, should I be doing it like this:
>
> db_connection.deallocatestatements;
> db_connection.closetransactions;
> db_connection.disconnectTopool;
>
> Currently I am just doing the disconnectTopool and memory seems to
> be continually rising with just a few connections in the pool.
>
> Ideas/suggestions?

I'd swap the order of these statements.

db_connection.closetransactions;
db_connection.deallocatestatements;
db_connection.disconnectTopool;

This should release all resources for the connection handle.
Please let me know if the resource usage continues to rise.

Also, my statement handle caching could be a problem too. Set
CacheStatementHandles to false.

Jason Wharton