Noel, Thank you for the suggestion about the <servernames> ....worked like a charm. I have been looking at the JDBCVirtualUserTable mailet and saw how it used avalon.excalibur.datasource.DataSourceComponent.
I assume that the package handles connection pooling; however, you are still openning and closing every time an instance of the mailet it closed. Though I looked at the package for several hours today, I think I am missing something. Does this package prevent the costly action of creating a connection and then closing it? Right now, it appears that I could JDBC directly form java.sql and still get the same result. Of course, I must be far off base. Thanks, Hut
