5 Replies Latest reply on Apr 30, 2014 12:38 PM by Bingu Shim

    Why doesn't the admin console work?

    Konrad R Newbie

      When following the "getting started" instructions for running JDG in standalone mode, the server starts up without issue and shows this in the log:

       

      16:08:41,332 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1
      16:08:41,490 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
      16:08:41,534 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss Data Grid 6.2.0 (AS 7.2.1.Final-redhat-10) starting
      16:08:42,096 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
      16:08:42,099 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
      16:08:42,102 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
      16:08:42,109 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1
      16:08:42,142 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 23) JBAS013171: Activating Security Subsystem
      16:08:42,142 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 21) JBAS011800: Activating Naming Subsystem
      16:08:42,142 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 17) JBAS010280: Activating Infinispan subsystem.
      16:08:42,149 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 27) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
      16:08:42,150 INFO  [org.jboss.as.security] (MSC service thread 1-15) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2
      16:08:42,183 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-13) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2)
      16:08:42,189 INFO  [org.jboss.as.naming] (MSC service thread 1-12) JBAS011802: Starting Naming Service
      16:08:42,404 INFO  [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080
      16:08:42,404 INFO  [org.apache.coyote.ajp] (MSC service thread 1-5) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/127.0.0.1:8009
      16:08:42,405 INFO  [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080
      16:08:42,597 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-4) JDGS010000: HotRodServer starting
      16:08:42,600 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-4) JDGS010001: HotRodServer listening on 127.0.0.1:11222
      16:08:42,600 INFO  [org.jboss.as.remoting] (MSC service thread 1-15) JBAS017100: Listening on 127.0.0.1:9999
      16:08:42,600 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
      16:08:42,742 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-14) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.1.Final-redhat-1
      16:08:42,742 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-11) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.1.Final-redhat-1
      16:08:43,173 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
      16:08:43,173 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-11) ISPN000031: MBeans were successfully registered to the platform MBean server.
      16:08:43,173 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-10) ISPN000031: MBeans were successfully registered to the platform MBean server.
      16:08:43,173 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-8) ISPN000031: MBeans were successfully registered to the platform MBean server.
      16:08:43,173 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-14) ISPN000031: MBeans were successfully registered to the platform MBean server.
      16:08:43,176 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-14) JBAS010281: Started memcachedCache cache from local container
      16:08:43,176 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010281: Started default cache from local container
      16:08:43,176 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-8) JBAS010281: Started other cache from security container
      16:08:43,176 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-10) JBAS010281: Started namedCache cache from local container
      16:08:43,176 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-11) JBAS010281: Started jboss-web-policy cache from security container
      16:08:43,183 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-15) JDGS010000: MemcachedServer starting
      16:08:43,183 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-15) JDGS010001: MemcachedServer listening on 127.0.0.1:11211
      16:08:43,187 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-6) JDGS010000: REST starting
      16:08:43,376 INFO  [org.infinispan.server.endpoint] (MSC service thread 1-6) JDGS010002: REST mapped to /rest
      16:08:43,406 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
      16:08:43,406 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
      16:08:43,407 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss Data Grid 6.2.0 (AS 7.2.1.Final-redhat-10) started in 2384ms - Started 92 of 129 services (37 services are passive or on-demand)
      

       

      The http://127.0.0.1:9990 URL just redirected to a blank page at http://127.0.0.1:9990/error/index.html until I used bin/add-user.sh to add an admin user (this is missing from the JDG documentation, but luckily I was familiar with that step from previous JBoss installations.) After adding the admin user, http://127.0.0.1:9990 now instead redirects to http://127.0.0.1:9990/console/index.html but that returns a HTTP 404 response.

       

      Is there anything else I can do to get the console working?

       

      Thanks,

      Konrad

        • 1. Re: Why doesn't the admin console work?
          Tristan Tarrant Master

          Hi Konrad,

           

          we do not package the admin console in JDG / Infinispan Server because it would expose functionality specific to the application server (such as deployments) which are not supported / not functional in our context. The supported management interface is via JON/RHQ.

          • 2. Re: Why doesn't the admin console work?
            Konrad R Newbie

            Thanks for your reply Tristan. I would suggest making that clear in the documentation, and either removing that admin console location from the logging output, or adding a brief explanation page (your message above would be perfect) instead of a 404 error.

            • 3. Re: Why doesn't the admin console work?
              Bingu Shim Newbie

              Hello Tristan,

               

              I'm having a same problem, and as you suggested I have tried using RHQ.

              I've been succeed to launch RHQ agent and server and installed infinispan-rhq plugin, and been able to connect RHQ Console.

               

              But when I add the following line to 'standalone.conf.bat' file to make RHQ console manage the infinispan

               

              set "JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=6996 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"

               

               

              and run 'standalone.bat' I got error some thing like

               

              Calling "D:\00.Infinispan\infinispan-server-6.0.2.Final-bin2\infinispan-server-6.0.2.Final\bin\standalone.conf.bat"
              ===============================================================================
              
              
                JBoss Bootstrap Environment
              
              
                JBOSS_HOME: D:\00.Infinispan\infinispan-server-6.0.2.Final-bin2\infinispan-server-6.0.2.Final
              
              
                JAVA: C:\Program Files\Java\jdk1.7.0_51\bin\java
              
              
                JAVA_OPTS: -XX:+TieredCompilation -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dcom.sun.management.jm
              xremote.port=6996 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.net.preferIPv4Stack=true -Djboss.m
              odules.system.pkgs=org.jboss.byteman
              
              
              ===============================================================================
              
              
              WARNING: Failed to load the specified log manager class org.jboss.logmanager.LogManager
              4월 30, 2014 6:40:34 오후 org.jboss.msc.service.ServiceLogger_$logger greeting
              INFO: JBoss MSC version 1.0.4.GA
              4월 30, 2014 6:40:34 오후 org.jboss.as.server.ApplicationServerService start
              INFO: JBAS015899: JBoss Infinispan Server 6.0.2.Final (AS 7.2.0.Final) starting
              4월 30, 2014 6:40:34 오후 org.jboss.as.controller.AbstractOperationContext executeStep
              ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([])
              java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging
                      at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:99)
                      at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440)
                      at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322)
                      at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229)
                      at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224)
                      at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:172)
                      at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:225)
                      at org.jboss.as.server.ServerService.boot(ServerService.java:333)
                      at org.jboss.as.server.ServerService.boot(ServerService.java:308)
                      at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188)
                      at java.lang.Thread.run(Thread.java:744)
              Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be
              org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "j
              ava.util.logging.manager" and set it to "org.jboss.logmanager.LogManager"
                      at java.util.concurrent.FutureTask.report(FutureTask.java:122)
                      at java.util.concurrent.FutureTask.get(FutureTask.java:188)
                      at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:91)
                      ... 10 more
              Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subs
              ystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "
              org.jboss.logmanager.LogManager"
                      at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:103)
                      at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97)
                      at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127)
                      at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:113)
                      at java.util.concurrent.FutureTask.run(FutureTask.java:262)
                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
                      at java.lang.Thread.run(Thread.java:744)
                      at org.jboss.threads.JBossThread.run(JBossThread.java:122)
              

               

              I googled and found the same question on this board,

              [AS7-1859] AS won't boot with sun jmx enabled - JBoss Issue Tracker

               

              According to David Lloyd's answer, jboss will not support JMX Remote.

               

              This means, there is noway to manage and monitor infinispan on remote location?

               

              I'm really hope there is a way to manage infinispan.

               

               

              Thanks.

               

              Bingu Shim

              • 4. Re: Why doesn't the admin console work?
                Tristan Tarrant Master

                In order to monitor the server with RHQ/JON you need to use the Infinispan/JDG Server plugin for RHQ/JON. This plugin uses the EAP DMR protocol instead of JMX.

                • 5. Re: Re: Why doesn't the admin console work?
                  Bingu Shim Newbie

                  Hi Tristan,

                   

                  Let me ask more questions to make me clear..

                   

                  I followed the instructions on User Guiide : http://infinispan.org/docs/6.0.x/user_guide/user_guide.html#_management_tooling

                   

                  I got this problem with the step 4 in the "14.2 RHQ" section


                  Which is

                   

                  4. At this point, RHQ is ready to start monitoring Infinispan instances, but before firing them up, make sure you start them with the following system properties so that RHQ agents can discover them:

                   

                  -Dcom.sun.management.jmxremote.port=6996 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false

                   

                   

                  I just added these options to the infinispan launch script, then got the error.

                   

                  Should I have to add this option to the RHQ script instead of Infinispan script?

                   

                   

                  Also I want to ask that, the instructions on this guide is what I should do to use the Infinispan/JDG Server plugin for RHQ/JON?