We had ora-00020 problems using connection pools if we did not explicitly close all statements, resultsets, etc - if we just closed the connection, the related objects remained open. We guessed it was because the connection was not really closed, only reused.
We have also been seeing some hotspot errors related to the Oracle OCI driver that resulted in logs that looked similar to what you are seeing. Not sure if that applies here - the server we saw that on was win2k. Larry >>> [EMAIL PROTECTED] 10/23/02 04:09 AM >>> Maybe this is also usefull to mention, but we are not sure if it is related: We are, at the same time, having troubles with the database connection to oracle. Queries are executed normally but; processes and sessions are not released after the query has returned the resultset (open_cursors are, they stay stable). This takes more and more processes and eventually ending in ora-00020 processes exceeded. We have not had that before. Details: Tomcat: 4.1.12 JKD: 1.4.1_b02 OS: Solaris 7 + required patches. Database: Oracle 8i --begin example-- 12 34 00 53 00 51 52 45 53 4f 55 52 43 45 3d 4d | .4.S.QRESOURCE=M 59 41 43 43 4f 55 4e 54 26 52 45 46 45 52 45 52 | YACCOUNT&REFERER 3d 52 45 51 55 45 53 54 5f 4f 56 45 52 56 49 45 | =REQUEST_OVERVIE 57 26 41 43 54 49 4f 4e 3d 52 45 51 55 45 53 54 | W&ACTION=REQUEST 5f 44 45 54 41 49 4c 26 52 45 51 55 45 53 54 49 | _DETAIL&REQUESTI 44 3d 34 33 39 33 33 | D=43933 --end example-- -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
