How about underlying connection pool? Imho one needs to close connection
On 10/5/07, Larry Meadors <[EMAIL PROTECTED]> wrote:
>
> As with anything, you can set them to null just to be safe - if you do
> that, the GC *may* get them sooner than if you don't.
>
> If you don't set them to null, they'
As with anything, you can set them to null just to be safe - if you do
that, the GC *may* get them sooner than if you don't.
If you don't set them to null, they'll remain referenced by the
containing object and not be collectible until the containing objects
are destroyed by the GC, which is kind
We have an application that has a ServletContextListener that creates
three SqlMapClients in the contextInitialized. When the application is
shutting down(in the contextDestroyed) should we just null out those
SqlMapClient or does it matter.
Called from the contextDestroyed
public static v
