Attachment 847459 Details for Bug 1050751 – server.log

server.log

server.log (text/plain), 160.22 KB, created by Viet Nguyen on 2014-01-09 01:48:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Viet Nguyen

Created: 2014-01-09 01:48:13 UTC

Size: 160.22 KB

patch

obsolete

>20:32:23,585 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1
>20:32:23,920 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
>20:32:24,013 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting
>20:32:26,389 INFO  [org.xnio] (MSC service thread 1-15) XNIO Version 3.0.7.GA-redhat-1
>20:32:26,399 INFO  [org.xnio.nio] (MSC service thread 1-15) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
>20:32:26,404 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
>20:32:26,410 INFO  [org.jboss.remoting] (MSC service thread 1-15) JBoss Remoting version 3.2.16.GA-redhat-1
>20:32:26,496 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
>20:32:26,513 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
>20:32:26,530 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem
>20:32:26,538 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem
>20:32:26,592 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-9) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2)
>20:32:26,595 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension
>20:32:26,598 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2
>20:32:26,616 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
>20:32:26,655 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
>20:32:26,662 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
>20:32:26,674 INFO  [org.jboss.jaxr] (MSC service thread 1-4) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
>20:32:26,735 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
>20:32:26,901 INFO  [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.4.Final-redhat-7
>20:32:26,937 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingjournal,bindingsDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingbindings,largeMessagesDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messaginglargemessages,pagingDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingpaging)
>20:32:26,944 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221006: Waiting to obtain live lock
>20:32:26,997 INFO  [org.apache.coyote.http11] (MSC service thread 1-10) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/10.16.90.16:8080
>20:32:26,998 INFO  [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
>20:32:27,094 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221013: Using NIO Journal
>20:32:27,103 INFO  [org.apache.coyote.http11] (MSC service thread 1-10) JBWEB003000: Coyote HTTP/1.1 starting on: http-/10.16.90.16:8080
>20:32:27,261 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221034: Waiting to obtain live lock
>20:32:27,263 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221035: Live Server Obtained live lock
>20:32:27,286 INFO  [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016328: CORBA Naming Service started
>20:32:27,288 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-10) JBAS015012: Started FileSystemDeploymentService for directory /qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/deployments
>20:32:27,290 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-10) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
>20:32:27,302 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 10.16.90.16:4447
>20:32:27,303 INFO  [org.jboss.as.remoting] (MSC service thread 1-11) JBAS017100: Listening on 10.16.90.16:6999
>20:32:28,104 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 10.16.90.16:5445 for CORE protocol
>20:32:28,110 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 10.16.90.16:5455 for CORE protocol
>20:32:28,113 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221007: Server is now live
>20:32:28,114 INFO  [org.hornetq.core.server] (MSC service thread 1-16) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [e5be279b-78cd-11e3-8423-6bf8f126e566] 
>20:32:28,163 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
>20:32:28,168 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
>20:32:28,239 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
>20:32:28,302 INFO  [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
>20:32:28,303 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
>20:32:28,311 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-9) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
>20:32:28,381 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://10.16.90.16:6990/management
>20:32:28,382 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://10.16.90.16:6990
>20:32:28,383 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started in 5381ms - Started 145 of 207 services (61 services are passive or on-demand)
>20:33:07,009 INFO  [org.apache.coyote.http11] (MSC service thread 1-13) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/10.16.90.16:7443
>20:33:07,010 INFO  [org.apache.coyote.http11] (MSC service thread 1-13) JBWEB003000: Coyote HTTP/1.1 starting on: http-/10.16.90.16:7443
>20:33:07,294 INFO  [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 2) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2)
>20:33:07,372 INFO  [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 4) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
>20:33:07,543 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:jboss/datasources/NoTxRHQDS]
>20:33:07,641 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:jboss/datasources/RHQDS]
>20:33:07,717 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.AlertConditionQueue
>20:33:07,788 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/AlertConditionQueue
>20:33:07,851 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftChangesetQueue
>20:33:07,856 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftChangesetQueue
>20:33:07,903 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftFileQueue
>20:33:07,908 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftFileQueue
>20:33:08,063 INFO  [org.jboss.as.server] (management-handler-thread - 3) JBAS015888: Creating http management service using socket-binding (management-http)
>20:33:08,076 INFO  [org.apache.catalina.core] (MSC service thread 1-9) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
>20:33:08,139 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
>20:33:14,114 INFO  [org.apache.catalina.core] (MSC service thread 1-11) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
>20:33:14,118 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010409: Unbound data source [java:jboss/datasources/RHQDS]
>20:33:14,118 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010409: Unbound data source [java:jboss/datasources/NoTxRHQDS]
>20:33:14,124 INFO  [org.jboss.jaxr] (MSC service thread 1-15) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory
>20:33:14,126 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
>20:33:14,129 INFO  [org.apache.coyote.http11] (MSC service thread 1-9) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.90.16:7443
>20:33:14,129 INFO  [org.apache.coyote.http11] (MSC service thread 1-9) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.90.16:7443
>20:33:14,129 INFO  [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.90.16:8080
>20:33:14,130 INFO  [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.90.16:8080
>20:33:14,139 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory
>20:33:14,146 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011605: Unbound messaging object to jndi name java:/queue/AlertConditionQueue
>20:33:14,154 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011605: Unbound messaging object to jndi name java:/queue/DriftFileQueue
>20:33:14,157 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
>20:33:14,160 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011605: Unbound messaging object to jndi name java:/queue/DriftChangesetQueue
>20:33:14,185 INFO  [org.hornetq.ra] (MSC service thread 1-4) HQ151003: HornetQ resource adaptor stopped
>20:33:14,228 INFO  [org.hornetq.core.server] (MSC service thread 1-15) HQ221002: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [e5be279b-78cd-11e3-8423-6bf8f126e566] stopped
>20:33:14,258 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-15) JBAS015401: Unbound mail session [java:jboss/mail/Default]
>20:33:14,273 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) stopped in 191ms
>20:33:14,276 INFO  [org.jboss.as] (MSC service thread 1-13) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting
>20:33:14,506 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
>20:33:14,534 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
>20:33:14,536 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
>20:33:14,544 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-10) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2)
>20:33:14,550 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem
>20:33:14,558 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem
>20:33:14,561 INFO  [org.jboss.as.jacorb] (MSC service thread 1-9) JBAS016330: CORBA ORB Service started
>20:33:14,563 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension
>20:33:14,570 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.4.Final-redhat-7
>20:33:14,580 INFO  [org.jboss.as.security] (MSC service thread 1-12) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2
>20:33:14,587 INFO  [org.jboss.as.jacorb] (MSC service thread 1-8) JBAS016328: CORBA Naming Service started
>20:33:14,592 INFO  [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
>20:33:14,598 INFO  [org.jboss.jaxr] (MSC service thread 1-7) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
>20:33:14,617 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
>20:33:14,618 INFO  [org.apache.coyote.http11] (MSC service thread 1-15) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/10.16.90.16:7080
>20:33:14,619 INFO  [org.apache.coyote.http11] (MSC service thread 1-15) JBWEB003000: Coyote HTTP/1.1 starting on: http-/10.16.90.16:7080
>20:33:14,623 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingjournal,bindingsDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingbindings,largeMessagesDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messaginglargemessages,pagingDirectory=/qa/home/vnguyen/jon-server-3.2.0.GA/jbossas/standalone/data/messagingpaging)
>20:33:14,624 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221006: Waiting to obtain live lock
>20:33:14,623 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
>20:33:14,625 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221013: Using NIO Journal
>20:33:14,635 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221034: Waiting to obtain live lock
>20:33:14,636 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221035: Live Server Obtained live lock
>20:33:14,655 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2)
>20:33:14,690 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
>20:33:14,696 INFO  [org.apache.coyote.http11] (MSC service thread 1-10) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/10.16.90.16:7443
>20:33:14,709 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-13) JBAS010400: Bound data source [java:jboss/datasources/NoTxRHQDS]
>20:33:14,706 INFO  [org.apache.coyote.http11] (MSC service thread 1-10) JBWEB003000: Coyote HTTP/1.1 starting on: http-/10.16.90.16:7443
>20:33:14,711 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-16) JBAS010400: Bound data source [java:jboss/datasources/RHQDS]
>20:33:14,753 INFO  [org.jboss.as.remoting] (MSC service thread 1-15) JBAS017100: Listening on 10.16.90.16:6999
>20:33:14,754 INFO  [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on 10.16.90.16:3447
>20:33:15,129 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 10.16.90.16:4455 for CORE protocol
>20:33:15,130 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 10.16.90.16:4449 for CORE protocol
>20:33:15,132 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221007: Server is now live
>20:33:15,132 INFO  [org.hornetq.core.server] (MSC service thread 1-7) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [e5be279b-78cd-11e3-8423-6bf8f126e566] 
>20:33:15,136 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.DriftFileQueue
>20:33:15,143 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/queue/DriftFileQueue
>20:33:15,145 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
>20:33:15,146 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.AlertConditionQueue
>20:33:15,148 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/queue/AlertConditionQueue
>20:33:15,149 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA
>20:33:15,149 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftChangesetQueue
>20:33:15,151 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftChangesetQueue
>20:33:15,153 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
>20:33:15,158 INFO  [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started
>20:33:15,159 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra
>20:33:15,162 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-12) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
>20:33:15,253 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://10.16.90.16:6990/management
>20:33:15,255 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
>20:33:15,255 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started in 977ms - Started 155 of 232 services (71 services are passive or on-demand)
>20:33:15,355 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of "rhq.ear" (runtime-name: "rhq.ear")
>20:33:22,993 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jaxb-api.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/lib/jaxb-impl-2.2.4.jar  does not point to a valid jar for a Class-Path reference.
>20:33:22,994 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry activation.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/lib/jaxb-impl-2.2.4.jar  does not point to a valid jar for a Class-Path reference.
>20:33:22,995 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jsr173_1.0_api.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/lib/jaxb-impl-2.2.4.jar  does not point to a valid jar for a Class-Path reference.
>20:33:22,996 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry jaxb1-impl.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/lib/jaxb-impl-2.2.4.jar  does not point to a valid jar for a Class-Path reference.
>20:33:23,020 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-downloads.war")
>20:33:23,020 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "null" (runtime-name: "coregui.war")
>20:33:23,020 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-server.jar")
>20:33:23,021 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-rest-examples.war")
>20:33:23,021 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-rest.war")
>20:33:23,022 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-portal.war")
>20:33:23,022 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-client.war")
>20:33:23,022 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-content_http.war")
>20:33:23,023 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-remoting.war")
>20:33:23,023 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-core-domain-ejb3.jar")
>20:33:23,022 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-agentupdate.war")
>20:33:23,293 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry lib/postgresql-9.2-1002.jdbc4.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar  does not point to a valid jar for a Class-Path reference.
>20:33:23,319 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry lib/activation-1.1.1.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar  does not point to a valid jar for a Class-Path reference.
>20:33:23,351 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015960: Class Path entry lib/snakeyaml-1.8.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,473 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry commons-beanutils.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,474 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry commons-digester.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,475 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry commons-fileupload.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,476 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry commons-logging.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,477 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry commons-validator.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,478 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015960: Class Path entry jakarta-oro.jar in /qa/home/vnguyen/jon-server-3.2.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-portal.war/WEB-INF/lib/struts-1.2.9.jar  does not point to a valid jar for a Class-Path reference.
>20:33:27,678 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for rhqpu
>20:33:41,077 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice.
>20:33:41,078 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.controller:main") which may be changed or removed in future versions without notice.
>20:33:41,078 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
>20:33:41,078 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.server:main") which may be changed or removed in future versions without notice.
>20:33:41,079 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
>20:33:41,079 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
>20:33:41,080 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice.
>20:33:41,081 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice.
>20:33:41,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.common-core:main") which may be changed or removed in future versions without notice.
>20:33:41,082 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.common-core:main") which may be changed or removed in future versions without notice.
>20:33:41,083 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
>20:33:41,083 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
>20:33:41,083 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice.
>20:33:41,084 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice.
>20:33:41,084 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice.
>20:33:41,084 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice.
>20:33:41,111 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-jaxrs:main") which may be changed or removed in future versions without notice.
>20:33:41,112 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-jaxrs:main") which may be changed or removed in future versions without notice.
>20:33:41,114 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
>20:33:41,115 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
>20:33:41,116 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
>20:33:41,116 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.jboss.as.naming:main") which may be changed or removed in future versions without notice.
>20:33:41,136 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice.
>20:33:41,136 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-13) JBAS018567: Deployment "deployment.rhq.ear.rhq-server.jar" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice.
>20:33:43,268 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-12) JBAS018567: Deployment "deployment.rhq.ear.rhq-portal.war" is using a private module ("com.sun.jsf-impl:1.2") which may be changed or removed in future versions without notice.
>20:33:43,269 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-12) JBAS018567: Deployment "deployment.rhq.ear.rhq-portal.war" is using a private module ("com.sun.jsf-impl:1.2") which may be changed or removed in future versions without notice.
>20:33:46,346 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named UserHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/UserHandlerBean!org.rhq.enterprise.server.rest.UserHandlerBean
>	java:app/rhq-server/UserHandlerBean!org.rhq.enterprise.server.rest.UserHandlerBean
>	java:module/UserHandlerBean!org.rhq.enterprise.server.rest.UserHandlerBean
>	java:global/rhq/rhq-server/UserHandlerBean
>	java:app/rhq-server/UserHandlerBean
>	java:module/UserHandlerBean
>
>20:33:46,347 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named OperationHistorySubsystemManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/OperationHistorySubsystemManagerBean!org.rhq.enterprise.server.subsystem.OperationHistorySubsystemManagerLocal
>	java:app/rhq-server/OperationHistorySubsystemManagerBean!org.rhq.enterprise.server.subsystem.OperationHistorySubsystemManagerLocal
>	java:module/OperationHistorySubsystemManagerBean!org.rhq.enterprise.server.subsystem.OperationHistorySubsystemManagerLocal
>	java:global/rhq/rhq-server/OperationHistorySubsystemManagerBean
>	java:app/rhq-server/OperationHistorySubsystemManagerBean
>	java:module/OperationHistorySubsystemManagerBean
>
>20:33:46,348 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DashboardManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerRemote
>	java:app/rhq-server/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerRemote
>	java:module/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerRemote
>	java:jboss/exported/rhq/rhq-server/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerRemote
>	java:global/rhq/rhq-server/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerLocal
>	java:app/rhq-server/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerLocal
>	java:module/DashboardManagerBean!org.rhq.enterprise.server.dashboard.DashboardManagerLocal
>
>20:33:46,348 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CallTimeDataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerLocal
>	java:app/rhq-server/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerLocal
>	java:module/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerLocal
>	java:global/rhq/rhq-server/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerRemote
>	java:app/rhq-server/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerRemote
>	java:module/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerRemote
>	java:jboss/exported/rhq/rhq-server/CallTimeDataManagerBean!org.rhq.enterprise.server.measurement.CallTimeDataManagerRemote
>
>20:33:46,349 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named LdapGroupManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/LdapGroupManagerBean!org.rhq.enterprise.server.resource.group.LdapGroupManagerLocal
>	java:app/rhq-server/LdapGroupManagerBean!org.rhq.enterprise.server.resource.group.LdapGroupManagerLocal
>	java:module/LdapGroupManagerBean!org.rhq.enterprise.server.resource.group.LdapGroupManagerLocal
>	java:global/rhq/rhq-server/LdapGroupManagerBean
>	java:app/rhq-server/LdapGroupManagerBean
>	java:module/LdapGroupManagerBean
>
>20:33:46,349 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementChartsManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementChartsManagerBean!org.rhq.enterprise.server.measurement.MeasurementChartsManagerLocal
>	java:app/rhq-server/MeasurementChartsManagerBean!org.rhq.enterprise.server.measurement.MeasurementChartsManagerLocal
>	java:module/MeasurementChartsManagerBean!org.rhq.enterprise.server.measurement.MeasurementChartsManagerLocal
>	java:global/rhq/rhq-server/MeasurementChartsManagerBean
>	java:app/rhq-server/MeasurementChartsManagerBean
>	java:module/MeasurementChartsManagerBean
>
>20:33:46,349 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SchedulerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SchedulerBean!org.rhq.enterprise.server.scheduler.SchedulerLocal
>	java:app/rhq-server/SchedulerBean!org.rhq.enterprise.server.scheduler.SchedulerLocal
>	java:module/SchedulerBean!org.rhq.enterprise.server.scheduler.SchedulerLocal
>	java:global/rhq/rhq-server/SchedulerBean
>	java:app/rhq-server/SchedulerBean
>	java:module/SchedulerBean
>
>20:33:46,350 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementBaselineManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerRemote
>	java:app/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerRemote
>	java:module/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerRemote
>	java:jboss/exported/rhq/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerRemote
>	java:global/rhq/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerLocal
>	java:app/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerLocal
>	java:module/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerLocal
>
>20:33:46,350 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SynchronizationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerRemote
>	java:app/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerRemote
>	java:module/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerRemote
>	java:jboss/exported/rhq/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerRemote
>	java:global/rhq/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerLocal
>	java:app/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerLocal
>	java:module/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerLocal
>
>20:33:46,350 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertTemplateManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertTemplateManagerBean!org.rhq.enterprise.server.alert.AlertTemplateManagerLocal
>	java:app/rhq-server/AlertTemplateManagerBean!org.rhq.enterprise.server.alert.AlertTemplateManagerLocal
>	java:module/AlertTemplateManagerBean!org.rhq.enterprise.server.alert.AlertTemplateManagerLocal
>	java:global/rhq/rhq-server/AlertTemplateManagerBean
>	java:app/rhq-server/AlertTemplateManagerBean
>	java:module/AlertTemplateManagerBean
>
>20:33:46,351 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementScheduleManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerRemote
>	java:app/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerRemote
>	java:module/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerRemote
>	java:jboss/exported/rhq/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerRemote
>	java:global/rhq/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerLocal
>	java:app/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerLocal
>	java:module/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerLocal
>
>20:33:46,351 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CacheConsistencyManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CacheConsistencyManagerBean!org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerLocal
>	java:app/rhq-server/CacheConsistencyManagerBean!org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerLocal
>	java:module/CacheConsistencyManagerBean!org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerLocal
>	java:global/rhq/rhq-server/CacheConsistencyManagerBean
>	java:app/rhq-server/CacheConsistencyManagerBean
>	java:module/CacheConsistencyManagerBean
>
>20:33:46,351 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceBossBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceBossBean!org.rhq.enterprise.server.resource.ResourceBossLocal
>	java:app/rhq-server/ResourceBossBean!org.rhq.enterprise.server.resource.ResourceBossLocal
>	java:module/ResourceBossBean!org.rhq.enterprise.server.resource.ResourceBossLocal
>	java:global/rhq/rhq-server/ResourceBossBean
>	java:app/rhq-server/ResourceBossBean
>	java:module/ResourceBossBean
>
>20:33:46,352 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ConfigurationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerRemote
>	java:app/rhq-server/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerRemote
>	java:module/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerRemote
>	java:jboss/exported/rhq/rhq-server/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerRemote
>	java:global/rhq/rhq-server/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerLocal
>	java:app/rhq-server/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerLocal
>	java:module/ConfigurationManagerBean!org.rhq.enterprise.server.configuration.ConfigurationManagerLocal
>
>20:33:46,352 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerRemote
>	java:app/rhq-server/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerRemote
>	java:module/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerRemote
>	java:jboss/exported/rhq/rhq-server/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerRemote
>	java:global/rhq/rhq-server/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerLocal
>	java:app/rhq-server/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerLocal
>	java:module/ResourceManagerBean!org.rhq.enterprise.server.resource.ResourceManagerLocal
>
>20:33:46,353 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StartupBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StartupBean!org.rhq.enterprise.server.core.StartupLocal
>	java:app/rhq-server/StartupBean!org.rhq.enterprise.server.core.StartupLocal
>	java:module/StartupBean!org.rhq.enterprise.server.core.StartupLocal
>	java:global/rhq/rhq-server/StartupBean
>	java:app/rhq-server/StartupBean
>	java:module/StartupBean
>
>20:33:46,353 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named GroupDefinitionRecalculationThreadMonitor in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/GroupDefinitionRecalculationThreadMonitor!org.rhq.enterprise.server.resource.group.definition.mbean.GroupDefinitionRecalculationThreadMonitor
>	java:app/rhq-server/GroupDefinitionRecalculationThreadMonitor!org.rhq.enterprise.server.resource.group.definition.mbean.GroupDefinitionRecalculationThreadMonitor
>	java:module/GroupDefinitionRecalculationThreadMonitor!org.rhq.enterprise.server.resource.group.definition.mbean.GroupDefinitionRecalculationThreadMonitor
>	java:global/rhq/rhq-server/GroupDefinitionRecalculationThreadMonitor
>	java:app/rhq-server/GroupDefinitionRecalculationThreadMonitor
>	java:module/GroupDefinitionRecalculationThreadMonitor
>
>20:33:46,353 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertNotificationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertNotificationManagerBean!org.rhq.enterprise.server.alert.AlertNotificationManagerLocal
>	java:app/rhq-server/AlertNotificationManagerBean!org.rhq.enterprise.server.alert.AlertNotificationManagerLocal
>	java:module/AlertNotificationManagerBean!org.rhq.enterprise.server.alert.AlertNotificationManagerLocal
>	java:global/rhq/rhq-server/AlertNotificationManagerBean
>	java:app/rhq-server/AlertNotificationManagerBean
>	java:module/AlertNotificationManagerBean
>
>20:33:46,353 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named OperationsHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/OperationsHandlerBean!org.rhq.enterprise.server.rest.OperationsHandlerBean
>	java:app/rhq-server/OperationsHandlerBean!org.rhq.enterprise.server.rest.OperationsHandlerBean
>	java:module/OperationsHandlerBean!org.rhq.enterprise.server.rest.OperationsHandlerBean
>	java:global/rhq/rhq-server/OperationsHandlerBean
>	java:app/rhq-server/OperationsHandlerBean
>	java:module/OperationsHandlerBean
>
>20:33:46,354 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ReportsHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ReportsHandlerBean!org.rhq.enterprise.server.rest.ReportsHandlerBean
>	java:app/rhq-server/ReportsHandlerBean!org.rhq.enterprise.server.rest.ReportsHandlerBean
>	java:module/ReportsHandlerBean!org.rhq.enterprise.server.rest.ReportsHandlerBean
>	java:global/rhq/rhq-server/ReportsHandlerBean
>	java:app/rhq-server/ReportsHandlerBean
>	java:module/ReportsHandlerBean
>
>20:33:46,354 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CoreServer in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CoreServer!org.rhq.enterprise.server.core.CoreServer
>	java:app/rhq-server/CoreServer!org.rhq.enterprise.server.core.CoreServer
>	java:module/CoreServer!org.rhq.enterprise.server.core.CoreServer
>	java:global/rhq/rhq-server/CoreServer
>	java:app/rhq-server/CoreServer
>	java:module/CoreServer
>
>20:33:46,354 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PartitionEventManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PartitionEventManagerBean!org.rhq.enterprise.server.cloud.PartitionEventManagerLocal
>	java:app/rhq-server/PartitionEventManagerBean!org.rhq.enterprise.server.cloud.PartitionEventManagerLocal
>	java:module/PartitionEventManagerBean!org.rhq.enterprise.server.cloud.PartitionEventManagerLocal
>	java:global/rhq/rhq-server/PartitionEventManagerBean
>	java:app/rhq-server/PartitionEventManagerBean
>	java:module/PartitionEventManagerBean
>
>20:33:46,355 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StatusManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StatusManagerBean!org.rhq.enterprise.server.cloud.StatusManagerLocal
>	java:app/rhq-server/StatusManagerBean!org.rhq.enterprise.server.cloud.StatusManagerLocal
>	java:module/StatusManagerBean!org.rhq.enterprise.server.cloud.StatusManagerLocal
>	java:global/rhq/rhq-server/StatusManagerBean
>	java:app/rhq-server/StatusManagerBean
>	java:module/StatusManagerBean
>
>20:33:46,355 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ServerManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ServerManagerBean!org.rhq.enterprise.server.cloud.instance.ServerManagerLocal
>	java:app/rhq-server/ServerManagerBean!org.rhq.enterprise.server.cloud.instance.ServerManagerLocal
>	java:module/ServerManagerBean!org.rhq.enterprise.server.cloud.instance.ServerManagerLocal
>	java:global/rhq/rhq-server/ServerManagerBean
>	java:app/rhq-server/ServerManagerBean
>	java:module/ServerManagerBean
>
>20:33:46,355 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ConfigurationHistoryHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ConfigurationHistoryHandler!org.rhq.enterprise.server.rest.reporting.ConfigurationHistoryLocal
>	java:app/rhq-server/ConfigurationHistoryHandler!org.rhq.enterprise.server.rest.reporting.ConfigurationHistoryLocal
>	java:module/ConfigurationHistoryHandler!org.rhq.enterprise.server.rest.reporting.ConfigurationHistoryLocal
>	java:global/rhq/rhq-server/ConfigurationHistoryHandler
>	java:app/rhq-server/ConfigurationHistoryHandler
>	java:module/ConfigurationHistoryHandler
>
>20:33:46,356 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named InventoryManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/InventoryManagerBean!org.rhq.enterprise.server.inventory.InventoryManagerLocal
>	java:app/rhq-server/InventoryManagerBean!org.rhq.enterprise.server.inventory.InventoryManagerLocal
>	java:module/InventoryManagerBean!org.rhq.enterprise.server.inventory.InventoryManagerLocal
>	java:global/rhq/rhq-server/InventoryManagerBean
>	java:app/rhq-server/InventoryManagerBean
>	java:module/InventoryManagerBean
>
>20:33:46,356 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CachedConditionProducerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CachedConditionProducerBean!org.rhq.enterprise.server.alert.engine.jms.CachedConditionProducerLocal
>	java:app/rhq-server/CachedConditionProducerBean!org.rhq.enterprise.server.alert.engine.jms.CachedConditionProducerLocal
>	java:module/CachedConditionProducerBean!org.rhq.enterprise.server.alert.engine.jms.CachedConditionProducerLocal
>	java:global/rhq/rhq-server/CachedConditionProducerBean
>	java:app/rhq-server/CachedConditionProducerBean
>	java:module/CachedConditionProducerBean
>
>20:33:46,356 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentSourceManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentSourceManagerBean!org.rhq.enterprise.server.content.ContentSourceManagerLocal
>	java:app/rhq-server/ContentSourceManagerBean!org.rhq.enterprise.server.content.ContentSourceManagerLocal
>	java:module/ContentSourceManagerBean!org.rhq.enterprise.server.content.ContentSourceManagerLocal
>	java:global/rhq/rhq-server/ContentSourceManagerBean
>	java:app/rhq-server/ContentSourceManagerBean
>	java:module/ContentSourceManagerBean
>
>20:33:46,357 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MetricHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MetricHandlerBean!org.rhq.enterprise.server.rest.MetricHandlerBean
>	java:app/rhq-server/MetricHandlerBean!org.rhq.enterprise.server.rest.MetricHandlerBean
>	java:module/MetricHandlerBean!org.rhq.enterprise.server.rest.MetricHandlerBean
>	java:global/rhq/rhq-server/MetricHandlerBean
>	java:app/rhq-server/MetricHandlerBean
>	java:module/MetricHandlerBean
>
>20:33:46,357 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceTypeHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceTypeHandlerBean!org.rhq.enterprise.server.rest.ResourceTypeHandlerBean
>	java:app/rhq-server/ResourceTypeHandlerBean!org.rhq.enterprise.server.rest.ResourceTypeHandlerBean
>	java:module/ResourceTypeHandlerBean!org.rhq.enterprise.server.rest.ResourceTypeHandlerBean
>	java:global/rhq/rhq-server/ResourceTypeHandlerBean
>	java:app/rhq-server/ResourceTypeHandlerBean
>	java:module/ResourceTypeHandlerBean
>
>20:33:46,357 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertSubsystemManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertSubsystemManagerBean!org.rhq.enterprise.server.subsystem.AlertSubsystemManagerLocal
>	java:app/rhq-server/AlertSubsystemManagerBean!org.rhq.enterprise.server.subsystem.AlertSubsystemManagerLocal
>	java:module/AlertSubsystemManagerBean!org.rhq.enterprise.server.subsystem.AlertSubsystemManagerLocal
>	java:global/rhq/rhq-server/AlertSubsystemManagerBean
>	java:app/rhq-server/AlertSubsystemManagerBean
>	java:module/AlertSubsystemManagerBean
>
>20:33:46,358 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AvailabilityManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerLocal
>	java:app/rhq-server/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerLocal
>	java:module/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerLocal
>	java:global/rhq/rhq-server/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerRemote
>	java:app/rhq-server/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerRemote
>	java:module/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerRemote
>	java:jboss/exported/rhq/rhq-server/AvailabilityManagerBean!org.rhq.enterprise.server.measurement.AvailabilityManagerRemote
>
>20:33:46,358 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SubjectPreferencesCacheBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SubjectPreferencesCacheBean!org.rhq.enterprise.server.auth.prefs.SubjectPreferencesCacheLocal
>	java:app/rhq-server/SubjectPreferencesCacheBean!org.rhq.enterprise.server.auth.prefs.SubjectPreferencesCacheLocal
>	java:module/SubjectPreferencesCacheBean!org.rhq.enterprise.server.auth.prefs.SubjectPreferencesCacheLocal
>	java:global/rhq/rhq-server/SubjectPreferencesCacheBean
>	java:app/rhq-server/SubjectPreferencesCacheBean
>	java:module/SubjectPreferencesCacheBean
>
>20:33:46,358 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.AlertMetadataManagerLocal
>	java:app/rhq-server/AlertMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.AlertMetadataManagerLocal
>	java:module/AlertMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.AlertMetadataManagerLocal
>	java:global/rhq/rhq-server/AlertMetadataManagerBean
>	java:app/rhq-server/AlertMetadataManagerBean
>	java:module/AlertMetadataManagerBean
>
>20:33:46,359 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceAvailabilityManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceAvailabilityManagerBean!org.rhq.enterprise.server.resource.ResourceAvailabilityManagerLocal
>	java:app/rhq-server/ResourceAvailabilityManagerBean!org.rhq.enterprise.server.resource.ResourceAvailabilityManagerLocal
>	java:module/ResourceAvailabilityManagerBean!org.rhq.enterprise.server.resource.ResourceAvailabilityManagerLocal
>	java:global/rhq/rhq-server/ResourceAvailabilityManagerBean
>	java:app/rhq-server/ResourceAvailabilityManagerBean
>	java:module/ResourceAvailabilityManagerBean
>
>20:33:46,359 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ProductVersionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ProductVersionManagerBean!org.rhq.enterprise.server.resource.ProductVersionManagerLocal
>	java:app/rhq-server/ProductVersionManagerBean!org.rhq.enterprise.server.resource.ProductVersionManagerLocal
>	java:module/ProductVersionManagerBean!org.rhq.enterprise.server.resource.ProductVersionManagerLocal
>	java:global/rhq/rhq-server/ProductVersionManagerBean
>	java:app/rhq-server/ProductVersionManagerBean
>	java:module/ProductVersionManagerBean
>
>20:33:46,359 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertDefinitionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerLocal
>	java:app/rhq-server/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerLocal
>	java:module/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerLocal
>	java:global/rhq/rhq-server/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerRemote
>	java:app/rhq-server/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerRemote
>	java:module/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerRemote
>	java:jboss/exported/rhq/rhq-server/AlertDefinitionManagerBean!org.rhq.enterprise.server.alert.AlertDefinitionManagerRemote
>
>20:33:46,360 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named OperationMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/OperationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.OperationMetadataManagerLocal
>	java:app/rhq-server/OperationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.OperationMetadataManagerLocal
>	java:module/OperationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.OperationMetadataManagerLocal
>	java:global/rhq/rhq-server/OperationMetadataManagerBean
>	java:app/rhq-server/OperationMetadataManagerBean
>	java:module/OperationMetadataManagerBean
>
>20:33:46,360 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceHandlerBean!org.rhq.enterprise.server.rest.ResourceHandlerBean
>	java:app/rhq-server/ResourceHandlerBean!org.rhq.enterprise.server.rest.ResourceHandlerBean
>	java:module/ResourceHandlerBean!org.rhq.enterprise.server.rest.ResourceHandlerBean
>	java:global/rhq/rhq-server/ResourceHandlerBean
>	java:app/rhq-server/ResourceHandlerBean
>	java:module/ResourceHandlerBean
>
>20:33:46,360 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementDefinitionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerRemote
>	java:app/rhq-server/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerRemote
>	java:module/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerRemote
>	java:jboss/exported/rhq/rhq-server/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerRemote
>	java:global/rhq/rhq-server/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerLocal
>	java:app/rhq-server/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerLocal
>	java:module/MeasurementDefinitionManagerBean!org.rhq.enterprise.server.measurement.MeasurementDefinitionManagerLocal
>
>20:33:46,361 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentSourceMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentSourceMetadataManagerBean!org.rhq.enterprise.server.content.metadata.ContentSourceMetadataManagerLocal
>	java:app/rhq-server/ContentSourceMetadataManagerBean!org.rhq.enterprise.server.content.metadata.ContentSourceMetadataManagerLocal
>	java:module/ContentSourceMetadataManagerBean!org.rhq.enterprise.server.content.metadata.ContentSourceMetadataManagerLocal
>	java:global/rhq/rhq-server/ContentSourceMetadataManagerBean
>	java:app/rhq-server/ContentSourceMetadataManagerBean
>	java:module/ContentSourceMetadataManagerBean
>
>20:33:46,361 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertConditionLogManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertConditionLogManagerBean!org.rhq.enterprise.server.alert.AlertConditionLogManagerLocal
>	java:app/rhq-server/AlertConditionLogManagerBean!org.rhq.enterprise.server.alert.AlertConditionLogManagerLocal
>	java:module/AlertConditionLogManagerBean!org.rhq.enterprise.server.alert.AlertConditionLogManagerLocal
>	java:global/rhq/rhq-server/AlertConditionLogManagerBean
>	java:app/rhq-server/AlertConditionLogManagerBean
>	java:module/AlertConditionLogManagerBean
>
>20:33:46,361 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ContentMetadataManagerLocal
>	java:app/rhq-server/ContentMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ContentMetadataManagerLocal
>	java:module/ContentMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ContentMetadataManagerLocal
>	java:global/rhq/rhq-server/ContentMetadataManagerBean
>	java:app/rhq-server/ContentMetadataManagerBean
>	java:module/ContentMetadataManagerBean
>
>20:33:46,362 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ClusterManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerRemote
>	java:app/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerRemote
>	java:module/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerRemote
>	java:jboss/exported/rhq/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerRemote
>	java:global/rhq/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerLocal
>	java:app/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerLocal
>	java:module/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerLocal
>
>20:33:46,362 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DynamicConfigurationPropertyBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DynamicConfigurationPropertyBean!org.rhq.enterprise.server.configuration.DynamicConfigurationPropertyLocal
>	java:app/rhq-server/DynamicConfigurationPropertyBean!org.rhq.enterprise.server.configuration.DynamicConfigurationPropertyLocal
>	java:module/DynamicConfigurationPropertyBean!org.rhq.enterprise.server.configuration.DynamicConfigurationPropertyLocal
>	java:global/rhq/rhq-server/DynamicConfigurationPropertyBean
>	java:app/rhq-server/DynamicConfigurationPropertyBean
>	java:module/DynamicConfigurationPropertyBean
>
>20:33:46,362 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ServerPluginsBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ServerPluginsBean!org.rhq.enterprise.server.plugin.ServerPluginsLocal
>	java:app/rhq-server/ServerPluginsBean!org.rhq.enterprise.server.plugin.ServerPluginsLocal
>	java:module/ServerPluginsBean!org.rhq.enterprise.server.plugin.ServerPluginsLocal
>	java:global/rhq/rhq-server/ServerPluginsBean
>	java:app/rhq-server/ServerPluginsBean
>	java:module/ServerPluginsBean
>
>20:33:46,363 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PluginDeploymentScanner in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PluginDeploymentScanner!org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner
>	java:app/rhq-server/PluginDeploymentScanner!org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner
>	java:module/PluginDeploymentScanner!org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner
>	java:global/rhq/rhq-server/PluginDeploymentScanner
>	java:app/rhq-server/PluginDeploymentScanner
>	java:module/PluginDeploymentScanner
>
>20:33:46,363 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RecentDriftHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RecentDriftHandler!org.rhq.enterprise.server.rest.reporting.RecentDriftLocal
>	java:app/rhq-server/RecentDriftHandler!org.rhq.enterprise.server.rest.reporting.RecentDriftLocal
>	java:module/RecentDriftHandler!org.rhq.enterprise.server.rest.reporting.RecentDriftLocal
>	java:global/rhq/rhq-server/RecentDriftHandler
>	java:app/rhq-server/RecentDriftHandler
>	java:module/RecentDriftHandler
>
>20:33:46,363 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StatusHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StatusHandlerBean!org.rhq.enterprise.server.rest.StatusHandlerBean
>	java:app/rhq-server/StatusHandlerBean!org.rhq.enterprise.server.rest.StatusHandlerBean
>	java:module/StatusHandlerBean!org.rhq.enterprise.server.rest.StatusHandlerBean
>	java:global/rhq/rhq-server/StatusHandlerBean
>	java:app/rhq-server/StatusHandlerBean
>	java:module/StatusHandlerBean
>
>20:33:46,364 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PluginConfigurationMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PluginConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.PluginConfigurationMetadataManagerLocal
>	java:app/rhq-server/PluginConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.PluginConfigurationMetadataManagerLocal
>	java:module/PluginConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.PluginConfigurationMetadataManagerLocal
>	java:global/rhq/rhq-server/PluginConfigurationMetadataManagerBean
>	java:app/rhq-server/PluginConfigurationMetadataManagerBean
>	java:module/PluginConfigurationMetadataManagerBean
>
>20:33:46,364 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementProblemManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerRemote
>	java:app/rhq-server/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerRemote
>	java:module/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerRemote
>	java:jboss/exported/rhq/rhq-server/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerRemote
>	java:global/rhq/rhq-server/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerLocal
>	java:app/rhq-server/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerLocal
>	java:module/MeasurementProblemManagerBean!org.rhq.enterprise.server.measurement.MeasurementProblemManagerLocal
>
>20:33:46,364 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SuspectMetricHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SuspectMetricHandler!org.rhq.enterprise.server.rest.reporting.SuspectMetricLocal
>	java:app/rhq-server/SuspectMetricHandler!org.rhq.enterprise.server.rest.reporting.SuspectMetricLocal
>	java:module/SuspectMetricHandler!org.rhq.enterprise.server.rest.reporting.SuspectMetricLocal
>	java:global/rhq/rhq-server/SuspectMetricHandler
>	java:app/rhq-server/SuspectMetricHandler
>	java:module/SuspectMetricHandler
>
>20:33:46,365 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named EventMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/EventMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.EventMetdataManagerLocal
>	java:app/rhq-server/EventMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.EventMetdataManagerLocal
>	java:module/EventMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.EventMetdataManagerLocal
>	java:global/rhq/rhq-server/EventMetadataManagerBean
>	java:app/rhq-server/EventMetadataManagerBean
>	java:module/EventMetadataManagerBean
>
>20:33:46,365 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StorageNodeManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerRemote
>	java:app/rhq-server/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerRemote
>	java:module/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerRemote
>	java:jboss/exported/rhq/rhq-server/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerRemote
>	java:global/rhq/rhq-server/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerLocal
>	java:app/rhq-server/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerLocal
>	java:module/StorageNodeManagerBean!org.rhq.enterprise.server.cloud.StorageNodeManagerLocal
>
>20:33:46,366 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named JPADriftServerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/JPADriftServerBean!org.rhq.enterprise.server.drift.JPADriftServerLocal
>	java:app/rhq-server/JPADriftServerBean!org.rhq.enterprise.server.drift.JPADriftServerLocal
>	java:module/JPADriftServerBean!org.rhq.enterprise.server.drift.JPADriftServerLocal
>	java:global/rhq/rhq-server/JPADriftServerBean
>	java:app/rhq-server/JPADriftServerBean
>	java:module/JPADriftServerBean
>
>20:33:46,366 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DriftManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerLocal
>	java:app/rhq-server/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerLocal
>	java:module/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerLocal
>	java:global/rhq/rhq-server/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerRemote
>	java:app/rhq-server/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerRemote
>	java:module/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerRemote
>	java:jboss/exported/rhq/rhq-server/DriftManagerBean!org.rhq.enterprise.server.drift.DriftManagerRemote
>
>20:33:46,366 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DriftTemplateManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerLocal
>	java:app/rhq-server/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerLocal
>	java:module/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerLocal
>	java:global/rhq/rhq-server/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerRemote
>	java:app/rhq-server/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerRemote
>	java:module/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerRemote
>	java:jboss/exported/rhq/rhq-server/DriftTemplateManagerBean!org.rhq.enterprise.server.drift.DriftTemplateManagerRemote
>
>20:33:46,367 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertDefinitionHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertDefinitionHandlerBean!org.rhq.enterprise.server.rest.AlertDefinitionHandlerBean
>	java:app/rhq-server/AlertDefinitionHandlerBean!org.rhq.enterprise.server.rest.AlertDefinitionHandlerBean
>	java:module/AlertDefinitionHandlerBean!org.rhq.enterprise.server.rest.AlertDefinitionHandlerBean
>	java:global/rhq/rhq-server/AlertDefinitionHandlerBean
>	java:app/rhq-server/AlertDefinitionHandlerBean
>	java:module/AlertDefinitionHandlerBean
>
>20:33:46,367 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named TestBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/TestBean!org.rhq.enterprise.server.test.TestLocal
>	java:app/rhq-server/TestBean!org.rhq.enterprise.server.test.TestLocal
>	java:module/TestBean!org.rhq.enterprise.server.test.TestLocal
>	java:global/rhq/rhq-server/TestBean
>	java:app/rhq-server/TestBean
>	java:module/TestBean
>
>20:33:46,367 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named TopologyManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/TopologyManagerBean!org.rhq.enterprise.server.cloud.TopologyManagerLocal
>	java:app/rhq-server/TopologyManagerBean!org.rhq.enterprise.server.cloud.TopologyManagerLocal
>	java:module/TopologyManagerBean!org.rhq.enterprise.server.cloud.TopologyManagerLocal
>	java:global/rhq/rhq-server/TopologyManagerBean
>	java:app/rhq-server/TopologyManagerBean
>	java:module/TopologyManagerBean
>
>20:33:46,367 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named EmailManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/EmailManagerBean!org.rhq.enterprise.server.core.EmailManagerLocal
>	java:app/rhq-server/EmailManagerBean!org.rhq.enterprise.server.core.EmailManagerLocal
>	java:module/EmailManagerBean!org.rhq.enterprise.server.core.EmailManagerLocal
>	java:global/rhq/rhq-server/EmailManagerBean
>	java:app/rhq-server/EmailManagerBean
>	java:module/EmailManagerBean
>
>20:33:46,368 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceGroupManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerRemote
>	java:app/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerRemote
>	java:module/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerRemote
>	java:jboss/exported/rhq/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerRemote
>	java:global/rhq/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerLocal
>	java:app/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerLocal
>	java:module/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerLocal
>
>20:33:46,368 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named BundleManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerRemote
>	java:app/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerRemote
>	java:module/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerRemote
>	java:jboss/exported/rhq/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerRemote
>	java:global/rhq/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerLocal
>	java:app/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerLocal
>	java:module/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerLocal
>
>20:33:46,368 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceMetadataManagerLocal
>	java:app/rhq-server/ResourceMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceMetadataManagerLocal
>	java:module/ResourceMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceMetadataManagerLocal
>	java:global/rhq/rhq-server/ResourceMetadataManagerBean
>	java:app/rhq-server/ResourceMetadataManagerBean
>	java:module/ResourceMetadataManagerBean
>
>20:33:46,369 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertHandlerBean!org.rhq.enterprise.server.rest.AlertHandlerBean
>	java:app/rhq-server/AlertHandlerBean!org.rhq.enterprise.server.rest.AlertHandlerBean
>	java:module/AlertHandlerBean!org.rhq.enterprise.server.rest.AlertHandlerBean
>	java:global/rhq/rhq-server/AlertHandlerBean
>	java:app/rhq-server/AlertHandlerBean
>	java:module/AlertHandlerBean
>
>20:33:46,369 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CustomJaasDeploymentService in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CustomJaasDeploymentService!org.rhq.enterprise.server.core.CustomJaasDeploymentService
>	java:app/rhq-server/CustomJaasDeploymentService!org.rhq.enterprise.server.core.CustomJaasDeploymentService
>	java:module/CustomJaasDeploymentService!org.rhq.enterprise.server.core.CustomJaasDeploymentService
>	java:global/rhq/rhq-server/CustomJaasDeploymentService
>	java:app/rhq-server/CustomJaasDeploymentService
>	java:module/CustomJaasDeploymentService
>
>20:33:46,369 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named TagManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerLocal
>	java:app/rhq-server/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerLocal
>	java:module/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerLocal
>	java:global/rhq/rhq-server/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerRemote
>	java:app/rhq-server/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerRemote
>	java:module/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerRemote
>	java:jboss/exported/rhq/rhq-server/TagManagerBean!org.rhq.enterprise.server.tagging.TagManagerRemote
>
>20:33:46,370 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AffinityGroupManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AffinityGroupManagerBean!org.rhq.enterprise.server.cloud.AffinityGroupManagerLocal
>	java:app/rhq-server/AffinityGroupManagerBean!org.rhq.enterprise.server.cloud.AffinityGroupManagerLocal
>	java:module/AffinityGroupManagerBean!org.rhq.enterprise.server.cloud.AffinityGroupManagerLocal
>	java:global/rhq/rhq-server/AffinityGroupManagerBean
>	java:app/rhq-server/AffinityGroupManagerBean
>	java:module/AffinityGroupManagerBean
>
>20:33:46,370 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementViewManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementViewManagerBean!org.rhq.enterprise.server.measurement.MeasurementViewManagerLocal
>	java:app/rhq-server/MeasurementViewManagerBean!org.rhq.enterprise.server.measurement.MeasurementViewManagerLocal
>	java:module/MeasurementViewManagerBean!org.rhq.enterprise.server.measurement.MeasurementViewManagerLocal
>	java:global/rhq/rhq-server/MeasurementViewManagerBean
>	java:app/rhq-server/MeasurementViewManagerBean
>	java:module/MeasurementViewManagerBean
>
>20:33:46,370 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementCompressionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementCompressionManagerBean!org.rhq.enterprise.server.measurement.MeasurementCompressionManagerLocal
>	java:app/rhq-server/MeasurementCompressionManagerBean!org.rhq.enterprise.server.measurement.MeasurementCompressionManagerLocal
>	java:module/MeasurementCompressionManagerBean!org.rhq.enterprise.server.measurement.MeasurementCompressionManagerLocal
>	java:global/rhq/rhq-server/MeasurementCompressionManagerBean
>	java:app/rhq-server/MeasurementCompressionManagerBean
>	java:module/MeasurementCompressionManagerBean
>
>20:33:46,371 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SavedSearchManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SavedSearchManagerBean!org.rhq.enterprise.server.search.SavedSearchManagerLocal
>	java:app/rhq-server/SavedSearchManagerBean!org.rhq.enterprise.server.search.SavedSearchManagerLocal
>	java:module/SavedSearchManagerBean!org.rhq.enterprise.server.search.SavedSearchManagerLocal
>	java:global/rhq/rhq-server/SavedSearchManagerBean
>	java:app/rhq-server/SavedSearchManagerBean
>	java:module/SavedSearchManagerBean
>
>20:33:46,371 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named EntityManagerFacade in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/EntityManagerFacade!org.rhq.enterprise.server.common.EntityManagerFacadeLocal
>	java:app/rhq-server/EntityManagerFacade!org.rhq.enterprise.server.common.EntityManagerFacadeLocal
>	java:module/EntityManagerFacade!org.rhq.enterprise.server.common.EntityManagerFacadeLocal
>	java:global/rhq/rhq-server/EntityManagerFacade
>	java:app/rhq-server/EntityManagerFacade
>	java:module/EntityManagerFacade
>
>20:33:46,371 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PlatformUtilizationHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PlatformUtilizationHandler!org.rhq.enterprise.server.rest.reporting.PlatformUtilizationLocal
>	java:app/rhq-server/PlatformUtilizationHandler!org.rhq.enterprise.server.rest.reporting.PlatformUtilizationLocal
>	java:module/PlatformUtilizationHandler!org.rhq.enterprise.server.rest.reporting.PlatformUtilizationLocal
>	java:global/rhq/rhq-server/PlatformUtilizationHandler
>	java:app/rhq-server/PlatformUtilizationHandler
>	java:module/PlatformUtilizationHandler
>
>20:33:46,372 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RecentOperationsHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RecentOperationsHandler!org.rhq.enterprise.server.rest.reporting.RecentOperationsLocal
>	java:app/rhq-server/RecentOperationsHandler!org.rhq.enterprise.server.rest.reporting.RecentOperationsLocal
>	java:module/RecentOperationsHandler!org.rhq.enterprise.server.rest.reporting.RecentOperationsLocal
>	java:global/rhq/rhq-server/RecentOperationsHandler
>	java:app/rhq-server/RecentOperationsHandler
>	java:module/RecentOperationsHandler
>
>20:33:46,372 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ServerCommunicationsService in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ServerCommunicationsService!org.rhq.enterprise.server.core.comm.ServerCommunicationsService
>	java:app/rhq-server/ServerCommunicationsService!org.rhq.enterprise.server.core.comm.ServerCommunicationsService
>	java:module/ServerCommunicationsService!org.rhq.enterprise.server.core.comm.ServerCommunicationsService
>	java:global/rhq/rhq-server/ServerCommunicationsService
>	java:app/rhq-server/ServerCommunicationsService
>	java:module/ServerCommunicationsService
>
>20:33:46,372 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named InventorySummaryHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/InventorySummaryHandler!org.rhq.enterprise.server.rest.reporting.InventorySummaryLocal
>	java:app/rhq-server/InventorySummaryHandler!org.rhq.enterprise.server.rest.reporting.InventorySummaryLocal
>	java:module/InventorySummaryHandler!org.rhq.enterprise.server.rest.reporting.InventorySummaryLocal
>	java:global/rhq/rhq-server/InventorySummaryHandler
>	java:app/rhq-server/InventorySummaryHandler
>	java:module/InventorySummaryHandler
>
>20:33:46,373 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DistributionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DistributionManagerBean!org.rhq.enterprise.server.content.DistributionManagerLocal
>	java:app/rhq-server/DistributionManagerBean!org.rhq.enterprise.server.content.DistributionManagerLocal
>	java:module/DistributionManagerBean!org.rhq.enterprise.server.content.DistributionManagerLocal
>	java:global/rhq/rhq-server/DistributionManagerBean
>	java:app/rhq-server/DistributionManagerBean
>	java:module/DistributionManagerBean
>
>20:33:46,373 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ConfigurationSubsystemManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ConfigurationSubsystemManagerBean!org.rhq.enterprise.server.subsystem.ConfigurationSubsystemManagerLocal
>	java:app/rhq-server/ConfigurationSubsystemManagerBean!org.rhq.enterprise.server.subsystem.ConfigurationSubsystemManagerLocal
>	java:module/ConfigurationSubsystemManagerBean!org.rhq.enterprise.server.subsystem.ConfigurationSubsystemManagerLocal
>	java:global/rhq/rhq-server/ConfigurationSubsystemManagerBean
>	java:app/rhq-server/ConfigurationSubsystemManagerBean
>	java:module/ConfigurationSubsystemManagerBean
>
>20:33:46,373 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named GroupAlertDefinitionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/GroupAlertDefinitionManagerBean!org.rhq.enterprise.server.alert.GroupAlertDefinitionManagerLocal
>	java:app/rhq-server/GroupAlertDefinitionManagerBean!org.rhq.enterprise.server.alert.GroupAlertDefinitionManagerLocal
>	java:module/GroupAlertDefinitionManagerBean!org.rhq.enterprise.server.alert.GroupAlertDefinitionManagerLocal
>	java:global/rhq/rhq-server/GroupAlertDefinitionManagerBean
>	java:app/rhq-server/GroupAlertDefinitionManagerBean
>	java:module/GroupAlertDefinitionManagerBean
>
>20:33:46,374 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DiscoveryBossBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossLocal
>	java:app/rhq-server/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossLocal
>	java:module/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossLocal
>	java:global/rhq/rhq-server/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossRemote
>	java:app/rhq-server/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossRemote
>	java:module/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossRemote
>	java:jboss/exported/rhq/rhq-server/DiscoveryBossBean!org.rhq.enterprise.server.discovery.DiscoveryBossRemote
>
>20:33:46,374 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertConditionCacheMonitor in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertConditionCacheMonitor!org.rhq.enterprise.server.alert.engine.mbean.AlertConditionCacheMonitor
>	java:app/rhq-server/AlertConditionCacheMonitor!org.rhq.enterprise.server.alert.engine.mbean.AlertConditionCacheMonitor
>	java:module/AlertConditionCacheMonitor!org.rhq.enterprise.server.alert.engine.mbean.AlertConditionCacheMonitor
>	java:global/rhq/rhq-server/AlertConditionCacheMonitor
>	java:app/rhq-server/AlertConditionCacheMonitor
>	java:module/AlertConditionCacheMonitor
>
>20:33:46,374 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceTypeManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerLocal
>	java:app/rhq-server/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerLocal
>	java:module/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerLocal
>	java:global/rhq/rhq-server/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerRemote
>	java:app/rhq-server/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerRemote
>	java:module/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerRemote
>	java:jboss/exported/rhq/rhq-server/ResourceTypeManagerBean!org.rhq.enterprise.server.resource.ResourceTypeManagerRemote
>
>20:33:46,375 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RepoManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerRemote
>	java:app/rhq-server/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerRemote
>	java:module/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerRemote
>	java:jboss/exported/rhq/rhq-server/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerRemote
>	java:global/rhq/rhq-server/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerLocal
>	java:app/rhq-server/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerLocal
>	java:module/RepoManagerBean!org.rhq.enterprise.server.content.RepoManagerLocal
>
>20:33:46,375 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DriftComplianceHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DriftComplianceHandler!org.rhq.enterprise.server.rest.reporting.DriftComplianceLocal
>	java:app/rhq-server/DriftComplianceHandler!org.rhq.enterprise.server.rest.reporting.DriftComplianceLocal
>	java:module/DriftComplianceHandler!org.rhq.enterprise.server.rest.reporting.DriftComplianceLocal
>	java:global/rhq/rhq-server/DriftComplianceHandler
>	java:app/rhq-server/DriftComplianceHandler
>	java:module/DriftComplianceHandler
>
>20:33:46,375 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AgentManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AgentManagerBean!org.rhq.enterprise.server.core.AgentManagerLocal
>	java:app/rhq-server/AgentManagerBean!org.rhq.enterprise.server.core.AgentManagerLocal
>	java:module/AgentManagerBean!org.rhq.enterprise.server.core.AgentManagerLocal
>	java:global/rhq/rhq-server/AgentManagerBean
>	java:app/rhq-server/AgentManagerBean
>	java:module/AgentManagerBean
>
>20:33:46,375 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertDefinitionHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertDefinitionHandler!org.rhq.enterprise.server.rest.reporting.AlertDefinitionLocal
>	java:app/rhq-server/AlertDefinitionHandler!org.rhq.enterprise.server.rest.reporting.AlertDefinitionLocal
>	java:module/AlertDefinitionHandler!org.rhq.enterprise.server.rest.reporting.AlertDefinitionLocal
>	java:global/rhq/rhq-server/AlertDefinitionHandler
>	java:app/rhq-server/AlertDefinitionHandler
>	java:module/AlertDefinitionHandler
>
>20:33:46,376 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentHandlerBean!org.rhq.enterprise.server.rest.ContentHandlerBean
>	java:app/rhq-server/ContentHandlerBean!org.rhq.enterprise.server.rest.ContentHandlerBean
>	java:module/ContentHandlerBean!org.rhq.enterprise.server.rest.ContentHandlerBean
>	java:global/rhq/rhq-server/ContentHandlerBean
>	java:app/rhq-server/ContentHandlerBean
>	java:module/ContentHandlerBean
>
>20:33:46,376 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named EventManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/EventManagerBean!org.rhq.enterprise.server.event.EventManagerLocal
>	java:app/rhq-server/EventManagerBean!org.rhq.enterprise.server.event.EventManagerLocal
>	java:module/EventManagerBean!org.rhq.enterprise.server.event.EventManagerLocal
>	java:global/rhq/rhq-server/EventManagerBean!org.rhq.enterprise.server.event.EventManagerRemote
>	java:app/rhq-server/EventManagerBean!org.rhq.enterprise.server.event.EventManagerRemote
>	java:module/EventManagerBean!org.rhq.enterprise.server.event.EventManagerRemote
>	java:jboss/exported/rhq/rhq-server/EventManagerBean!org.rhq.enterprise.server.event.EventManagerRemote
>
>20:33:46,376 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ServerPluginService in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ServerPluginService!org.rhq.enterprise.server.plugin.pc.ServerPluginService
>	java:app/rhq-server/ServerPluginService!org.rhq.enterprise.server.plugin.pc.ServerPluginService
>	java:module/ServerPluginService!org.rhq.enterprise.server.plugin.pc.ServerPluginService
>	java:global/rhq/rhq-server/ServerPluginService
>	java:app/rhq-server/ServerPluginService
>	java:module/ServerPluginService
>
>20:33:46,377 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named GroupDefinitionExpressionBuilderManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/GroupDefinitionExpressionBuilderManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionExpressionBuilderManagerLocal
>	java:app/rhq-server/GroupDefinitionExpressionBuilderManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionExpressionBuilderManagerLocal
>	java:module/GroupDefinitionExpressionBuilderManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionExpressionBuilderManagerLocal
>	java:global/rhq/rhq-server/GroupDefinitionExpressionBuilderManagerBean
>	java:app/rhq-server/GroupDefinitionExpressionBuilderManagerBean
>	java:module/GroupDefinitionExpressionBuilderManagerBean
>
>20:33:46,377 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StorageClusterSettingsManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StorageClusterSettingsManagerBean!org.rhq.enterprise.server.storage.StorageClusterSettingsManagerLocal
>	java:app/rhq-server/StorageClusterSettingsManagerBean!org.rhq.enterprise.server.storage.StorageClusterSettingsManagerLocal
>	java:module/StorageClusterSettingsManagerBean!org.rhq.enterprise.server.storage.StorageClusterSettingsManagerLocal
>	java:global/rhq/rhq-server/StorageClusterSettingsManagerBean
>	java:app/rhq-server/StorageClusterSettingsManagerBean
>	java:module/StorageClusterSettingsManagerBean
>
>20:33:46,377 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RootHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RootHandlerBean!org.rhq.enterprise.server.rest.RootHandlerBean
>	java:app/rhq-server/RootHandlerBean!org.rhq.enterprise.server.rest.RootHandlerBean
>	java:module/RootHandlerBean!org.rhq.enterprise.server.rest.RootHandlerBean
>	java:global/rhq/rhq-server/RootHandlerBean
>	java:app/rhq-server/RootHandlerBean
>	java:module/RootHandlerBean
>
>20:33:46,378 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named GroupHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/GroupHandlerBean!org.rhq.enterprise.server.rest.GroupHandlerBean
>	java:app/rhq-server/GroupHandlerBean!org.rhq.enterprise.server.rest.GroupHandlerBean
>	java:module/GroupHandlerBean!org.rhq.enterprise.server.rest.GroupHandlerBean
>	java:global/rhq/rhq-server/GroupHandlerBean
>	java:app/rhq-server/GroupHandlerBean
>	java:module/GroupHandlerBean
>
>20:33:46,378 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertConditionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertConditionManagerBean!org.rhq.enterprise.server.alert.AlertConditionManagerLocal
>	java:app/rhq-server/AlertConditionManagerBean!org.rhq.enterprise.server.alert.AlertConditionManagerLocal
>	java:module/AlertConditionManagerBean!org.rhq.enterprise.server.alert.AlertConditionManagerLocal
>	java:global/rhq/rhq-server/AlertConditionManagerBean
>	java:app/rhq-server/AlertConditionManagerBean
>	java:module/AlertConditionManagerBean
>
>20:33:46,378 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SupportManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerRemote
>	java:app/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerRemote
>	java:module/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerRemote
>	java:jboss/exported/rhq/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerRemote
>	java:global/rhq/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerLocal
>	java:app/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerLocal
>	java:module/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerLocal
>
>20:33:46,379 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ShutdownListener in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ShutdownListener!org.rhq.enterprise.server.core.ShutdownListener
>	java:app/rhq-server/ShutdownListener!org.rhq.enterprise.server.core.ShutdownListener
>	java:module/ShutdownListener!org.rhq.enterprise.server.core.ShutdownListener
>	java:global/rhq/rhq-server/ShutdownListener
>	java:app/rhq-server/ShutdownListener
>	java:module/ShutdownListener
>
>20:33:46,379 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementDataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerRemote
>	java:app/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerRemote
>	java:module/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerRemote
>	java:jboss/exported/rhq/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerRemote
>	java:global/rhq/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerLocal
>	java:app/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerLocal
>	java:module/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerLocal
>
>20:33:46,379 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RemoteClientManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RemoteClientManagerBean!org.rhq.enterprise.server.core.RemoteClientManagerLocal
>	java:app/rhq-server/RemoteClientManagerBean!org.rhq.enterprise.server.core.RemoteClientManagerLocal
>	java:module/RemoteClientManagerBean!org.rhq.enterprise.server.core.RemoteClientManagerLocal
>	java:global/rhq/rhq-server/RemoteClientManagerBean
>	java:app/rhq-server/RemoteClientManagerBean
>	java:module/RemoteClientManagerBean
>
>20:33:46,380 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SubjectManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerLocal
>	java:app/rhq-server/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerLocal
>	java:module/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerLocal
>	java:global/rhq/rhq-server/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerRemote
>	java:app/rhq-server/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerRemote
>	java:module/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerRemote
>	java:jboss/exported/rhq/rhq-server/SubjectManagerBean!org.rhq.enterprise.server.auth.SubjectManagerRemote
>
>20:33:46,380 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RoleManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerLocal
>	java:app/rhq-server/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerLocal
>	java:module/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerLocal
>	java:global/rhq/rhq-server/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerRemote
>	java:app/rhq-server/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerRemote
>	java:module/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerRemote
>	java:jboss/exported/rhq/rhq-server/RoleManagerBean!org.rhq.enterprise.server.authz.RoleManagerRemote
>
>20:33:46,383 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AuthorizationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AuthorizationManagerBean!org.rhq.enterprise.server.authz.AuthorizationManagerLocal
>	java:app/rhq-server/AuthorizationManagerBean!org.rhq.enterprise.server.authz.AuthorizationManagerLocal
>	java:module/AuthorizationManagerBean!org.rhq.enterprise.server.authz.AuthorizationManagerLocal
>	java:global/rhq/rhq-server/AuthorizationManagerBean
>	java:app/rhq-server/AuthorizationManagerBean
>	java:module/AuthorizationManagerBean
>
>20:33:46,383 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementMonitor in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementMonitor!org.rhq.enterprise.server.measurement.instrumentation.MeasurementMonitor
>	java:app/rhq-server/MeasurementMonitor!org.rhq.enterprise.server.measurement.instrumentation.MeasurementMonitor
>	java:module/MeasurementMonitor!org.rhq.enterprise.server.measurement.instrumentation.MeasurementMonitor
>	java:global/rhq/rhq-server/MeasurementMonitor
>	java:app/rhq-server/MeasurementMonitor
>	java:module/MeasurementMonitor
>
>20:33:46,384 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AdvisoryManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AdvisoryManagerBean!org.rhq.enterprise.server.content.AdvisoryManagerLocal
>	java:app/rhq-server/AdvisoryManagerBean!org.rhq.enterprise.server.content.AdvisoryManagerLocal
>	java:module/AdvisoryManagerBean!org.rhq.enterprise.server.content.AdvisoryManagerLocal
>	java:global/rhq/rhq-server/AdvisoryManagerBean
>	java:app/rhq-server/AdvisoryManagerBean
>	java:module/AdvisoryManagerBean
>
>20:33:46,384 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentUIManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentUIManagerBean!org.rhq.enterprise.server.content.ContentUIManagerLocal
>	java:app/rhq-server/ContentUIManagerBean!org.rhq.enterprise.server.content.ContentUIManagerLocal
>	java:module/ContentUIManagerBean!org.rhq.enterprise.server.content.ContentUIManagerLocal
>	java:global/rhq/rhq-server/ContentUIManagerBean
>	java:app/rhq-server/ContentUIManagerBean
>	java:module/ContentUIManagerBean
>
>20:33:46,384 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StorageClientManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StorageClientManagerBean!org.rhq.enterprise.server.storage.StorageClientManagerBean
>	java:app/rhq-server/StorageClientManagerBean!org.rhq.enterprise.server.storage.StorageClientManagerBean
>	java:module/StorageClientManagerBean!org.rhq.enterprise.server.storage.StorageClientManagerBean
>	java:global/rhq/rhq-server/StorageClientManagerBean
>	java:app/rhq-server/StorageClientManagerBean
>	java:module/StorageClientManagerBean
>
>20:33:46,385 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RecentAlertHandler in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RecentAlertHandler!org.rhq.enterprise.server.rest.reporting.RecentAlertLocal
>	java:app/rhq-server/RecentAlertHandler!org.rhq.enterprise.server.rest.reporting.RecentAlertLocal
>	java:module/RecentAlertHandler!org.rhq.enterprise.server.rest.reporting.RecentAlertLocal
>	java:global/rhq/rhq-server/RecentAlertHandler
>	java:app/rhq-server/RecentAlertHandler
>	java:module/RecentAlertHandler
>
>20:33:46,385 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SystemInfoManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SystemInfoManagerBean!org.rhq.enterprise.server.system.SystemInfoManagerLocal
>	java:app/rhq-server/SystemInfoManagerBean!org.rhq.enterprise.server.system.SystemInfoManagerLocal
>	java:module/SystemInfoManagerBean!org.rhq.enterprise.server.system.SystemInfoManagerLocal
>	java:global/rhq/rhq-server/SystemInfoManagerBean
>	java:app/rhq-server/SystemInfoManagerBean
>	java:module/SystemInfoManagerBean
>
>20:33:46,385 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named StorageNodeOperationsHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/StorageNodeOperationsHandlerBean!org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerLocal
>	java:app/rhq-server/StorageNodeOperationsHandlerBean!org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerLocal
>	java:module/StorageNodeOperationsHandlerBean!org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerLocal
>	java:global/rhq/rhq-server/StorageNodeOperationsHandlerBean
>	java:app/rhq-server/StorageNodeOperationsHandlerBean
>	java:module/StorageNodeOperationsHandlerBean
>
>20:33:46,386 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertDampeningManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertDampeningManagerBean!org.rhq.enterprise.server.alert.AlertDampeningManagerLocal
>	java:app/rhq-server/AlertDampeningManagerBean!org.rhq.enterprise.server.alert.AlertDampeningManagerLocal
>	java:module/AlertDampeningManagerBean!org.rhq.enterprise.server.alert.AlertDampeningManagerLocal
>	java:global/rhq/rhq-server/AlertDampeningManagerBean
>	java:app/rhq-server/AlertDampeningManagerBean
>	java:module/AlertDampeningManagerBean
>
>20:33:46,386 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ConfigurationMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ConfigurationMetadataManagerBean!org.rhq.enterprise.server.configuration.metadata.ConfigurationMetadataManagerLocal
>	java:app/rhq-server/ConfigurationMetadataManagerBean!org.rhq.enterprise.server.configuration.metadata.ConfigurationMetadataManagerLocal
>	java:module/ConfigurationMetadataManagerBean!org.rhq.enterprise.server.configuration.metadata.ConfigurationMetadataManagerLocal
>	java:global/rhq/rhq-server/ConfigurationMetadataManagerBean
>	java:app/rhq-server/ConfigurationMetadataManagerBean
>	java:module/ConfigurationMetadataManagerBean
>
>20:33:46,386 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ContentManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerLocal
>	java:app/rhq-server/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerLocal
>	java:module/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerLocal
>	java:global/rhq/rhq-server/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerRemote
>	java:app/rhq-server/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerRemote
>	java:module/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerRemote
>	java:jboss/exported/rhq/rhq-server/ContentManagerBean!org.rhq.enterprise.server.content.ContentManagerRemote
>
>20:33:46,387 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named DataAccessManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerLocal
>	java:app/rhq-server/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerLocal
>	java:module/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerLocal
>	java:global/rhq/rhq-server/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerRemote
>	java:app/rhq-server/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerRemote
>	java:module/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerRemote
>	java:jboss/exported/rhq/rhq-server/DataAccessManagerBean!org.rhq.enterprise.server.report.DataAccessManagerRemote
>
>20:33:46,387 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SchedulerService in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SchedulerService!org.rhq.enterprise.server.scheduler.SchedulerService
>	java:app/rhq-server/SchedulerService!org.rhq.enterprise.server.scheduler.SchedulerService
>	java:module/SchedulerService!org.rhq.enterprise.server.scheduler.SchedulerService
>	java:global/rhq/rhq-server/SchedulerService
>	java:app/rhq-server/SchedulerService
>	java:module/SchedulerService
>
>20:33:46,387 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PluginManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PluginManagerBean!org.rhq.enterprise.server.resource.metadata.PluginManagerLocal
>	java:app/rhq-server/PluginManagerBean!org.rhq.enterprise.server.resource.metadata.PluginManagerLocal
>	java:module/PluginManagerBean!org.rhq.enterprise.server.resource.metadata.PluginManagerLocal
>	java:global/rhq/rhq-server/PluginManagerBean
>	java:app/rhq-server/PluginManagerBean
>	java:module/PluginManagerBean
>
>20:33:46,388 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named CachedConditionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/CachedConditionManagerBean!org.rhq.enterprise.server.alert.CachedConditionManagerLocal
>	java:app/rhq-server/CachedConditionManagerBean!org.rhq.enterprise.server.alert.CachedConditionManagerLocal
>	java:module/CachedConditionManagerBean!org.rhq.enterprise.server.alert.CachedConditionManagerLocal
>	java:global/rhq/rhq-server/CachedConditionManagerBean
>	java:app/rhq-server/CachedConditionManagerBean
>	java:module/CachedConditionManagerBean
>
>20:33:46,388 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named FailoverListManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/FailoverListManagerBean!org.rhq.enterprise.server.cloud.FailoverListManagerLocal
>	java:app/rhq-server/FailoverListManagerBean!org.rhq.enterprise.server.cloud.FailoverListManagerLocal
>	java:module/FailoverListManagerBean!org.rhq.enterprise.server.cloud.FailoverListManagerLocal
>	java:global/rhq/rhq-server/FailoverListManagerBean
>	java:app/rhq-server/FailoverListManagerBean
>	java:module/FailoverListManagerBean
>
>20:33:46,388 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named OperationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerRemote
>	java:app/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerRemote
>	java:module/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerRemote
>	java:jboss/exported/rhq/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerRemote
>	java:global/rhq/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerLocal
>	java:app/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerLocal
>	java:module/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerLocal
>
>20:33:46,389 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceConfigurationMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceConfigurationMetadataManagerLocal
>	java:app/rhq-server/ResourceConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceConfigurationMetadataManagerLocal
>	java:module/ResourceConfigurationMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.ResourceConfigurationMetadataManagerLocal
>	java:global/rhq/rhq-server/ResourceConfigurationMetadataManagerBean
>	java:app/rhq-server/ResourceConfigurationMetadataManagerBean
>	java:module/ResourceConfigurationMetadataManagerBean
>
>20:33:46,389 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named PlatformUtilizationManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/PlatformUtilizationManagerBean!org.rhq.enterprise.server.resource.PlatformUtilizationManagerLocal
>	java:app/rhq-server/PlatformUtilizationManagerBean!org.rhq.enterprise.server.resource.PlatformUtilizationManagerLocal
>	java:module/PlatformUtilizationManagerBean!org.rhq.enterprise.server.resource.PlatformUtilizationManagerLocal
>	java:global/rhq/rhq-server/PlatformUtilizationManagerBean
>	java:app/rhq-server/PlatformUtilizationManagerBean
>	java:module/PlatformUtilizationManagerBean
>
>20:33:46,389 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertConditionCacheManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertConditionCacheManagerBean!org.rhq.enterprise.server.alert.engine.AlertConditionCacheManagerLocal
>	java:app/rhq-server/AlertConditionCacheManagerBean!org.rhq.enterprise.server.alert.engine.AlertConditionCacheManagerLocal
>	java:module/AlertConditionCacheManagerBean!org.rhq.enterprise.server.alert.engine.AlertConditionCacheManagerLocal
>	java:global/rhq/rhq-server/AlertConditionCacheManagerBean
>	java:app/rhq-server/AlertConditionCacheManagerBean
>	java:module/AlertConditionCacheManagerBean
>
>20:33:46,390 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named ResourceFactoryManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerLocal
>	java:app/rhq-server/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerLocal
>	java:module/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerLocal
>	java:global/rhq/rhq-server/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerRemote
>	java:app/rhq-server/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerRemote
>	java:module/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerRemote
>	java:jboss/exported/rhq/rhq-server/ResourceFactoryManagerBean!org.rhq.enterprise.server.resource.ResourceFactoryManagerRemote
>
>20:33:46,390 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementOOBManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementOOBManagerBean!org.rhq.enterprise.server.measurement.MeasurementOOBManagerLocal
>	java:app/rhq-server/MeasurementOOBManagerBean!org.rhq.enterprise.server.measurement.MeasurementOOBManagerLocal
>	java:module/MeasurementOOBManagerBean!org.rhq.enterprise.server.measurement.MeasurementOOBManagerLocal
>	java:global/rhq/rhq-server/MeasurementOOBManagerBean
>	java:app/rhq-server/MeasurementOOBManagerBean
>	java:module/MeasurementOOBManagerBean
>
>20:33:46,394 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named AlertManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerRemote
>	java:app/rhq-server/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerRemote
>	java:module/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerRemote
>	java:jboss/exported/rhq/rhq-server/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerRemote
>	java:global/rhq/rhq-server/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerLocal
>	java:app/rhq-server/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerLocal
>	java:module/AlertManagerBean!org.rhq.enterprise.server.alert.AlertManagerLocal
>
>20:33:46,395 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named RemoteInstallManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerRemote
>	java:app/rhq-server/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerRemote
>	java:module/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerRemote
>	java:jboss/exported/rhq/rhq-server/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerRemote
>	java:global/rhq/rhq-server/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerLocal
>	java:app/rhq-server/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerLocal
>	java:module/RemoteInstallManagerBean!org.rhq.enterprise.server.install.remote.RemoteInstallManagerLocal
>
>20:33:46,395 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named GroupDefinitionManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerLocal
>	java:app/rhq-server/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerLocal
>	java:module/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerLocal
>	java:global/rhq/rhq-server/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerRemote
>	java:app/rhq-server/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerRemote
>	java:module/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerRemote
>	java:jboss/exported/rhq/rhq-server/GroupDefinitionManagerBean!org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerRemote
>
>20:33:46,395 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named EventHandlerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/EventHandlerBean!org.rhq.enterprise.server.rest.EventHandlerBean
>	java:app/rhq-server/EventHandlerBean!org.rhq.enterprise.server.rest.EventHandlerBean
>	java:module/EventHandlerBean!org.rhq.enterprise.server.rest.EventHandlerBean
>	java:global/rhq/rhq-server/EventHandlerBean
>	java:app/rhq-server/EventHandlerBean
>	java:module/EventHandlerBean
>
>20:33:46,396 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named MeasurementMetadataManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/MeasurementMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.MeasurementMetadataManagerLocal
>	java:app/rhq-server/MeasurementMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.MeasurementMetadataManagerLocal
>	java:module/MeasurementMetadataManagerBean!org.rhq.enterprise.server.resource.metadata.MeasurementMetadataManagerLocal
>	java:global/rhq/rhq-server/MeasurementMetadataManagerBean
>	java:app/rhq-server/MeasurementMetadataManagerBean
>	java:module/MeasurementMetadataManagerBean
>
>20:33:46,396 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-10) JNDI bindings for session bean named SystemManagerBean in deployment unit subdeployment "rhq-server.jar" of deployment "rhq.ear" are as follows:
>
>	java:global/rhq/rhq-server/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerRemote
>	java:app/rhq-server/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerRemote
>	java:module/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerRemote
>	java:jboss/exported/rhq/rhq-server/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerRemote
>	java:global/rhq/rhq-server/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerLocal
>	java:app/rhq-server/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerLocal
>	java:module/SystemManagerBean!org.rhq.enterprise.server.system.SystemManagerLocal
>
>20:33:46,702 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 63) JBAS011402: Starting Persistence Unit Service 'rhq.ear/rhq-core-domain-ejb3.jar#rhqpu'
>20:33:46,873 INFO  [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 63) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2}
>20:33:46,880 INFO  [org.hibernate.Version] (ServerService Thread Pool -- 63) HHH000412: Hibernate Core {4.2.0.SP1-redhat-1}
>20:33:46,882 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 63) HHH000206: hibernate.properties not found
>20:33:46,884 INFO  [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 63) HHH000021: Bytecode provider name : javassist
>20:33:46,908 INFO  [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 63) HHH000204: Processing PersistenceUnitInfo [
>	name: rhqpu
>	...]
>20:33:50,004 INFO  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 63) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
>20:33:51,256 INFO  [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 63) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
>20:33:51,272 INFO  [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (ServerService Thread Pool -- 63) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
>20:33:51,288 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 63) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
>20:33:51,378 INFO  [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 63) HV000001: Hibernate Validator 4.3.1.Final-redhat-1
>20:34:04,469 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'AlertConditionConsumerBean' with 'hornetq-ra' resource adapter
>20:34:04,470 INFO  [org.jboss.as.ejb3] (MSC service thread 1-10) JBAS014142: Started message driven bean 'DriftFileBean' with 'hornetq-ra' resource adapter
>20:34:04,472 INFO  [org.jboss.as.ejb3] (MSC service thread 1-14) JBAS014142: Started message driven bean 'DriftChangesetBean' with 'hornetq-ra' resource adapter
>20:34:04,974 INFO  [org.rhq.enterprise.server.core.CoreServer] (ServerService Thread Pool -- 79) Version=[4.9.0.JON320GA], Build Number=[734bd56], Build Date=[12.Dec.2013 11.40.26 EST]
>20:34:04,983 INFO  [org.rhq.enterprise.server.scheduler.SchedulerService] (ServerService Thread Pool -- 72) Scheduler has a default operation timeout of [600] seconds.
>20:34:05,567 INFO  [org.jboss.web] (ServerService Thread Pool -- 76) JBAS018210: Register web context: /portal
>20:34:05,630 INFO  [org.apache.catalina.core] (ServerService Thread Pool -- 76) JBWEB001093: The listener com.sun.faces.config.ConfigureListener is already configured for this context, the duplicate definition has been ignored
>20:34:05,692 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 76) Initializing Mojarra (1.2_15-b01-redhat-3) for context '/portal'
>20:34:06,897 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 76) JSF1051: Service entry 'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider.  Entry will be ignored.
>20:34:06,898 INFO  [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 76) JSF1048: PostConstruct/PreDestroy annotations present.  ManagedBeans methods marked with these annotations will have said annotations processed.
>20:34:07,577 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 76) Initialized response-time filter for webapp with context root 'portal'.
>20:34:07,591 INFO  [org.ajax4jsf.cache.CacheManager] (ServerService Thread Pool -- 76) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
>20:34:07,593 INFO  [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 76) Creating LRUMap cache instance using parameters: {RtEnabled=false, facelets.DEVELOPMENT=true, com.sun.faces.numberOfLogicalViews=2, facelets.LIBRARIES=/WEB-INF/tags/on.component.taglib.xml;/WEB-INF/tags/on.function.taglib.xml, javax.faces.CONFIG_FILES=/WEB-INF/jsf-components/configuration-components.xml,
>         /WEB-INF/jsf-components/error-components.xml,
>         /WEB-INF/jsf-components/inventory-components.xml,
>         /WEB-INF/jsf-components/layout-components.xml,
>         /WEB-INF/jsf-components/navigation-components.xml,
>         /WEB-INF/jsf-components/pagination-components.xml,
>         /WEB-INF/jsf-components/sorting-components.xml,
>         /WEB-INF/jsf-components/table-components.xml,
>         /WEB-INF/jsf-components/time-components.xml,
>         /WEB-INF/jsf-components/upload-components.xml,
>         /WEB-INF/jsf-components/metric-components.xml,
>
>         /WEB-INF/jsf-managed-beans/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans/content-beans.xml,
>         /WEB-INF/jsf-managed-beans/autodiscovery-beans.xml,
>         /WEB-INF/jsf-managed-beans/cluster-beans.xml,
>         /WEB-INF/jsf-managed-beans/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans/global-beans.xml,
>         /WEB-INF/jsf-managed-beans/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans/admin-beans.xml,
>         /WEB-INF/jsf-managed-beans/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans/operation-beans.xml,
>         /WEB-INF/jsf-managed-beans/test-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-auto-group/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans-auto-group/measurement-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-common/availability-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/event-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/navigation-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-definition/group-definition-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-resource-group/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/operation-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/measurement-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-subsystem/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/operation-beans.xml,
>
>         /WEB-INF/jsf-navigation/alert-navigation.xml,
>         /WEB-INF/jsf-navigation/cluster-navigation.xml,
>         /WEB-INF/jsf-navigation/content-navigation.xml,
>         /WEB-INF/jsf-navigation/events-navigation.xml,
>         /WEB-INF/jsf-navigation/autodiscovery-navigation.xml,
>         /WEB-INF/jsf-navigation/configuration-navigation.xml,
>         /WEB-INF/jsf-navigation/inventory-navigation.xml,
>         /WEB-INF/jsf-navigation/admin-navigation.xml,
>         /WEB-INF/jsf-navigation/operation-navigation.xml,
>         /WEB-INF/jsf-navigation/measurement-navigation.xml,
>         /WEB-INF/jsf-navigation/summary-navigation.xml,
>         /WEB-INF/jsf-navigation/test-navigation.xml,
>         
>         /WEB-INF/jsf-navigation/admin-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/alert-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/cluster-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/content-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/events-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/operation-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/measurement-plain-navigation.xml,
>
>         /WEB-INF/jsf-navigation-definition/group-definition-navigation.xml,
>
>         /WEB-INF/jsf-navigation-resource-group/alert-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/configuration-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/events-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/inventory-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/operation-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/measurement-navigation.xml,
>         
>         /WEB-INF/jsf-navigation-resource-group/alert-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/configuration-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/events-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/operation-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/measurement-plain-navigation.xml,
>         
>         /WEB-INF/jsf-navigation-auto-group/events-navigation.xml,
>         /WEB-INF/jsf-navigation-auto-group/measurement-navigation.xml,
>
>         /WEB-INF/jsf-navigation-subsystem/tab-container-navigation.xml,
>
>         /WEB-INF/jsf-converters/common-converters.xml,
>         /WEB-INF/jsf-converters/content-converters.xml,
>         /WEB-INF/jsf-converters/inventory-converters.xml, org.richfaces.SKIN=DEFAULT, com.sun.faces.validateXml=false, context-constants=org.rhq.enterprise.gui.legacy.Constants, resteasy.scanned.providers=org.rhq.enterprise.server.rest.CustomExceptionMapper, resteasy.scanned.jndi.resources=java:app/rhq-server/UserHandlerBean;org.rhq.enterprise.server.rest.UserHandlerBean;true,java:app/rhq-server/OperationsHandlerBean;org.rhq.enterprise.server.rest.OperationsHandlerBean;true,java:app/rhq-server/ReportsHandlerBean;org.rhq.enterprise.server.rest.ReportsHandlerBean;true,java:app/rhq-server/ConfigurationHistoryHandler;org.rhq.enterprise.server.rest.reporting.ConfigurationHistoryHandler;true,java:app/rhq-server/MetricHandlerBean;org.rhq.enterprise.server.rest.MetricHandlerBean;true,java:app/rhq-server/ResourceTypeHandlerBean;org.rhq.enterprise.server.rest.ResourceTypeHandlerBean;true,java:app/rhq-server/ResourceHandlerBean;org.rhq.enterprise.server.rest.ResourceHandlerBean;true,java:app/rhq-server/RecentDriftHandler;org.rhq.enterprise.server.rest.reporting.RecentDriftHandler;true,java:app/rhq-server/StatusHandlerBean;org.rhq.enterprise.server.rest.StatusHandlerBean;true,java:app/rhq-server/SuspectMetricHandler;org.rhq.enterprise.server.rest.reporting.SuspectMetricHandler;true,java:app/rhq-server/AlertDefinitionHandlerBean;org.rhq.enterprise.server.rest.AlertDefinitionHandlerBean;true,java:app/rhq-server/AlertHandlerBean;org.rhq.enterprise.server.rest.AlertHandlerBean;true,java:app/rhq-server/PlatformUtilizationHandler;org.rhq.enterprise.server.rest.reporting.PlatformUtilizationHandler;true,java:app/rhq-server/RecentOperationsHandler;org.rhq.enterprise.server.rest.reporting.RecentOperationsHandler;true,java:app/rhq-server/InventorySummaryHandler;org.rhq.enterprise.server.rest.reporting.InventorySummaryHandler;true,java:app/rhq-server/DriftComplianceHandler;org.rhq.enterprise.server.rest.reporting.DriftComplianceHandler;true,java:app/rhq-server/AlertDefinitionHandler;org.rhq.enterprise.server.rest.reporting.AlertDefinitionHandler;true,java:app/rhq-server/ContentHandlerBean;org.rhq.enterprise.server.rest.ContentHandlerBean;true,java:app/rhq-server/RootHandlerBean;org.rhq.enterprise.server.rest.RootHandlerBean;true,java:app/rhq-server/GroupHandlerBean;org.rhq.enterprise.server.rest.GroupHandlerBean;true,java:app/rhq-server/RecentAlertHandler;org.rhq.enterprise.server.rest.reporting.RecentAlertHandler;true,java:app/rhq-server/EventHandlerBean;org.rhq.enterprise.server.rest.EventHandlerBean;true, com.sun.faces.verifyObjects=false, javax.servlet.jsp.jstl.fmt.localizationContext=ApplicationResources, javax.faces.STATE_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, resteasy.unwrapped.exceptions=javax.ejb.EJBException, com.sun.faces.numberOfViewsInSession=2}
>20:34:07,594 INFO  [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 76) Creating LRUMap cache instance of default capacity
>20:34:07,610 INFO  [org.ajax4jsf.cache.CacheManager] (ServerService Thread Pool -- 76) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory
>20:34:07,610 INFO  [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 76) Creating LRUMap cache instance using parameters: {RtEnabled=false, facelets.DEVELOPMENT=true, com.sun.faces.numberOfLogicalViews=2, facelets.LIBRARIES=/WEB-INF/tags/on.component.taglib.xml;/WEB-INF/tags/on.function.taglib.xml, javax.faces.CONFIG_FILES=/WEB-INF/jsf-components/configuration-components.xml,
>         /WEB-INF/jsf-components/error-components.xml,
>         /WEB-INF/jsf-components/inventory-components.xml,
>         /WEB-INF/jsf-components/layout-components.xml,
>         /WEB-INF/jsf-components/navigation-components.xml,
>         /WEB-INF/jsf-components/pagination-components.xml,
>         /WEB-INF/jsf-components/sorting-components.xml,
>         /WEB-INF/jsf-components/table-components.xml,
>         /WEB-INF/jsf-components/time-components.xml,
>         /WEB-INF/jsf-components/upload-components.xml,
>         /WEB-INF/jsf-components/metric-components.xml,
>
>         /WEB-INF/jsf-managed-beans/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans/content-beans.xml,
>         /WEB-INF/jsf-managed-beans/autodiscovery-beans.xml,
>         /WEB-INF/jsf-managed-beans/cluster-beans.xml,
>         /WEB-INF/jsf-managed-beans/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans/global-beans.xml,
>         /WEB-INF/jsf-managed-beans/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans/admin-beans.xml,
>         /WEB-INF/jsf-managed-beans/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans/operation-beans.xml,
>         /WEB-INF/jsf-managed-beans/test-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-auto-group/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans-auto-group/measurement-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-common/availability-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/event-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans-common/navigation-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-definition/group-definition-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-resource-group/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/inventory-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/operation-beans.xml,
>         /WEB-INF/jsf-managed-beans-resource-group/measurement-beans.xml,
>
>         /WEB-INF/jsf-managed-beans-subsystem/alert-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/configuration-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/measurement-beans.xml,
>         /WEB-INF/jsf-managed-beans-subsystem/operation-beans.xml,
>
>         /WEB-INF/jsf-navigation/alert-navigation.xml,
>         /WEB-INF/jsf-navigation/cluster-navigation.xml,
>         /WEB-INF/jsf-navigation/content-navigation.xml,
>         /WEB-INF/jsf-navigation/events-navigation.xml,
>         /WEB-INF/jsf-navigation/autodiscovery-navigation.xml,
>         /WEB-INF/jsf-navigation/configuration-navigation.xml,
>         /WEB-INF/jsf-navigation/inventory-navigation.xml,
>         /WEB-INF/jsf-navigation/admin-navigation.xml,
>         /WEB-INF/jsf-navigation/operation-navigation.xml,
>         /WEB-INF/jsf-navigation/measurement-navigation.xml,
>         /WEB-INF/jsf-navigation/summary-navigation.xml,
>         /WEB-INF/jsf-navigation/test-navigation.xml,
>         
>         /WEB-INF/jsf-navigation/admin-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/alert-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/cluster-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/content-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/events-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/operation-plain-navigation.xml,
>         /WEB-INF/jsf-navigation/measurement-plain-navigation.xml,
>
>         /WEB-INF/jsf-navigation-definition/group-definition-navigation.xml,
>
>         /WEB-INF/jsf-navigation-resource-group/alert-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/configuration-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/events-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/inventory-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/operation-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/measurement-navigation.xml,
>         
>         /WEB-INF/jsf-navigation-resource-group/alert-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/configuration-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/events-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/operation-plain-navigation.xml,
>         /WEB-INF/jsf-navigation-resource-group/measurement-plain-navigation.xml,
>         
>         /WEB-INF/jsf-navigation-auto-group/events-navigation.xml,
>         /WEB-INF/jsf-navigation-auto-group/measurement-navigation.xml,
>
>         /WEB-INF/jsf-navigation-subsystem/tab-container-navigation.xml,
>
>         /WEB-INF/jsf-converters/common-converters.xml,
>         /WEB-INF/jsf-converters/content-converters.xml,
>         /WEB-INF/jsf-converters/inventory-converters.xml, org.richfaces.SKIN=DEFAULT, com.sun.faces.validateXml=false, context-constants=org.rhq.enterprise.gui.legacy.Constants, resteasy.scanned.providers=org.rhq.enterprise.server.rest.CustomExceptionMapper, resteasy.scanned.jndi.resources=java:app/rhq-server/UserHandlerBean;org.rhq.enterprise.server.rest.UserHandlerBean;true,java:app/rhq-server/OperationsHandlerBean;org.rhq.enterprise.server.rest.OperationsHandlerBean;true,java:app/rhq-server/ReportsHandlerBean;org.rhq.enterprise.server.rest.ReportsHandlerBean;true,java:app/rhq-server/ConfigurationHistoryHandler;org.rhq.enterprise.server.rest.reporting.ConfigurationHistoryHandler;true,java:app/rhq-server/MetricHandlerBean;org.rhq.enterprise.server.rest.MetricHandlerBean;true,java:app/rhq-server/ResourceTypeHandlerBean;org.rhq.enterprise.server.rest.ResourceTypeHandlerBean;true,java:app/rhq-server/ResourceHandlerBean;org.rhq.enterprise.server.rest.ResourceHandlerBean;true,java:app/rhq-server/RecentDriftHandler;org.rhq.enterprise.server.rest.reporting.RecentDriftHandler;true,java:app/rhq-server/StatusHandlerBean;org.rhq.enterprise.server.rest.StatusHandlerBean;true,java:app/rhq-server/SuspectMetricHandler;org.rhq.enterprise.server.rest.reporting.SuspectMetricHandler;true,java:app/rhq-server/AlertDefinitionHandlerBean;org.rhq.enterprise.server.rest.AlertDefinitionHandlerBean;true,java:app/rhq-server/AlertHandlerBean;org.rhq.enterprise.server.rest.AlertHandlerBean;true,java:app/rhq-server/PlatformUtilizationHandler;org.rhq.enterprise.server.rest.reporting.PlatformUtilizationHandler;true,java:app/rhq-server/RecentOperationsHandler;org.rhq.enterprise.server.rest.reporting.RecentOperationsHandler;true,java:app/rhq-server/InventorySummaryHandler;org.rhq.enterprise.server.rest.reporting.InventorySummaryHandler;true,java:app/rhq-server/DriftComplianceHandler;org.rhq.enterprise.server.rest.reporting.DriftComplianceHandler;true,java:app/rhq-server/AlertDefinitionHandler;org.rhq.enterprise.server.rest.reporting.AlertDefinitionHandler;true,java:app/rhq-server/ContentHandlerBean;org.rhq.enterprise.server.rest.ContentHandlerBean;true,java:app/rhq-server/RootHandlerBean;org.rhq.enterprise.server.rest.RootHandlerBean;true,java:app/rhq-server/GroupHandlerBean;org.rhq.enterprise.server.rest.GroupHandlerBean;true,java:app/rhq-server/RecentAlertHandler;org.rhq.enterprise.server.rest.reporting.RecentAlertHandler;true,java:app/rhq-server/EventHandlerBean;org.rhq.enterprise.server.rest.EventHandlerBean;true, com.sun.faces.verifyObjects=false, javax.servlet.jsp.jstl.fmt.localizationContext=ApplicationResources, javax.faces.STATE_SAVING_METHOD=server, javax.faces.DEFAULT_SUFFIX=.xhtml, resteasy.unwrapped.exceptions=javax.ejb.EJBException, com.sun.faces.numberOfViewsInSession=2}
>20:34:07,611 INFO  [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 76) Creating LRUMap cache instance of default capacity
>20:34:08,157 INFO  [org.apache.struts.tiles.TilesPlugin] (ServerService Thread Pool -- 76) Tiles definition factory loaded for module ''.
>20:34:08,187 INFO  [org.apache.struts.validator.ValidatorPlugIn] (ServerService Thread Pool -- 76) Loading validation rules file from '/WEB-INF/validation/validator-rules.xml'
>20:34:08,188 INFO  [org.apache.struts.validator.ValidatorPlugIn] (ServerService Thread Pool -- 76) Loading validation rules file from '/WEB-INF/validation/validation.xml'
>20:34:08,403 INFO  [org.jboss.web] (ServerService Thread Pool -- 84) JBAS018210: Register web context: /client
>20:34:08,536 INFO  [org.jboss.web] (ServerService Thread Pool -- 76) JBAS018210: Register web context: /downloads
>20:34:08,558 INFO  [org.rhq.enterprise.gui.download.DownloadServlet] (ServerService Thread Pool -- 76) Starting the RHQ download servlet...
>20:34:08,583 INFO  [org.jboss.web] (ServerService Thread Pool -- 70) JBAS018210: Register web context: /agentupdate
>20:34:08,602 INFO  [org.rhq.enterprise.gui.agentupdate.AgentUpdateServlet] (ServerService Thread Pool -- 70) Starting the RHQ agent update servlet
>20:34:08,831 INFO  [org.jboss.web] (ServerService Thread Pool -- 70) JBAS018210: Register web context: /content
>20:34:08,864 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 70) Initializing Mojarra 2.1.19-jbossorg-1 20130304-0420 for context '/content'
>20:34:13,068 INFO  [org.jboss.web] (ServerService Thread Pool -- 76) JBAS018210: Register web context: /rest
>20:34:13,105 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 76) Initialized response-time filter for webapp with context root 'rest'.
>20:34:13,150 INFO  [org.jboss.web] (ServerService Thread Pool -- 76) JBAS018210: Register web context: /rest-examples
>20:34:13,214 INFO  [org.jboss.web] (ServerService Thread Pool -- 76) JBAS018210: Register web context: /jboss-remoting-servlet-invoker
>20:34:13,313 INFO  [org.jboss.web] (ServerService Thread Pool -- 84) JBAS018210: Register web context: /coregui
>20:34:13,368 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 84) Initialized response-time filter for webapp with context root 'coregui'.
>20:34:13,428 INFO  [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "rhq.ear" (runtime-name : "rhq.ear")
>20:34:20,554 INFO  [org.apache.coyote.http11] (MSC service thread 1-8) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.90.16:7080
>20:34:20,554 INFO  [org.apache.coyote.http11] (MSC service thread 1-8) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.90.16:7080
>20:34:20,580 INFO  [org.apache.coyote.http11] (MSC service thread 1-12) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.16.90.16:7443
>20:34:20,581 INFO  [org.apache.coyote.http11] (MSC service thread 1-12) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.16.90.16:7443
>20:34:20,743 INFO  [org.apache.catalina.core] (MSC service thread 1-16) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
>20:34:21,040 INFO  [org.jboss.web] (ServerService Thread Pool -- 79) JBAS018224: Unregister web context: /coregui
>20:34:21,069 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 79) -- Filter destroy: 0 requests processed (hashCode=1947853755).
>20:34:21,095 INFO  [org.jboss.jaxr] (MSC service thread 1-12) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory
>20:34:21,134 INFO  [org.rhq.enterprise.server.core.ShutdownListener] (ServerService Thread Pool -- 79) Shutdown listener has been told we are shutting down - starting to clean up now...
>20:34:21,194 INFO  [org.rhq.enterprise.server.core.ShutdownListener] (ServerService Thread Pool -- 79) No need for shutting down the scheduler, because it is not running.
>20:34:21,730 INFO  [org.rhq.enterprise.server.core.ShutdownListener] (ServerService Thread Pool -- 79) Shutdown listener completed its shutdown tasks. It is safe to shutdown now.
>20:34:21,767 INFO  [org.jboss.web] (ServerService Thread Pool -- 79) JBAS018224: Unregister web context: /jboss-remoting-servlet-invoker
>20:34:21,778 INFO  [org.jboss.web] (ServerService Thread Pool -- 79) JBAS018224: Unregister web context: /rest-examples
>20:34:21,788 INFO  [org.jboss.web] (ServerService Thread Pool -- 79) JBAS018224: Unregister web context: /rest
>20:34:21,789 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 79) -- Filter destroy: 0 requests processed (hashCode=689740529).
>20:34:21,798 INFO  [org.jboss.web] (ServerService Thread Pool -- 80) JBAS018224: Unregister web context: /content
>20:34:21,840 INFO  [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018224: Unregister web context: /agentupdate
>20:34:21,850 INFO  [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018224: Unregister web context: /downloads
>20:34:21,859 INFO  [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018224: Unregister web context: /client
>20:34:21,867 INFO  [org.jboss.web] (ServerService Thread Pool -- 71) JBAS018224: Unregister web context: /portal
>20:34:21,871 INFO  [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 71) -- Filter destroy: 0 requests processed (hashCode=240787614).
>20:34:22,374 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-13) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
>20:34:22,391 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-10) JBAS010409: Unbound data source [java:jboss/datasources/NoTxRHQDS]
>20:34:22,441 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 84) JBAS011605: Unbound messaging object to jndi name java:/queue/AlertConditionQueue
>20:34:22,484 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 70) JBAS011403: Stopping Persistence Unit Service 'rhq.ear/rhq-core-domain-ejb3.jar#rhqpu'
>20:34:22,492 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/RHQDS]
>20:34:22,501 INFO  [org.hornetq.ra] (MSC service thread 1-4) HQ151003: HornetQ resource adaptor stopped
>20:34:22,590 INFO  [org.hornetq.core.server] (MSC service thread 1-8) HQ221002: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [e5be279b-78cd-11e3-8423-6bf8f126e566] stopped
>20:34:22,591 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment null (runtime-name: rhq-rest-examples.war) in 1683ms
>20:34:22,596 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015877: Stopped deployment null (runtime-name: rhq-core-domain-ejb3.jar) in 1797ms
>20:34:22,597 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015877: Stopped deployment null (runtime-name: rhq-server.jar) in 1696ms
>20:34:22,597 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015877: Stopped deployment null (runtime-name: rhq-downloads.war) in 1763ms
>20:34:22,597 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment null (runtime-name: rhq-agentupdate.war) in 2123ms
>20:34:22,598 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment null (runtime-name: rhq-remoting.war) in 1702ms
>20:34:22,598 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015877: Stopped deployment null (runtime-name: rhq-client.war) in 1798ms
>20:34:22,613 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015877: Stopped deployment null (runtime-name: rhq-rest.war) in 1872ms
>20:34:22,725 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015877: Stopped deployment null (runtime-name: coregui.war) in 1984ms
>20:34:22,757 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: rhq-content_http.war) in 1870ms
>20:34:22,859 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: rhq-portal.war) in 2118ms
>20:34:23,497 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment rhq.ear (runtime-name: rhq.ear) in 2989ms
>20:34:23,514 INFO  [org.jboss.as] (MSC service thread 1-10) JBAS015950: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) stopped in 2602ms

Actions: View

Attachments on bug 1050751: 847457 | 847458 | 847459 | 847460 | 847704