Re: JDBC multi Connections in servlets with OCI7 driver

We have seen the same problem with a normal multi-threaded Java application where each thread has an independent connection to Oracle. The "first" thread using the OCI JDBC driver acquires a Java monitor on a string object, which it does not release until the "Select" returns. Other threads on other connections wait.

This obviously can cause very poor response times and deadlocks in an update environment.

We have reported it to Oracle, but not received any solution other than use the Type 4 drivers (we have, they get around the problem, but a simple benchmark runs over 4 times slower using the type 4 compared to the Type 2) or try a 3rd-party driver.

Kent Fitch                           Ph: +61 6 276 6711
ITS  CSIRO  Canberra  Australia      kent.fitch_at_its.csiro.au

In article <6a20jl$fk5$1_at_bw107zhb.bluewin.ch>,

   "Pascal BEY" <beyp_at_mygale.org> wrote:
>Hello,
>
>
>I use Oracle 7.3.2 and Oracle JDBC OCI 7.
>
>Please Help me!
>
>The first Oracle JDBC connection works very well in a servlet
>on the JavaWebServer 1.0.3.
>But, the second connection request seems to wait for the end of the
>SELECT launched in the first connection.
>
>Is this normal in a servlet ?
>
>How can I launch more than one SQL statement at the same time ?
>
>Thanks in advance !!!
>
>One more question :
>- Does the Oracle Web Server know the servlets mechanism ?
>
>
>
Received on Thu Jan 22 1998 - 00:00:00 CST