Not precisely sure how this debug facility works but it looks like connection pool debug info if you specify the ---pool.debug property is routed to some kind of stdout. Is there a way to intervene there and redirect that output into the same place where other product logging is going (e.g. syslog, file logs, etc.)? tyia. Chris