Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Mysteriously dropped connection and deciphering the trace
Hi all,
I have an application that uses Oracle's JDBC thin driver 9.0.x to have a nice, friendly chat with 8.1.x database. During this exchange the server rudely interrupts the conversation and causes the application to fubar. The driver reports this as 'Connection reset' (IOException) without any error numbers. The server is hosted by a 3rd party in one of those "controlled" environments so my first guess is network/tx timeout but wouldn't it say so? This is 100% reproducible and always fails in the same place. The line of code corresponding to that reported in JDBC driver stack trace does nothing but unset the auto commit. If this is indeed a case of one particular transaction timing out on commit, how do I tell if this is indeed the case? I can't do a client-side SQL*Net trace with the thin driver and server-side SQL trace doesn't tell me anything interesting.
Here's the relevant part of the server-side SQL*Net trace (IP address changed to protect the innocent):
nigini: Count in NI global area now: 1
nigini: Count in NI global area now: 1
nrigbni: Unable to get data from navigation file tnsnav.ora
niotns: Not enabling dead connection detection.
nlpcaini: No process parameters set
nsinherit: connecting... nsinherit: doing connect handshake... nsinherit:
nsopen: opening transport... nttcnp: Validnode Table IN use; err 0x0 nsopen: transport is open
nsopen: opening transport... nttcnp: Validnode Table IN use; err 0x0 nttcnp: getting sockname nttcnp: getting peername nttcon: set TCP_NODELAY on 18 nsopen: transport is open
nscon: doing connect handshake... nscon: sending NSPTRS packet nscon: doing connect handshake... nscon: got NSPTCN packet
nscon: sending NSPTAC packet nscon: doing connect handshake... nscon: nsctxinf[0]=0x49, [1]=0x8
nioqbr: calling rdbms ast handler... nioqbr: ...done. nioqrs: state = interrupted (1)
nioqbr: calling rdbms ast handler... nioqbr: ...done. nioqrs: state = interrupted (1)
ORA-12630 (if that's what nazsgunm is saying) is like HTTP 500: no way to tell what went wrong..
Any help is appreciated.
Alex Smith
Insight LLC
Received on Thu Jul 31 2003 - 16:45:17 CDT