Hi,
I am experimenting with multiple connection pools. I am at a point where it will be very convenient to retrieve the pool a particular LDAP connection is associated with.
However the getConnection() method of the LDAPConnection class is currently not public.
At present, this method is only used internally within the LDAP SDK (e.g., to intercept a request to close the connection so that it is released to the pool as defunct) so it isn't public. However, I can consider making it public.
For now, you have a couple of options. One way would be to the getConnectionPoolName method, and to maintain a map of connection pool names to connection pool instances. Another would be to use reflection to retrieve the getConnectionPool method, make it accessible, and invoke it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just committed a change that makes the LDAPConnection.getConnectionPool method public. This will be included in the next release of the LDAP SDK. If you want it now, then you can check out and build the SDK from the Subversion repository, or you can use one of the workarounds I described earlier.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am experimenting with multiple connection pools. I am at a point where it will be very convenient to retrieve the pool a particular LDAP connection is associated with.
However the getConnection() method of the LDAPConnection class is currently not public.
AbstractConnectionPool getConnectionPool() { return connectionPool; }Anyone knows a workaround to that ?
Thanks,
At present, this method is only used internally within the LDAP SDK (e.g., to intercept a request to close the connection so that it is released to the pool as defunct) so it isn't public. However, I can consider making it public.
For now, you have a couple of options. One way would be to the getConnectionPoolName method, and to maintain a map of connection pool names to connection pool instances. Another would be to use reflection to retrieve the getConnectionPool method, make it accessible, and invoke it.
I have just committed a change that makes the LDAPConnection.getConnectionPool method public. This will be included in the next release of the LDAP SDK. If you want it now, then you can check out and build the SDK from the Subversion repository, or you can use one of the workarounds I described earlier.