I posted this on the axis user list, and someone was kind enough to ask for the full stack trace. However, there is no log entry for this event in Tomcat's logs, notwithstanding a statement to the contrary on the error page Tomcat displays. So now I'm beginning to suspect Tomcat in the original error, since it's not able to produce a full stack trace. I believe I have Tomcat configured properly for logging errors, and I've received stack traces in the logs many times. On the logging tab of the service properties window for Tomcat, I have all levels configured to place log files in the directory in which I'm looking, and I have "redirect Stderrorr" and "redirect Stdout" to auto.
I'm running Tomcat 5.5.8 on XP. Any idea how I can get this stacktrace, or if Tomcat could be garbling the class reference somehow?
-Mark
Here's the text of the Tomcat error page.[ Line 94 of ProxyServlet.java says Document doc = XMLUtils.newDocument(); ]
*type* Exception report
*message*
*description* _The server encountered an internal error () that prevented it from fulfilling this request._
*exception*
javax.servlet.ServletException: Servlet execution threw an exception
*root cause*
java.lang.NoClassDefFoundError: javax/xml/soap/SOAPException
Proxy.ProxyServlet.handleHtmlFile(ProxyServlet.java:94)
Proxy.ProxyServlet.doGet(ProxyServlet.java:55)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)*note* _The full stack trace of the root cause is available in the Apache Tomcat/5.0 logs._
------------------------------------------------------------------------
Apache Tomcat/5.0
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
