I don't know if this has anything to do with it, but the SQLite engine itself is loaded in NestedVM. I would not think that would have a large bearing on the JDBC driver itself, but it is something different about this particular database.
-Tom On Mon, Nov 9, 2009 at 7:25 PM, Vivek Pandey <[email protected]> wrote: > I am investigating memory leak related to hot deployment of Rails > application on GlassFish. One of the hanging references is the JDBC driver, > in this case: org.sqlite.JDBC. The class loader is > org.jruby.util.JRubyClassLoader. > I tried to fix it by trying to do something like this: > for (Enumeration e = DriverManager.getDrivers(); > e.hasMoreElements();) { > Driver driver = (Driver) e.nextElement(); > if (driver.getClass().getClassLoader() == > getClass().getClassLoader()) { > DriverManager.deregisterDriver(driver); > } > } > This does not work because DriverManager.getDrivers() returns only the > drivers loaded by this classloader so org.sqlite3.JDBC is not even reported > although in the debugger I can see it very well and its loaded by > JRubyClassLoader. > So the right fix will be in Ruby.tearDown() to do what I am trying to do > using JRubyClassLoader loaded class. > I have opened a JIRA: http://jira.codehaus.org/browse/JRUBY-4226 > -vivek. -- blog: http://blog.enebo.com twitter: tom_enebo mail: [email protected] --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
