Why doesn't the admin console work?
rokickik Feb 24, 2014 4:56 PMWhen 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