DevPartner Java Memory Analysis and Connection Pooling



If I am performing memory analysis, and I have closed a connection to the database, but am using connection pooling so that the object is still in memory, would DevPartner report that as a memory leak?


In an object pooling or connection pooling type scenario, if the application was properly warmed up then no objects will be allocated during the processing of the request. So DPJ would not show the pooled connection as a leak. They key is warming up the connection pool properly - if you forget to warm it up and it needs to create a new connection to service the request then that new connection *will* be reported as a leak.

Old KB# 11244
Comment List
Related Discussions