From what I can parse, Proxool is a connection pool for JDBC connections. This suggests that the problem is that your application is not using the connection pool correctly. Instead of calling close on operator objects, your code probably discards them and / or their parent connections. Proxool relies on finalizers to close the underlying objects implemented by the driver ... but this requires instances of Finalizer. It may also mean that you force the connection to open / close (real) database connections more often than necessary, and that would be bad for performance.
Therefore, I suggest that you check your code for missing ResultSet, Statement, and / or Connection objects and make sure that you close them in finally blocks.
Looking at a memory dump, I expect you to be worried about where 898 527 228 bytes go. The vast majority are stored by a Finalizer object whose id is 2aab07855e38 . If you still have a dump file, see what Finalizer means. This looks more problematic than Proxool objects.
Stephen C Dec 02 2018-11-11T00: 00Z
source share