On 02.07.2013 10:36, Christopher BROWN wrote: > What is the best strategy for integrating JDBC drivers, such as MySQL, > jTDS, and others that can start background threads or timers, so that these > can be correctly stopped when the bundle is unloaded?
Implementing the JDBC Service bits? See Enterprise Spec Chapter #125. This won't magically "fix" the underlying driver code if it behaves badly and has e.g. no way to stop internal threads, but it gives you a starting point to sanitize the driver/client interaction. This of course assumes that your client code is at least slightly JDBC-service aware and does not blindly call Class.forName() to grope the driver. Also I think I saw that only with JDK 8 some of the internal tangles with the JDK<->JDBC registration mechanism will allow clean removal of a driver (sorry, don't remember the details). Contacting driver vendors about this is a complete waste of time. -h --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
