We've got an application in production on Tomcat 4.1.30 (SDK 1.4.2). The application works fine in test. In production, however, there seems to be some kind of degradation. When there is a certain load (not even very high), the following occurs: These 2 lines (in several classes, JasperReports as well as our own code): DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); documentBuilder = factory.newDocumentBuilder();
Start to work with the wrong class: org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl (the XML parser of Axis2) instead of the wanted class: org.apache.xerces.jaxp.DocumentBuilderFactoryImpl Both classes are in our classpath, but for some reason this problem only occurs in production after a period of uptime. This gives NullPointerExceptions. What should we do to avoid this ? Is it the classloader of tomcat going strange ? Any help would be appreciated. -- View this message in context: http://www.nabble.com/Tomcat-4.1.30-classloader-problem-tp14841424p14841424.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
