https://issues.apache.org/bugzilla/show_bug.cgi?id=52025
--- Comment #8 from Rick Bullotta <rick.bullo...@thingworx.com> 2011-10-17 13:52:48 UTC --- Thanks, Mark. Probably the reason they left the Service provider stuff in sun.misc!!! We'll just go back to the ever-popular Class.forName, which (almost) always works... (In reply to comment #7) > I am closing this as INVALID as the Service Provider mechanism for > DriverManager is - as I suspected - broken for servlet container environments. > Given that it was a lottery if this ever worked before, that it now > consistently doesn't work isn't really a regression. > > What I have done is updated the documentation to try and explain what is going > on and how to work-around it. Basically, just assume the service provider > mechanism isn't there and manually register (and deregister) the Driver. > > The change for the updated docs is here: > http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/jndi-datasource-examples-howto.xml?r1=1184919&r2=1184918&pathrev=1184919 > > You may find this presentation on memory leaks useful / interesting: > http://people.apache.org/~markt/presentations/2010-11-04-Memory-Leaks-60mins.pdf -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
