Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Accelerate</strong> <strong>Your</strong> <strong>JBoss</strong> <strong>Enterprise</strong> <strong>Middleware</strong> –JCA ContainerJCAJCAContainerContainer● For the JCA container we are going to concentrate on data sources.● The JCA container is responsible for the integration of our datasources into the application server and provides services for them.● The three areas we will concentrate on are:● Database connection pooling, the Cached Connection Manager,and Prepared Statement Caching.● The size of the database connection pool is directly related to theconcurrent execution of queries across your application.● To small a pool, and you add to your response times.● The default timeout for a database connection is 30 seconds!● This is a long time to wait, and you won't get the log message of atimeout until you have real problems with applicationperformance.● The Cached Connection Manager provides a debugging capability forleaked database connections.● Unless you are doing your own JDBC code, this is typically notneeded.● It's much easier to turn off in EAP 6, than it was in EAP 5.