John R Pierce wrote:
>>> Its my understanding from reading the prior threads on this that
>>> somewhere
>>> after jdbc 213 they moved the initial BEGIN to the first SQL Execute
>>> rather
>>> than immediately upon Connection.
>>>
>>
>> This change only occured in the 8.0 development branch, and not on the
>> 7.4
>> branch. I produced a patch and then current versions of the 7.4 jar
>> files
>> for people to try this out on their 7.4 servers, but no one ever got back
>> to me about it, ...
>
>
> I'm amazed... Sounds like noone is doing any serious work with JDBC,
> or only has short lived 'applet' kind of applications where long
> persistance connections aren't an issue.
[...]
Often, connection pools have a maximum connection lifetime (either
directly or indirectly via their replacement policy). So you may just
not see the problem at all in this case since you never have an idle
transaction open indefinitely.
I'm doing "serious work" with JDBC and the stable driver does have a
number of deficiencies. I've been fixing them as I encounter them -- I
suggest you try the current development driver as this is where I've
been doing my work. The development driver should be quite stable, it
just hasn't had as much real-world use as the stable driver has had.
We're using it in released versions of our software without problems.
-O