5 Replies Latest reply on Feb 3, 2004 5:46 PM by Erik Sliman

    jboss 3.2.3 on windows 2000 prof

    srikantp Newbie

      Hello All,

      I downloaded jboss-3.2.3. My system configuration windows 2000 prof and java 1.4.1_01 ver. http://localhost:8080/ gives

      HTTP Status 500 - No Context configured to process this request


      how to solve this problem?


      thanx

      Srikanth

        • 1. Re: jboss 3.2.3 on windows 2000 prof
          falling Newbie

          Hi, I think that is what is supposed to happen. that means the you have installed it correctly...
          I am new too; and have set the following system variables:
          JAVA_HOME C:\j2sdk1.4.2_03
          JBOSS_HOME C:\jboss-3.2.3
          Path %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\j2sdk1.4.2_03\jre\bin;%JBOSS_HOME%\bin
          Then I run the bat file at c:\jboss-3.2.3\bin\run.bat
          no exception is thrown and it displays "...started in 25s563ms "

          but, when I try to acess http://localhost:8080/
          I get this "The page cannot be displayed" message

          Did I miss some thing?

          Thanks!

          • 2. Re: jboss 3.2.3 on windows 2000 prof
            Erik Sliman Apprentice

            This is a frequently asked question because, this is what is supposed to happen when you install JBoss.

            Every web application deployed to JBoss is associated with a "context" which translates to a subdirectly off the main directory, or root. Two applications installed out of the box are:

            http://localhost:8080/jmx-console
            http://localhost:8080/web-console

            Thus, the context for the latter is "web-console". The error you get, 500, simply says that there is not application with the root context of "/".

            When you deploy an EAR, you can specify the context for your WARs in the EAR's META-INF/application.xml. Here is a sample, which includes two WARs, and one of them is the root (SuperMain.war), which will appear when you access "http://localhost:8080". The other will appear when you access "http://localhost:8080/admin".

            < application>
             <display-name>Super Application</display-name>
             < description>Super Application< /description>
            
             < module>
             < web>
             <web-uri>SuperMain.war</web-uri>
             <context-root>/</context-root>
             < /web>
             < /module>
            
             < module>
             < web>
             <web-uri>SuperAdmin.war</web-uri>
             <context-root>/admin</context-root>
             < /web>
             < /module>
            
             < module>
             < ejb>SuperEJB.jar< /ejb>
             < /module>
            
            < /application>
            


            Do not include the spaces you see above at the beginning of each tag. I had to put the spaces to get those tags to show up in the forum.

            Note that if you do not deploy the war in an EAR or do not specify the context-root in the application.xml of the ear, then it will default to using the war name to determine the context. Thus, without the deployment descriptor, SuperMain.war contents would have been accessible via "http://localhost:8080/SuperMain".

            Here is the FAQ for this topic:
            http://www.jboss.org/index.html?module=bb&op=viewtopic&t=7059

            • 3. Re: jboss 3.2.3 on windows 2000 prof
              falling Newbie

              but what about my question? I get a "page cannot be displayed" message, with the title being"HTTP 500 Internal server error"

              • 4. Re: jboss 3.2.3 on windows 2000 prof
                Darran Lofthouse Master

                falling - Did you read the reply from erik777?

                • 5. Re: jboss 3.2.3 on windows 2000 prof
                  Erik Sliman Apprentice

                  falling,

                  That is a different error, and usually comes form Apache HTTPD. It's confusing that on Apache's HTTPD server and Tomcat server error 500 mean completely different things.

                  HTTP 500 Internal server error

                  on Apache's HTTPD server can mean just about anything. In short, your Apache server blew up, it trapped the error and spit it out without crashing your OS. Your best bet is to look at your Apache error logs.

                  Are you trying to get mod_jk 1 or 2 to work? If so, this is the typical error when HTTPD can't talk to Tomcat, or has issues when it tries.

                  If you are getting this error when you try to access port 8080, then I suspect that Apache may be listening to this port. Shut down Apache HTTPD and try again to see if Tomcat/JBoss is working correctly first.

                  SRIKANTP, the original poster, was getting the error from Tomcat, not Apache HTTPD. So he got the Tomcat 500 error "No Context configured".

                  Also the Tomcat error says Apache Tomcat at the bottom of the error page, but HTTPD will not mention Tomcat.