-
1. Re: HTTP Status 500 - No Context configured to process this
I have the same problem. I'm on a Win 2K machine. I downloaded JBoss 3.0.6 and unzipped the archive, preserving directory names (of course). When I execute jboss-3.0.6\bin\run.bat (with no arguments), I get the HTTP Status 500 response, as mentioned by Netm in the above post.
Any ideas would be very much appreciated! ;)
- Jeff -
2. Re: HTTP Status 500 - No Context configured to process this
Well, this is embarassing ;)
I'm on a new machine. I did not have JAVA_HOME configured, nor was the Java \bin directory on my path (which shouldn't matter since JBoss comes with it's own runtime as I understand it).
Anyway, once I configured JAVA_HOME and added cL\j2sdk1.4.1 to my PATH environment variable, the following URL worked for me:
http://localhost:8080/jmx-console/
Hope that helps! -
3. Re: HTTP Status 500 - No Context configured to process this
Hi I've encountered the same problem. I can access the jmx-console but I can't look at any of the example servlets or jsps? I can't even get the original tomcat index page at
http://localhost:8080/
to come up?
Why have jboss changed this. Is there any documentation on what and why they've done this?
Thanks,
Mark. -
4. Re: HTTP Status 500 - No Context configured to process this
You need to deploy an application to the deploy directory. The integrated Tomcat server is not the same as the 'stock' server, because the apps are mounted from the deploy directory, which is the server-wide place to deploy all non-core services and applications. If you drop in a WAR file (like a war from the Tomcat distro) or an EAR file, you will be able to get to it. There has been tons of discussion about this exact issue in forums and maillists. You can probably find more info by searching here (try FAQ forum) and the maillists.
Mike
