Oracle driver killing jvm

Thread view:

Robert - 14 Apr 2005 20:25 GMT

I was wondering how you tell. Our jboss server is going down about
twice a day now with NO Exceptions, no segmentation faults and it
appears no core files. We just switched to the oracle OCI drive pretty
recently to accomodate clob/blob needs for some bioinformatics
software. Anyway we're testing the newest thin driver as I type this
but I was wondering if anyone had a way to tell if it was for sure the
oracle driver killing the jvm. Thanks.

-Robert

Reply to this Message

Joe Weinstein - 14 Apr 2005 21:10 GMT

> I was wondering how you tell. Our jboss server is going down about
> twice a day now with NO Exceptions, no segmentation faults and it
[quoted text clipped - 5 lines]
>
> -Robert

Hi. The thin driver won't/can't be killing the JVM, but the OCI-based
driver certainly could. You should make sure you have the very latest
version of OCI. The way to find the culprit would be to start your
JVM under a C-level debugger like dbx or whatever one your OS has.
The native-level debugger will at the very least say where/why the
process exited.
Joe Weinstein at BEA

(PS: if you have an OS limit on the size of the core file you are allowed
to write, you won't get one if it would be bigger.)

Reply to this Message

Oracle driver killing jvm

Free Magazines