|
The default is -client. The -server is the same as
-hotspot (deprecated).
The bug list is here
This was fixed in JDK 1.3.1 but we couldn't get the
Oracle OCI or thin drivers to work.
The Oracle OCI driver has a bug for 8.1.7 so we
couldn't use this with JDK 1.3.0.
(BUG-1542130
The use of OciConnectionPool may cause a hang in a
multi-threaded
environment )
The only option that worked was JDK 1.3.0 and the
8.1.7 Thin drivers. Its a shame since this means we have to choose the slowest
of both technologies.
Of course Oracle recommends to go to JDK
1.2.2.
ap
----- Original Message -----
Sent: Thursday, July 26, 2001 6:32
PM
Subject: RE: Anyone experience any
problems with JDBC Oracle drivers and J DK 1.3.1 with connection
pooling?
Funny..and I read that too. Thanks. I guess we'll
have to forgo the -server option. Do I have to specify -client? Or isn't
-hotspot (the default) ok?
Thanks.
See my previous email with
Subject: Oracle, JDK 1.3, Orion Re: Orion Performance
Tuning
Andrew Panagos
I have been trying
to figure out why I can't connect to our Oracle database. We are running
JDK 1.3.1 with Orion 1.5.2. We are using the jdbc.zip (I assume
classes12.zip). I am reading on Oracle that Oracle 8.1.7 (and 8.1.5) only
have JDBC drivers that support JDK 1.2.x. Does this mean running JDK 1.3.1
is a BAD move when using JDBC drivers from Oracle? Should I go back to JDK
1.2.2 for Orion? There are problems with JDK 1.2.2, such as the NT-LOGOFF
and what not when running Orion as a service that I am trying to avoid.
Please advise me if running Orion with JDK 1.3.1 (on Win2K Server or
Solaris) is OK while using Oracle 8.1.5 and/or Oracle 8.1.7 databases and
jdbc drivers.
Thanks.
|
