removeCatalog

Drops a database's catalog to prevent memory leaks if a connection (pool) pointing to dynamic URLs is closed.

In most standard backend applications, connection URLs are static and catalogs should not be dropped. However, if your application dynamically connects to and disconnects from thousands of different databases at runtime, you should call this method upon closing the data source to allow the JVM Garbage Collector to free the catalog.

A connection still open when this is called keeps the catalog it had until it closes: its sessions read that one, register into it and reload it. Connections opened afterwards read the database's types afresh, with nothing registered.

Parameters