-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All,
Propes, Barry L [GCG-NAOT] wrote: > we had similar connection problems with Oracle here. > > At first I changed drivers, which I thought would help, then while I > was furiously trying to implement connection pooling, which I ended > up doing, we discovered there were big problems with the network > connection to Oracle, as well as the listeners cache on the DB being > full. > > They rebooted the oracle server and all was immediately well. Might > see if they can try that where you are. If rebooting the database server worked, you might be leaking cursors or even connections. IIRC, Oracle won't release a cursor on the server unless you actually call ResultSet.close. So, even if you don't have a connection leak, you still might have a cursor leak. And, of course, if you have a connection leak -- even one that doesn't snowball over time... like if you have one that runs on startup only but gets leaked -- the server will never drop that connection (at least, this was the behavior of Oracle last time I used it with Java). Connections on the server side require obscene amounts of memory, and you can really bring your Oracle server to its knees with leaky connections and/or cursors. Maybe that doesn't help, but I figured I'd point it out, anyway. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+rGa9CaO5/Lv0PARAqfMAJ0XzFWKZ+3enY0ge6YPBogaMLHAeACfUmmX nb0jR7W/j1g7TFwug8RaKRw= =fORQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
