Thanks for your reply - much appreciated.
To answer your question about the jdbc connections being shared across all apps...
I develop and deploy servlet apps to several tomcat servers we host. The management of customer access and database connections is managed by another team who maintain the conf/context.xml file on each server. When we get a new customer, a schema is built and jdbc connection created without any involvement or app redeployment by me. This can happen daily. I can also redeploy apps whenever I want knowing security will never be compromised.
I completely agree that of the 64 pools I see, I only want to see 16 of them (2 apps * 8 connections).
If you (or anyone reading this) know of a way to dedicate jdbc connections to a specific app on tomcat, which can be managed outside the app's webapps folder, then please post advice/a link.
Finally kjkoster, even if someone knows a solution to my last request, it would still be very handy if the 64 item limit could be lifted within the probe.