Tungsten Connector can work behind a connection pool without any issue.
Upon switch or failover, all connections in the pool will be broken but not closed. The very next time one of these pooled connections is used, it will be transparently reconnected unless autoReconnect has been disabled by the tpm installation flag:
shell > tpm update alpha --connector-autoreconnect=false
When using a connection pool mechanism in applications, the dynamic
connection setting maxAppliedLatency should not be
used. This setting is only meaningful at connection time; since
connection pools open a set of connections, the applied latency will
most probably be outdated when the application will actually use the
pooled connection