Hi All, The standard tomcat datasource resource is a pooled datasource. In addition to all the datasource properties already exposed through admin interface I also need to expose the pool behind the datasource.
i.e. I need to obtain a list of objects in the resource pool as well as information on the thread that has each object checked out. With possibly the ability to manually reclaim a resource. Will this level of pool manageability be part of the standard tomcat management feature set or will I have to do it myself? One possible solution woudl be to extend the GenericObjectPool class in the following manner: a. Add a secondary datastructure to keep track of who 'borrowed' what. b. Override the borrowObject() & returnObject() methods to maintain the secondary datastrucure c. Expose this class through an MBean. This solution however would require building custom object factories and getting hold of my datasource in a non standard way. Any suggestions? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
