Atomikos Forum

"cannot grow pool as it reached max size" in new 3.3 release

Hi again!

After testing the new version of Atomikos, I´ve seen a message like this in the log:

"ConnectionPool: cannot grow pool as it reached max size:2000"

How this can happen if Oracle Enterprise Manager tells me there are only 17 connections?

This leads for us to problems in production environment (Tomcat 5.0) like getting several minutes to execute some queries (I suppose is when doing borrowConnection), but no problem in development environment (Tomcat 5.5). How this could be?

Temporary we have switched back to the previous release (3.2.0).

Regards
Juan G Send private email
Friday, May 23, 2008
 
 
Hi,

The 'cannot grow pool' log statement is misleading, see default82df.html?community.6.77 (the very last message).

If you encounter problems with the new pool, I'd suggest you to install the transactions-jdbc-deprecated.jar present in the 3.3 release that contains the old pool. Both can be used in parallel so at least you don't have to revert to a previous version.

I can only suggest you to collect more information about why you got that performance slowdown with the new pool as there is very little I can do from what you posted.

If you want us to concentrate on helping you sort out that performance issue, I'd also suggest you to get some support (http://www.atomikos.com/Main/ProductSupport).
Ludovic Orban Send private email
Friday, May 23, 2008
 
 
Hi,

I noticed you have different platforms in development and production.

In order to be able to compare in any meaningful way, development and production environments should be exact mirrors of each other. Otherwise, it is like comparing apples to pears. Could you try with 5.0 in development too?

Thanks
Guy
Guy Pardon Send private email
Monday, May 26, 2008
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics