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

From Stéphane RIFF
Subject Re: [SPAM] - Re: [SPAM] - Re: JDBC HighLoad - Found word(s)
Date
Msg-id 41FE3906.7010008@cerene.fr
Whole thread Raw
In response to Re: [SPAM] - Re: JDBC HighLoad - Found word(s) XXX in the  (Kris Jurka <books@ejurka.com>)
Responses Re: [SPAM] - Re: [SPAM] - Re: JDBC HighLoad - Found word(s)  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Ok so how can i make a preparedStatement pool or
allocated my preparedStatements for each connection ???

Kris Jurka wrote:

>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
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo@postgresql.org so that your
>      message can get through to the mailing list cleanly
>
>
>
>



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.2 - Release Date: 28/01/2005


pgsql-jdbc by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Fix for changing parameter types with server prepared statements
Next
From: Venkatesh Babu
Date:
Subject: Help with exception: java.lang.IllegalArgumentException: \0 not allowed