This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 98114 - Tomcat fails to startup but there is a workaround
Summary: Tomcat fails to startup but there is a workaround
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-16 20:29 UTC by combsyes
Modified: 2007-06-18 16:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description combsyes 2007-03-16 20:29:33 UTC 
Using 1.5.0_11-b03 (hotspot client) for Tomcat 5.5.17 when I run the project
with 'Enable HTTP Monitor' checkbox ticked on I get the following exception:


SEVERE: Servlet.service() for servlet TM7Servlet threw exception
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
        at
javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
        at
org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:410)
        at
org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:384)
        at
org.netbeans.modules.schema2beans.GraphManager.createXmlDocument(GraphManager.java:331)
        at
org.netbeans.modules.schema2beans.GraphManager.createRootElementNode(GraphManager.java:115)
        at
org.netbeans.modules.web.monitor.data.MonitorData.<init>(MonitorData.java:53)
        at
org.netbeans.modules.web.monitor.data.MonitorData.<init>(MonitorData.java:46)
        at
org.netbeans.modules.web.monitor.server.MonitorFilter.setupDataRecord(MonitorFilter.java:459)
        at
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:306)
        at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
        at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
        at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
        at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
        at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)

When the HTTP Monitor is disabled, the project runs just fine. I discovered the
workaround on Nabble in the following thread:

http://www.nabble.com/Tomcat-problem-when-using-Apache-Xerces-tf2910208.html#a8138016

Perhaps this problem can now be fixed since it has been around since 2005
Comment 1 Sherold Dev 2007-06-06 14:05:20 UTC 
I cannot reproduce the issue. Can you please provide steps to reproduce it? Did
you add any special jars (XML related) to the project or server class path?

Marking the issue as INCOMPLETE.
Comment 2 Sherold Dev 2007-06-18 16:08:33 UTC 
Closing the issue as WORKSFORME since I cannot reproduce the issue and there is no feedback from the user.