Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #33962
| From | Andreas Leitgeb <avl@logic.at> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Troubles with informix jdbc driver ... |
| Date | 2016-03-14 21:30 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnneebi5.456.avl@login.logic.tuwien.ac.at> (permalink) |
| References | <slrnnedgqn.456.avl@login.logic.tuwien.ac.at> <nc76jq$ph$1@gwaiyur.mb-net.net> |
Marcel Mueller <news.5.maazl@spamgourmet.org> wrote:
> On 14.03.16 14.54, Andreas Leitgeb wrote:
>> A previous version of Informix jdbc ("3.70.JC5DE") was very
>> strict with "thread safety", in that it governed any connection
>> to any db server with a global lock. If one DB server was
>> temporarily unreachable, then it would block also connections
>> to any other db server (attempted from other threads).
> I would call this a bug.
So did I, and apparently so did IBM when they fixed that one ;-)
>> Some newer version of their jdbc driver (4.10.JC5) seems to
>> have that fixed, but we now observe that Connections obtained
>> from calling DriverManager.getConnection(...) casually get
>> mixed up!
> Sure that you did not introduce a race condition in your code?
How can one ever be sure about such a thing? ;-)
That's why I asked for others' experience.
My code wasn't changed for the new driver (I didn't even know they were
using a newer driver, until they started to report connection mixups.)
Never using static fields to hold jdbc-related objects, and never passing
such objects around from thread to thread makes me quite sure that the
mix up doesn't happen in my code, though.
> Did you write a test case that opens and verifies different connections
> concurrently?
We have such patterns happening in production. We had the same patterns
already with old driver, but that one's connect-lock might have covered
that particular bug (be it in our code or in the driver).
> If it fails you could contact the vendor.
I think our customers are already walking that path...
I just hoped for others reporting similar observations.
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Troubles with informix jdbc driver ... Andreas Leitgeb <avl@logic.at> - 2016-03-14 13:54 +0000
Re: Troubles with informix jdbc driver ... Marcel Mueller <news.5.maazl@spamgourmet.org> - 2016-03-14 21:23 +0100
Re: Troubles with informix jdbc driver ... Andreas Leitgeb <avl@logic.at> - 2016-03-14 21:30 +0000
Re: Troubles with informix jdbc driver ... Arne Vajhøj <arne@vajhoej.dk> - 2016-03-14 18:16 -0400
Re: Troubles with informix jdbc driver ... Marcel Mueller <news.5.maazl@spamgourmet.org> - 2016-03-15 21:57 +0100
Re: Troubles with informix jdbc driver ... Arne Vajhøj <arne@vajhoej.dk> - 2016-03-15 21:18 -0400
Re: Troubles with informix jdbc driver ... Andreas Leitgeb <avl@logic.at> - 2016-03-15 22:25 +0000
Re: Troubles with informix jdbc driver ... Arne Vajhøj <arne@vajhoej.dk> - 2016-03-15 21:25 -0400
Re: Troubles with informix jdbc driver ... Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2016-03-14 21:26 -0700
Re: Troubles with informix jdbc driver ... Andreas Leitgeb <avl@logic.at> - 2016-03-15 22:09 +0000
Re: Troubles with informix jdbc driver ... Andreas Leitgeb <avl@logic.at> - 2016-03-16 21:37 +0000
Re: Troubles with informix jdbc driver ... Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2016-03-16 22:36 -0700
Re: Troubles with informix jdbc driver ... -- workaround found Andreas Leitgeb <avl@logic.at> - 2016-03-17 17:23 +0000
Re: Troubles with informix jdbc driver ... -- workaround found Andreas Leitgeb <avl@logic.at> - 2016-03-18 11:13 +0000
csiph-web