4 Replies Latest reply on Aug 3, 2009 5:30 PM by davidz

    Problems Reaching Admin Console

    davidz

      Hi,

      I have a fresh install of jboss 4.2.3.GA on a Red Hat Server Version 5.3. When I execute run.sh, it seems to have a clean start, but I'm not able to reach the admin console on port 8080.

      Does anyone have any suggestions about what might be causing the problem?

      Here is my server startup log:

      =========================================================================
      
       JBoss Bootstrap Environment
      
       JBOSS_HOME: /var/jboss-4.2.3.GA
      
       JAVA: /var/ibm/java2-i386-50/bin/java
      
       JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
      
       CLASSPATH: /var/jboss-4.2.3.GA/bin/run.jar:/var/ibm/java2-i386-50/lib/tools.jar
      
      =========================================================================
      
      09:07:37,160 INFO [Server] Starting JBoss (MX MicroKernel)...
      09:07:37,163 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
      09:07:37,165 INFO [Server] Home Dir: /var/jboss-4.2.3.GA
      09:07:37,165 INFO [Server] Home URL: file:/var/jboss-4.2.3.GA/
      09:07:37,169 INFO [Server] Patch URL: null
      09:07:37,169 INFO [Server] Server Name: default
      09:07:37,170 INFO [Server] Server Home Dir: /var/jboss-4.2.3.GA/server/default
      09:07:37,171 INFO [Server] Server Home URL: file:/var/jboss-4.2.3.GA/server/default/
      09:07:37,171 INFO [Server] Server Log Dir: /var/jboss-4.2.3.GA/server/default/log
      09:07:37,173 INFO [Server] Server Temp Dir: /var/jboss-4.2.3.GA/server/default/tmp
      09:07:37,174 INFO [Server] Root Deployment Filename: jboss-service.xml
      09:07:37,749 INFO [ServerInfo] Java version: 1.5.0,IBM Corporation
      09:07:37,750 INFO [ServerInfo] Java VM: IBM J9 VM 2.3,IBM Corporation
      09:07:37,750 INFO [ServerInfo] OS-System: Linux 2.6.18-128.1.6.el5,x86
      09:07:38,250 INFO [Server] Core system initialized
      09:07:41,757 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      09:07:41,761 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      09:07:42,438 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
      09:07:42,439 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
      09:07:42,696 INFO [TransactionManagerService] Starting recovery manager
      09:07:42,820 INFO [TransactionManagerService] Recovery manager started
      09:07:42,820 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
      09:07:46,609 INFO [EJB3Deployer] Starting java:comp multiplexer
      09:07:50,059 INFO [NativeServerConfig] JBoss Web Services - Native
      09:07:50,059 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
      09:07:51,115 INFO [Embedded] Catalina naming disabled
      09:07:51,310 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /var/ibm/java2-i386-50/jre/bin:/usr/lib
      09:07:51,401 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8989
      09:07:51,403 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
      09:07:51,404 INFO [Catalina] Initialization processed in 288 ms
      09:07:51,405 INFO [StandardService] Starting service jboss.web
      09:07:51,408 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
      09:07:51,454 INFO [Catalina] Server startup in 50 ms
      09:07:51,578 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
      09:07:52,230 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
      09:07:52,407 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
      09:07:52,628 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
      09:07:53,501 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
      09:07:54,025 INFO [MailService] Mail Service bound to java:/Mail
      09:07:54,198 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
      09:07:54,243 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
      09:07:54,307 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
      09:07:54,344 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
      09:07:54,416 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
      09:07:54,453 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
      09:07:54,501 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
      09:07:54,513 INFO [QuartzResourceAdapter] start quartz!!!
      09:07:54,601 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      09:07:54,636 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      09:07:54,640 INFO [RAMJobStore] RAMJobStore initialized.
      09:07:54,641 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      09:07:54,642 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      09:07:54,643 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      09:07:55,540 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      09:07:55,889 INFO [A] Bound to JNDI name: queue/A
      09:07:55,893 INFO [B] Bound to JNDI name: queue/B
      09:07:55,896 INFO [C] Bound to JNDI name: queue/C
      09:07:55,899 INFO [D] Bound to JNDI name: queue/D
      09:07:55,902 INFO [ex] Bound to JNDI name: queue/ex
      09:07:55,925 INFO [testTopic] Bound to JNDI name: topic/testTopic
      09:07:55,929 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      09:07:55,932 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
      09:07:55,937 INFO [testQueue] Bound to JNDI name: queue/testQueue
      09:07:55,996 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
      09:07:56,040 INFO [DLQ] Bound to JNDI name: queue/DLQ
      09:07:56,193 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      09:07:56,225 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      09:07:56,463 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8989
      09:07:56,491 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      09:07:56,506 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 19s:327ms
      


        • 1. Re: Problems Reaching Admin Console
          peterj

          Of course you cannot access it on port 8080 because you changed the port:

          :07:56,463 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8989

          • 2. Re: Problems Reaching Admin Console
            davidz

            Good catch, I forgot about changing the port. My server used to run on Sun One Webserver 7 with the admin port on 8989. I changed the jboss port number to 8989 to make sure that there would be no firewall conflicts.

            However, I still can't access the admin port on either 8080 or 8989. Any other ideas?

            • 3. Re: Problems Reaching Admin Console
              peterj

              I hope the URL you are using is:

              http://localhost:8080

              Nothing else will work since the app server is bound to localhost.

              If you want remote access (or even local access using the hostname), you will need to start with the -b option:

              ./run.sh -b 0.0.0.0

              • 4. Re: Problems Reaching Admin Console
                davidz

                Thanks again! That fixed the problem.

                My server does not have any web browser installed and I always access it via a text based SSH (without X-forwarding enabled). So I was trying to connect remotely to the admin console without the -b option.........