Weblogic 6.1 sp5 core dump by OCI driver

Question

I have encountered a core dump problem on weblogic server 6.1 SP5 the error message
as below, I am using weblogic oci driver for oracle "libweblogicoci37.so" , anyone
can help?
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 4 occurred at PC=0x242795c
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.

Answer 1

Galen Boyer wrote:
On Sun, 28 Mar 2004, [email protected] wrote:
Galen Boyer wrote:
On Sat, 27 Mar 2004, [email protected] wrote:
One way to get a substantial boost in reliability is to switch
to the latest appropriate Oracle thin driver.But then you can suffer performance losses.Actually, the latest oracle thin drivers are very fast. The 10g
driver in particular. Well, we are on 9i here and we have lots of CLOB and BLOB
operations. Understood. The latest should work. (How comfortable does that make you ;) )
It is a sad choice we used to have to make between
faster-but-buggy homicidal old OCI code (wherein a bug in one
module can cause a segfault in an innocent unrelated module's
execution, and bring down a whole JVM) and the reliability of
Java. Fortunately, the future is at hand. The future is at hand? I do believe you are starting to sound a
bit like an evangelist. :-)Yep. Back in '96 when we wrote and marketed all the first JDBC drivers
for MS SQLServer, Oracle, Informix and Sybase, we did it solely
so enable our application server to be able to do real work. We were all
absolutely sure the driver market would dry up in 6 months as all the
DBMS vendors made excellent free type-4 drivers. We were over-optimistic.
Sybase's driver still requires you to install non-standard tables and
procedures in the DBMS. Oracle drivers are sloutching toward sufficiency,
but their first GA driver had a hard-wired value of READ_UNCOMMITTED
for getTransactionIsolation, and if you tried setTransactionIsolation
of either READ_COMMITTED or SERIALIZABLE, the driver would throw an
exception! We actually had a weblogic workaround to intercept this
jdbc call and send the "ALTER SESSION " to do what the customer wanted!
At the same time we had a major struggle to get Oracle to admit that
in spite of their documentation, OCI was not threadsafe (killing our
OCI-based driver in weblogic applications) until 7.1.4 on solaris
and NT, and 8.0.5 on other platforms. Did you know they had separate
codelines for OCI on each platform? For a while each platform's OCI
had a different hard-wired limit of the number of simultaneous connections
on client could have? For a while that limited what our application server
could do. OCI was written for simple teller-like client applications.
The new thin drivers take on more of the possible client-side
processing, and can do RAC failover etc. JoeOh well. I for one am a bit skeptical that Oracle is going to
fix java driver bugs before OCI bugs and I don't have any reason
to commit to any "platform independent" solution like java's thin
driver. We are completely based on Oracle here and we have a
J2EE solution for the app just cause we had to choose something.
If thin is better, than we will go with that.The last highest-level talks I had with Oracle folks they indicated that
they wanted everyone to go thin. OCI was a headache for them. Their
OCI code was undocumented and all the original experts had left the company.
That was in 2000 or so, so it is likely better now. They may well have
invested a lot of reverse-documentation by now.
One of the benefits of Java is the reliability. I think you'll
ultimately be happier with the thin. We do want you successful.
Joe