Strange Pooling
Q: I have strange pooling? Connections that are not matched in my matchManagedConnections are
destroyed.
A: Yes this is the default/expected behaviour. The default pool is a singleton MRU list of supposedly equivalent connections. If you have different connections configured from the ConnectionRequestInfo you should use the poorly named:
<application-managed-security></application-managed-security>
Q: Why the poor name?
A: Because the original author of the XML only anticipated security information in the ConnectionRequestInfo
Q: Isn't this non-spec compliant?
A: Go read the spec
Related
Comments