[Ronald R DiFrango]

For JDBC Type 2 drivers, [in my case DB2], they require access to a DLL. the error I have found on several occarsions is that the minute I create one connection to the database and I attempt to connect to another one, I get the dreaded, the DLL loaded by another class loader problem. Any thoughts on how the DLL’s are loaded? Any way you can make load it only once and re-use it?

[Riyad Kalla]

I’ll check with the dev.

[support-jeff]

This may be a limitation of the JDBC driver itself – I have no experience with type 2 drivers myself so I do not speak from authority. You might check the DB2 support site and user forums for advice on this.

[Ronald R DiFrango]

My only question is, how do you create/use class loaders for any of the database stuff? Based upon past experience with JNI code, you must have it all running within the same class loader in order to for this to work. I have had this probelm with JUnit and JNI and we solved it by using 1 class loader within JUnit [Specific setup class] to ensure it only gets loaded 1 and works for all tests.

I would expect that you could do something similiar, like put a Type 2 flag and the Database Explorere knows to only load the Driver once instead of a new instance everytime.

[support-jeff]

Interesting solution. The functionality for loading driver classes comes right out of the JFaceDBC/SQLExplorer plugin. I wonder if Type 2 drivers were ever tested/worked with those original plugins?

[Eric Miles]

I’m having this same problem with DB2 drivers as well. Any known solution or workaround? Are there other drivers that work?

[Author]

Posts