3 Replies Latest reply on Dec 23, 2008 10:22 AM by jaikiran pai

    Unable to open the admin console

    Sanjeev Khurana Newbie

      Hi,
      Port 8080 was already in use so after installing the jboss I changed the port to 28080 in /apps/vendor/jboss/server/default/deploy/jboss-web.deployer/server.xml as below and restarted the jboss.



      When I try to start the web browser http://10.232.11.70:28080/ it doesn't come up show the following error:

      Internet Explorer cannot display the webpage

      Most likely causes:
      You are not connected to the Internet.
      The website is encountering problems.
      There might be a typing error in the address.


      regards,
      Sanjeev.

        • 1. Re: Unable to open the admin console
          jaikiran pai Master

          What command do you use to start JBoss? Which version of JBoss do you use? And please post the console logs.

          While posting logs, remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure your message is correctly formatted.

          • 2. Re: Unable to open the admin console
            Sanjeev Khurana Newbie

            What command do you use to start JBoss?

            /apps/vendor/jboss/bin/run.sh

            Which version of JBoss do you use?

            jboss-4.2.3.GA

            And please post the console logs.



            bash-3.00# ./run.sh
            =========================================================================

            JBoss Bootstrap Environment

            JBOSS_HOME: /apps/vendor/jboss/jboss-4.2.3.GA

            JAVA: java

            JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.clien
            t.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

            CLASSPATH: /apps/vendor/jboss/jboss-4.2.3.GA/bin/run.jar

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

            16:37:42,889 INFO [Server] Starting JBoss (MX MicroKernel)...
            16:37:42,891 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=
            JBoss_4_2_3_GA date=200807181417)
            16:37:42,893 INFO [Server] Home Dir: /apps/vendor/jboss/jboss-4.2.3.GA
            16:37:42,893 INFO [Server] Home URL: file:/apps/vendor/jboss/jboss-4.2.3.GA/
            16:37:42,895 INFO [Server] Patch URL: null
            16:37:42,895 INFO [Server] Server Name: default
            16:37:42,895 INFO [Server] Server Home Dir: /apps/vendor/jboss/jboss-4.2.3.GA/s
            erver/default
            16:37:42,896 INFO [Server] Server Home URL: file:/apps/vendor/jboss/jboss-4.2.3
            .GA/server/default/
            16:37:42,896 INFO [Server] Server Log Dir: /apps/vendor/jboss/jboss-4.2.3.GA/se
            rver/default/log
            16:37:42,897 INFO [Server] Server Temp Dir: /apps/vendor/jboss/jboss-4.2.3.GA/s
            erver/default/tmp
            16:37:42,897 INFO [Server] Root Deployment Filename: jboss-service.xml
            16:37:43,521 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc.
            16:37:43,522 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_04-b05
            ,Sun Microsystems Inc.
            16:37:43,522 INFO [ServerInfo] OS-System: SunOS 5.10,sparc
            16:37:44,211 INFO [Server] Core system initialized
            16:37:48,686 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
            /
            16:37:48,690 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
            ce:jboss-log4j.xml
            16:37:50,143 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
            version) - JBoss Inc.
            16:37:50,143 INFO [TransactionManagerService] Setting up property manager MBean
            and JMX layer
            16:37:50,780 INFO [TransactionManagerService] Starting recovery manager
            16:37:50,952 INFO [TransactionManagerService] Recovery manager started
            16:37:50,952 INFO [TransactionManagerService] Binding TransactionManager JNDI R
            eference
            16:37:56,689 INFO [EJB3Deployer] Starting java:comp multiplexer
            16:38:01,709 INFO [NativeServerConfig] JBoss Web Services - Native
            16:38:01,710 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200
            803312044)
            16:38:03,764 INFO [Embedded] Catalina naming disabled
            16:38:04,675 INFO [AprLifecycleListener] The Apache Tomcat Native library which
            allows optimal performance in production environments was not found on the java
            .library.path: /usr/jdk/instances/jdk1.5.0/jre/lib/sparc/server:/usr/jdk/instanc
            es/jdk1.5.0/jre/lib/sparc:/usr/jdk/instances/jdk1.5.0/jre/../lib/sparc:/usr/lib
            16:38:04,952 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
            .1-28080
            16:38:04,954 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-28
            009
            16:38:04,954 INFO [Catalina] Initialization processed in 1190 ms
            16:38:04,954 INFO [StandardService] Starting service jboss.web
            16:38:04,959 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
            16:38:05,076 INFO [Catalina] Server startup in 121 ms
            16:38:05,286 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
            eb.deployer/ROOT.war/
            16:38:06,513 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
            http-invoker.sar/invoker.war/
            16:38:06,946 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
            jbossws.sar/jbossws-context.war/
            16:38:07,368 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
            deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
            16:38:09,537 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
            loy/management/console-mgr.sar/web-console.war/
            16:38:10,886 INFO [MailService] Mail Service bound to java:/Mail
            16:38:11,348 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/jboss-ha-local-jdbc.rar
            16:38:11,417 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/jboss-ha-xa-jdbc.rar
            16:38:11,468 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/jboss-local-jdbc.rar
            16:38:11,525 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/jboss-xa-jdbc.rar
            16:38:11,627 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/jms/jms-ra.rar
            16:38:11,679 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/mail-ra.rar
            16:38:11,751 INFO [RARDeployment] Required license terms exist, view META-INF/r
            a.xml in .../deploy/quartz-ra.rar
            16:38:11,767 INFO [QuartzResourceAdapter] start quartz!!!
            16:38:11,957 INFO [SimpleThreadPool] Job execution threads will use class loade
            r of thread: main
            16:38:12,010 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
            16:38:12,017 INFO [RAMJobStore] RAMJobStore initialized.
            16:38:12,018 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
            r' initialized from default resource file in Quartz package: 'quartz.properties'
            16:38:12,018 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
            16:38:12,018 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
            TERED started.
            16:38:13,328 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
            oss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
            16:38:13,845 INFO [A] Bound to JNDI name: queue/A
            16:38:13,848 INFO [B] Bound to JNDI name: queue/B
            16:38:13,852 INFO [C] Bound to JNDI name: queue/C
            16:38:13,855 INFO [D] Bound to JNDI name: queue/D
            16:38:13,871 INFO [ex] Bound to JNDI name: queue/ex
            16:38:13,909 INFO [testTopic] Bound to JNDI name: topic/testTopic
            16:38:13,913 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
            16:38:13,916 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
            16:38:13,923 INFO [testQueue] Bound to JNDI name: queue/testQueue
            16:38:14,004 INFO [UILServerILService] JBossMQ UIL service available at : /127.
            0.0.1:8093
            16:38:14,072 INFO [DLQ] Bound to JNDI name: queue/DLQ
            16:38:14,414 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
            oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
            16:38:14,708 INFO [TomcatDeployer] deploy, ctxPath=/GMLCSilmulator, warUrl=.../
            tmp/deploy/tmp65063GMLCSilmulator-exp.war/
            16:38:14,875 INFO [TomcatDeployer] deploy, ctxPath=/helloworld, warUrl=.../tmp/
            deploy/tmp65064helloworld-exp.war/
            16:38:15,133 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
            loy/jmx-console.war/
            16:38:15,576 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-2
            8080
            16:38:15,636 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-28009
            16:38:15,752 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBos
            s_4_2_3_GA date=200807181417)] Started in 32s:851ms

            • 3. Re: Unable to open the admin console
              jaikiran pai Master

               

              /apps/vendor/jboss/bin/run.sh

              16:38:15,576 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-28080


              Use the -b option to start the server. See this for details http://www.jboss.org/community/docs/DOC-10179