Recently I've embedded Tomcat directly within our application. The idea is that web application extensions to the system can easily share the core of our platform and the root Spring application context. This has worked well up until yesterday when I ran into some weird class loading issues with Tomcat.
Once issue was that if an application included a JAR file that is also included in the core platform, Tomcat would still load the class from the system classloader, instead of loading it from the WAR file using the Tomcat web app classloader.
For example, this is a problem when using the Wicket web framework. Wicket will load a class for a page from inside one of the Wicket core classes using getClass().getClassLoader().loadClass(XYZ). However, since Wicket was loaded using the system class loader it cannot see the web app's classes and this will result in a ClassNotFoundException.
Another problem was using CGLib. When CGLib tried to instantiate a class using ClassLoader.defineClass() it would result in a NoClassDefFoundError. Again, the problem here is that CGLib was loaded from the system class loader and cannot resolve classes from the web app's WAR file.
It took a while to find out why this is happening. According to the Tomcat 5 Class Loader HOW-TO, it should always load classed from the web app itself before loading them from the system class loader, except for special case classes. Looking at the middle of the page however, it does say that the system class loader is used first. Unfortunately for the longest time I was looking at the Tomcat 4 Class Loader HOW-TO and on that page it still indicates that the web app class loader is always used first.
It turns out the system class loader is in fact always used first. Specifically line 1267 of WebappClassLoader in the Tomcat 5.5.17 sources. However, if you use the normal Catalina startup script it resets the system class path to only include a minimal set of classes, so in that case it would not find application specific classes using the system class loader. Therefore running Tomcat normally it would always end up using the WebappClassLoader.
To get the same behaviour when embedding Tomcat in your own application, you have to create a bootstrap class. You only include the bootstrap class in the class path when loading your application. The bootstrap class then creates a URLClassLoader to load in the rest of your application classes. For example:
public class Bootstrap
{
public static void main(String args[])
{
String root = args[0];
try
{
List<URL> classpath = new ArrayList<URL>();
classpath.add(new File(root + File.separator + "conf" + File.separator).toURL());
addJarFileUrls(classpath, new File(root + File.separator + "libs"));
ClassLoader cl = new URLClassLoader(classpath.toArray(new URL[0]));
// Set the proper classloader for this thread.
Thread.currentThread().setContextClassLoader(cl);
// Use reflection to load a class to normally load the rest of the app.
// Reflection will use the Thread's context class loader and therefore pick up
// the rest of our libraries.
Class appClass = cl.loadClass("com.neatstep.frank.Application");
Object app = appClass.newInstance();
Method m = app.getClass().getMethod("start", new Class[0]);
m.invoke(app, new Object[0]);
}
catch (Exception ex)
{
ex.printStackTrace();
System.exit(1);
}
}
/**
* Add JAR files found in the given directory to the list of URLs.
* @param jarUrls the list to add URLs to
* @param root the directory to recursively search for JAR files.
*/
private static void addJarFileUrls(List<URL> jarUrls, File root) throws MalformedURLException
{
File[] children = root.listFiles();
if (children == null)
{
return;
}
for (int i = 0; i < children.length; i++)
{
File child = children[i];
if (child.isDirectory() && child.canRead())
{
addJarFileUrls(jarUrls, child);
}
else if (child.isFile() && child.canRead() &&
child.getName().toLowerCase().endsWith(".jar"))
{
jarUrls.add(child.toURL());
}
}
}
And in a separate class file that is included in one of the JAR files which we dynamically add to the URLClassPath above:
public class Application
{
public void start()
{
// Do whatever you want.
// Initialize embedded Tomcat.
}
}
After adding this bootstrap class to our application, everything worked fine.
Recent comments
29 weeks 6 days ago
1 year 10 weeks ago
1 year 13 weeks ago
1 year 42 weeks ago
2 years 3 days ago
2 years 2 weeks ago
2 years 6 weeks ago
2 years 8 weeks ago
2 years 12 weeks ago
2 years 13 weeks ago