On 22.11.2013, at 02:20, Christopher Schultz
wrote:
>> I also think that this is a justifiable spec violation, and all I’m
>> asking is that this fact is shown more prominently, esp. as JDBC
>> pool is advertised as a drop-in replacement for DBCP.
>
> Fair enough. Care you file a documentation b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 11/21/13, 2:18 AM, Rainer Frey (Inxmail GmbH) wrote:
>
> On 20.11.2013, at 14:21, Christopher Schultz
> wrote:
>
>> Rainer, FWIW, Connection.close also states this:
>>
>> " Releases this Connection object's database and JDBC resources
On 20.11.2013, at 14:21, Christopher Schultz
wrote:
> Rainer,
> FWIW, Connection.close also states this:
>
> "
> Releases this Connection object's database and JDBC resources
> immediately instead of waiting for them to be automatically released.
> "
>
> Does that mean that all connection poo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rainer,
On 11/20/13, 2:36 AM, Rainer Frey (Inxmail GmbH) wrote:
>
> On 19.11.2013, at 14:45, Mark Thomas wrote:
>
>> On 19/11/2013 13:32, Carl Boberg wrote:
>>
>>> I have here an example of the way we close from the
>>> application, (the devs ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Carl,
A late reply, but I believe you have some problems with your code.
Mark's comments about Tomcat-pool indicate that certain sloppy
resource-management activities may leave resources open on the server,
and I'm fairly sure that, given the code y
On 19.11.2013, at 14:45, Mark Thomas wrote:
> On 19/11/2013 13:32, Carl Boberg wrote:
>
>> I have here an example of the way we close from the application, (the devs
>> have named it dispose). From my untrained non java dev eye we do not seem
>> to be doing statement.Close(); and Im curious if
On Nov 19, 2013, at 8:32 AM, Carl Boberg wrote:
> Thanks for taking the time Daniel,
>
> It is very hard to explain the problem since, and it was also stupid of me
> to not include the fact that I have tried all kinds of similar combinations
> of configuration in context.xml. With botch dbcp and
On 19/11/2013 13:32, Carl Boberg wrote:
> I have here an example of the way we close from the application, (the devs
> have named it dispose). From my untrained non java dev eye we do not seem
> to be doing statement.Close(); and Im curious if that might be the issue?
> If so, why does DBCP handle
Thanks for taking the time Daniel,
It is very hard to explain the problem since, and it was also stupid of me
to not include the fact that I have tried all kinds of similar combinations
of configuration in context.xml. With botch dbcp and jdbc pools
The behaviour persists. For example these are on
On Nov 18, 2013, at 9:48 AM, Carl Boberg wrote:
> Hello,
>
> We have recently migrated from dbcp pool to the newer tomcat-jdbc pool. As
> I understand, it is supposed to be almost a "drop in replacement" for dbcp.
*Almost* is the key word here. It's very similar, but there are differences
(ty
Hello,
We have recently migrated from dbcp pool to the newer tomcat-jdbc pool. As
I understand, it is supposed to be almost a "drop in replacement" for dbcp.
Everything works great except once small thing. Its a bit difficult for me
to explain but our DBA is really annoyed by it...
With the new
11 matches
Mail list logo
