Monday, October 27, 2003 06:44 AM
Maybe (unlike many error messages which are close but just a bit off the "real problem") it is really telling the truth, e.g. are all the pooled/managed connections really in use? maybe you have a "leak", where some are not getting returned to the pool (some cursor, resultset, statement not being closed, etc.)? what if you increase the max number of connections in the pool? etc. (are you using the default, maybe is it different, between the 2 different versions? etc.)
Can you monitor/check the connections, from the database side? e.g. with Oracle, the "DBA Studio" can verify open/idle connections etc.