The solution has been posted almost as many times as the problem (;>) Of course, with the forums down, you can't find those posts (:o)
The tomcat-test.ear (which is automatically deployed with this configuration) does not use the root context -- it uses the "/jboss" context. Therefore, the request for http://localhost:8080 will return a 500. -Michael Schulz -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Butcher Sent: Thursday, January 17, 2002 10:21 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] HTTP 500 Context Error with JBoss 2.4.4 and Tomcat 4.0.1 Dear List, I've seen discussion of and postings about this error with JBoss 2.4.4 and Tomcat 4.0.1 "right out of the zip" but I don't seem to be able to find a posted solution. In brief, when running this combination (including Windows 2000, JDK 1.3.1) using the batch file "run with catalina," it appears that Tomcat successfully starts but requests sent to http://localhost:8080/ result in an HTTP 500 - No Context Defined error being returned from Tomcat along with a long stacktrace of a null pointer exception (which you can see in some of the other messages) printing out in the JBoss DOS window. Otherwise, when Tomcat is run as a standalone, http://localhost:8080/ works and http://localhost:8080/jboss/index.html works when they are run together. Any suggestions would be appreciated. Sincerely, Steve _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
