> OK, I'll have to investigate the DB setting more thoroughly. The maximum > sessions and processes in Oracle are higher than we were using for the test > though (several hundred).
We hit a similar situation a year ago. Essentailly Oracle has a TNS listener process that accepts connections. This is responsible for counting connections and preventing any new ones when the limit is hit. The counting only occurs on a background thread every x minutes, hence if you have a high turnover of connections, you can exceed the limit. Even if your app correctly returns all connections, the TNS listener will not "see" the returned connections, and hence hit the error above. For our situation we were able to just bump up the connections allowed to the db. This may or may not help in your case HTH Chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
