-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 7/20/2011 4:59 PM, Mark Thomas wrote:
> On 20/07/2011 21:46, Christopher Schultz wrote:
>> Mark,
>>
>> On 7/20/2011 4:25 AM, Mark Thomas wrote:
>>> You need to de-register the driver you registered. However, that
>>> won't be causing the le
My personal advice with the Oracle driver is to put it at the server level, not
at the webapp level.
For instance if you use the query timeouts, oracle JDBC spawns a Thread to
handle the timeouts, and there is no way to properly stop this thread so tomcat
will continue complaining about leaking
On 20/07/2011 21:46, Christopher Schultz wrote:
> Mark,
>
> On 7/20/2011 4:25 AM, Mark Thomas wrote:
>> You need to de-register the driver you registered. However, that
>> won't be causing the leak since Tomcat already did the clean up for
>> you. Time to get the profiler out.
>
> Quick question:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 7/20/2011 4:25 AM, Mark Thomas wrote:
> You need to de-register the driver you registered. However, that
> won't be causing the leak since Tomcat already did the clean up for
> you. Time to get the profiler out.
Quick question: I get these
