3 Replies Latest reply on Jul 3, 2009 4:43 PM by Peter Johnson

    JBoss 4.2.2 not listening

    Iván Pazmiño Novice

      Hi,

      I have a server instance, copy of a default, that starts normally and deploy a datasource, and ejb jar and a war. It's configured to listen at the port 8081

      Once it has finished starting up, it seemd to be ready to serve, but it is impossible to make it work. When trying to get any resource, for example http://localhost:8180/app it takes ages and does nothing and after a while shows a blank page. I tried http://localhost:8180 and the page displays in a very long time.

      And the most bizarre is, when I go to the command line window where started the instance y press Crtl+C and nothing happens. The server won't shut down

      Any ideas?
      Thanks in advance.

        • 1. Re: JBoss 4.2.2 not listening
          Peter Johnson Master

          What version of JBoss AS? What OS? What JVM?

          What is the CPU usage?

          Try this - undeploy all of your apps, including the datasource. Bring up JBoss AS and try to access the home page and do a CTRL-C. Does it respond? If so, then good. Now repeat the same thing several times, each time adding in one more app (start with the datasource, then the EJB JAR, then the WAR). That should help identify which app is causing the issue.

          • 2. Re: JBoss 4.2.2 not listening
            Iván Pazmiño Novice

            I have reinstalled from zero and made some changes so it works along with other instance I need to be started. It started up again, but now when trying to access the page it throws an error right away

            java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/compiler/parser/Scanner

            The installation is on Win XP
            Is a JBoss 4.2.2
            Java jdk 1.5

            • 3. Re: JBoss 4.2.2 not listening
              Peter Johnson Master

              Are you doing this within Eclipse? If so, don't. Do everything from the command line.

              When posting exceptions, post the full stack trace, not just the error message. Also, don't bother posting exceptions that show up in the browser - they are usually useless. There should be a corresponding exception in the console log - post that.

              Also, when posting what you are doing, please be exact and specific. Phrases such as "and made some changes so it works along with other instance I need to be started" give me no clue as to what it is that you did, and "other instance" could mean anything. Instance of what???