Re: [SPAM] - Re: JDBC HighLoad - Found word(s) XXX in the - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: [SPAM] - Re: JDBC HighLoad - Found word(s) XXX in the
Date
Msg-id Pine.BSO.4.56.0501281837510.24668@leary.csoft.net
Whole thread Raw
In response to Re: [SPAM] - Re: JDBC HighLoad - Found word(s) XXX in the  (Stéphane RIFF <stephane.riff@cerene.fr>)
Responses Re: [SPAM] - Re: [SPAM] - Re: JDBC HighLoad - Found word(s)  (Stéphane RIFF <stephane.riff@cerene.fr>)
List pgsql-jdbc

On Fri, 28 Jan 2005, [ISO-8859-1] St�phane RIFF wrote:

> Yes i use it as a singleon what's the problem with that ???
> I instanciate One object => 1 pool for all threads and each thread use
> the saveTrame

The problem is you have all your preprared statements allocated in the
singleton instead of per connection.  This is bad because you
overwrite them upon each call to prepareQuery.  When you have multiple
threads doing this at once what will happen is the first thread will
prepare them and start executing, the second thread will also prepare them
and begin executing, but since the statements are global, you've replaced
the first threads versions and it will now be executing on the second
threads connection because it's using the global statements.  You've got
chaos going on here.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: New JDBC site
Next
From: Kris Jurka
Date:
Subject: Re: Fix for changing parameter types with server prepared statements