6 Replies Latest reply on Jun 5, 2013 2:19 AM by Nicklas Karlsson

    JBoss runtime error?

    James Akins Newbie

      Hi

      I know this will probably be a newbie quetsion, but any help is appreciated.

      I'm running the jboss on my amazon web service instance. I am running it on a fedora ami.

      When I execute jboss with "./standalone.sh" , the program will start to run but then it stops after a couple seconds and looks to me like its waiting for something. below is a snippet of what it looks like when it is "waiting".

       

      Am I doing something wrong here or at that point am I supposed to start entering commands?

       

      On the last line, it just stays like that. What is supposed to happen?

       

       

       

      JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /root/jboss-as-7.1.1.Final

       

       

        JAVA: java

       

       

        JAVA_OPTS:  -server -XX:+TieredCompilation -Xms64m -Xmx86m -XX:MaxPermSize=64m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

       

       

      =========================================================================

       

       

      12:51:14,476 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

      12:51:16,264 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      12:51:16,427 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

      12:51:20,038 INFO  [org.xnio] XNIO Version 3.0.3.GA

      12:51:20,111 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

      12:51:20,131 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

      12:51:20,154 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

      12:51:20,273 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

      12:51:20,386 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

      12:51:20,393 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

      12:51:20,398 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

      12:51:20,400 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

      12:51:20,402 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

      12:51:20,468 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

      12:51:21,340 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final

      12:51:21,511 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

      12:51:21,563 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

      12:51:21,887 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      12:51:22,251 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA

      12:51:22,429 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

      12:51:23,373 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--10.62.57.21-8080

      12:51:25,380 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /root/jboss-as-7.1.1.Final/standalone/deployments

      12:51:25,490 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /127.0.0.1:9999

      12:51:25,520 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447

      12:51:25,748 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      12:51:25,843 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://10.62.57.21:9990

      12:51:25,844 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 12560ms - Started 133 of 209 services (75 services are passive or on-demand)

        • 1. Re: JBoss runtime error?
          Nicklas Karlsson Master

          Congratulations! The server is up and running, nothing else is supposed to happen in that window! ;-)

           

          Now comes the part where you drop in applications in the deployment folder or use the CLI or web console to deploy (and interact with the server). Have a look at the AS documentation for more info (https://docs.jboss.org/author/display/AS71/Documentation)

           

          You might also want to try out the later EAP 6.1.0.Alpha.

          • 2. Re: JBoss runtime error?
            James Akins Newbie

            Awesome, thanks for the reply, Nicklas.

             

            I have just one more question.

             

            When I am in the bin directory, I type the command "./run.sh"

             

            As soon as I type that command, in order for me to run the server(correct?), it says this:

             

            ========================================================================================

             

             

            To start JBoss Application Server please see /root/jboss-as-7.1.1.Final/bin/../README.txt

             

             

            ========================================================================================

             

            What does this mean? I thought I had the server already up?

            Also, when I try to go to my localport:8080 or even localport:9990, nothing exists. Any help is appreciated! thank you!

            • 3. Re: JBoss runtime error?
              Wolf-Dieter Fink Master

              run.sh is the 'old' method to start former JBoss versions. The script is only meant to show users of the former version how to start the new AS7.

               

              It depends on the configuration where the sockets are listening. http looks like configured on 10.62.57.21.

              If you try to use 9990 for the admin interface it is on localhost, you need to start the browser on the same system. You only see a page with a hint that you need to add an admin user to login (by default)

              • 4. Re: JBoss runtime error?
                James Akins Newbie

                So from my previous post, my server is up and fully operational then, correct?

                 

                I did try to go to the website localhost:9990, nor did 8080. Does this mean my server is running or down? I am beginning to write a bootstrap script where I am downloading and uploading Maven repository war files. I assume JBoss is the tool where I also need to listen and archive my files?

                 

                Sorry for all these newbie questions, I am just trying to understand it fully. The guide helps somewhat, but doesn't always have the specific answer I am looking for.

                 

                Thanks!

                • 5. Re: JBoss runtime error?
                  Stephen Coy Master

                  It looks like your instance is listening on 10.62.57.21.

                  • 6. Re: JBoss runtime error?
                    Nicklas Karlsson Master

                    > I assume JBoss is the tool where I also need to listen and archive my files?

                     

                     

                    I didn't quite parse that. But if you want to update wars before the server starts, I guess you will have to pull them down and have them land in the standalone/deployments directory.