2 Replies Latest reply on Sep 25, 2006 6:15 PM by Walt Stoneburner

    JBOSS isn't working... VERY BEGINNER

    Tracy Monteith Newbie

      Just installed JBoss and, of course, it isn't working.

      I had several jsps and servlets working in tomcat. I tried to migrate them to jboss so I can eventually add ejbs to the mix.

      Every page html, or jsp I get a 404 error.

      I can't figure out why nothing works.

      In tomcat I can check the log files and see the error. Not true on JBoss.

      I found 2 log files on JBOSS:

      If I refresh the web page and get the 404 error, this error isnt logged.

      How do I know why it isn't working?

      So now, I try to refresh the log files.

      I kill jboss, remove the log files, and restart jboss; the log files are 1.5M

      That's insane!!! How can jboss make 1.5M log files just after just starting?

      Please explain what's going on here. I'm very confused.

        • 1. Re: JBOSS isn't working... VERY BEGINNER
          Peter Johnson Master

          How did you deploy your servlets? In JBoss, you should create a war file and copy the war file to the server/default/deploy directory (for example, you would have server/default/deploy/foobar.war). Then you can access index.html as http://locahost:8080/foobar/index.html.

          Depending on the services you installed (I assume you used the installer jar file, and not the zip file), a 1.5MB log file for startup is normal. You can controll this via the loj4j.xml file in server/default/conf.

          • 2. Re: JBOSS isn't working... VERY BEGINNER
            Walt Stoneburner Newbie

            I'm new to all this as well, but seem to have had some decent luck.

            The solution I took to was using NetBeans, which made it trivial to make and deploy .jsp stuff. It can send 'em to TomCat or JBoss, which I discovered were using a different ports -- so make sure you're using the right URL.

            If I understand things correctly, you do not have a directory you drop JSP files into, but rather you create a WAR file (NetBeans does it for you) and move it to JBoss's server/default/deploy directory (which NetBeans also does for you).

            The JBoss log files are large because they are also capturing DEBUG and INFO log items -- in other words, the system is deliberately being extremely verbose so you can see everything at a very granular level.

            I believe there was a typo in the last reply, and that the file to turn this logging down a notch is log4j.xml.

            But I understand your frustration, you're expecting to see a file get accessed and a 404 if it isn't there. Instead, I think it's looking inside the WAR file, and if it can't find the deployment, it just tells the browser it has no idea what you've requested. I'm not sure this appears in the log, though I suspect it does, only as some other message and not a 404. Perhaps something like no web application by that name?