Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 832714 Details for
Bug 1038202
recovery alert fired twice
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
s2_server.log
s2_server.log (text/x-log), 248.17 KB, created by
Armine Hovsepyan
on 2013-12-04 15:46:00 UTC
(
hide
)
Description:
s2_server.log
Filename:
MIME Type:
Creator:
Armine Hovsepyan
Created:
2013-12-04 15:46:00 UTC
Size:
248.17 KB
patch
obsolete
>04:41:34,911 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1 >04:41:35,222 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 >04:41:35,401 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting >04:41:38,366 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1 >04:41:38,395 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) >04:41:38,389 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1 >04:41:38,418 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1 >04:41:38,608 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem. >04:41:38,617 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem >04:41:38,686 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main, 1.2] >04:41:38,692 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem >04:41:38,720 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem >04:41:38,808 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension >04:41:38,841 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2 >04:41:39,298 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) >04:41:39,380 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2) >04:41:39,502 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service >04:41:39,909 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory >04:41:40,045 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default] >04:41:40,523 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.4.Final-redhat-7 >04:41:41,109 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080 >04:41:41,156 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080 >04:41:42,021 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started >04:41:42,906 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingpaging) >04:41:42,909 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221006: Waiting to obtain live lock >04:41:43,149 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221013: Using NIO Journal >04:41:43,174 INFO [org.jboss.as.jacorb] (MSC service thread 1-1) JBAS016328: CORBA Naming Service started >04:41:43,364 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/deployments >04:41:43,366 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] >04:41:43,824 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221034: Waiting to obtain live lock >04:41:43,825 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221035: Live Server Obtained live lock >04:41:43,984 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:6999 >04:41:44,398 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 0.0.0.0:4447 >04:41:45,815 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 0.0.0.0:5455 for CORE protocol >04:41:45,832 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 0.0.0.0:5445 for CORE protocol >04:41:45,846 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221007: Server is now live >04:41:45,847 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [486044ce-5cc8-11e3-a2cf-979e3c98f2cd] >04:41:45,870 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 58) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "joner7.bc.jonqe.lab.eng.bos.redhat.com". If this new address is incorrect please manually configure the connector to use the proper one. >04:41:45,934 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory >04:41:45,940 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory >04:41:46,010 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA >04:41:46,076 INFO [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started >04:41:46,077 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra >04:41:46,082 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] >04:41:46,238 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:6990/management >04:41:46,239 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:6990 >04:41:46,239 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started in 12135ms - Started 145 of 207 services (61 services are passive or on-demand) >04:42:54,537 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8080 >04:42:54,543 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8080 >04:42:54,564 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] >04:42:54,566 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] >04:42:54,570 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started >04:42:54,576 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory >04:42:54,588 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory >04:42:54,655 INFO [org.hornetq.ra] (MSC service thread 1-1) HQ151003: HornetQ resource adaptor stopped >04:42:54,731 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221002: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [486044ce-5cc8-11e3-a2cf-979e3c98f2cd] stopped >04:42:54,746 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) stopped in 239ms >04:43:46,698 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1 >04:43:47,005 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 >04:43:47,174 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting >04:43:47,203 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties: > [Standalone] = > app.name = rhq-server > file.encoding = UTF-8 > file.encoding.pkg = sun.io > file.separator = / > hibernate.dialect = org.hibernate.dialect.PostgreSQLDialect > java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment > java.awt.headless = true > java.awt.printerjob = sun.print.PSPrinterJob > java.class.path = /home/hudson/jon-server-3.2.0.CR1/jbossas/jboss-modules.jar > java.class.version = 50.0 > java.endorsed.dirs = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/endorsed > java.ext.dirs = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/ext:/usr/java/packages/lib/ext > java.home = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre > java.io.tmpdir = /tmp > java.library.path = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > java.net.preferIPv4Stack = true > java.runtime.name = OpenJDK Runtime Environment > java.runtime.version = 1.6.0_24-b24 > java.security.manager = > java.security.policy = =/home/hudson/jon-server-3.2.0.CR1/bin/internal/rhq-server.security-policy > java.specification.name = Java Platform API Specification > java.specification.vendor = Sun Microsystems Inc. > java.specification.version = 1.6 > java.util.logging.manager = org.jboss.logmanager.LogManager > java.vendor = Sun Microsystems Inc. > java.vendor.url = http://java.sun.com/ > java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi > java.version = 1.6.0_24 > java.vm.info = mixed mode > java.vm.name = OpenJDK 64-Bit Server VM > java.vm.specification.name = Java Virtual Machine Specification > java.vm.specification.vendor = Sun Microsystems Inc. > java.vm.specification.version = 1.0 > java.vm.vendor = Sun Microsystems Inc. > java.vm.version = 20.0-b12 > javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder > javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory > javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory > javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory > javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory > javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory > javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory > javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory > javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory > javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory > jboss.bind.address = 0.0.0.0 > jboss.bind.address.management = 127.0.0.1 > jboss.home.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas > jboss.host.name = joner7 > jboss.management.http.port = 6990 > jboss.management.https.port = 6443 > jboss.management.native.port = 6999 > jboss.modules.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/modules > jboss.modules.system.pkgs = org.jboss.byteman > jboss.node.name = joner7 > jboss.qualified.host.name = joner7.bc.jonqe.lab.eng.bos.redhat.com > jboss.server.base.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone > jboss.server.config.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/configuration > jboss.server.data.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data > jboss.server.default.config = standalone-full.xml > jboss.server.deploy.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/content > jboss.server.log.dir = /home/hudson/jon-server-3.2.0.CR1/logs > jboss.server.name = joner7 > jboss.server.persist.config = true > jboss.server.temp.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/tmp > jboss.socket.binding.port-offset = 0 > line.separator = > > logging.configuration = file:/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/configuration/logging.properties > module.path = /home/hudson/jon-server-3.2.0.CR1/modules:/home/hudson/jon-server-3.2.0.CR1/jbossas/modules > org.apache.coyote.http11.Http11Protocol.COMPRESSION = on > org.apache.coyote.http11.Http11Protocol.COMPRESSION_MIME_TYPES = text/javascript,text/css,text/html > org.jboss.boot.log.file = /home/hudson/jon-server-3.2.0.CR1/logs/server.log > org.jboss.resolver.warning = true > org.xml.sax.driver = __redirected.__XMLReaderFactory > os.arch = amd64 > os.name = Linux > os.version = 2.6.32-358.el6.x86_64 > path.separator = : > rhq.autoinstall.database = auto > rhq.autoinstall.enabled = true > rhq.autoinstall.public-endpoint-address = > rhq.communications.connector.bind-address = > rhq.communications.connector.bind-port = > rhq.communications.connector.security.client-auth-mode = none > rhq.communications.connector.security.keystore.alias = RHQ > rhq.communications.connector.security.keystore.file = ${jboss.server.config.dir}/rhq.keystore > rhq.communications.connector.security.keystore.key-password = RHQManagement > rhq.communications.connector.security.keystore.password = RHQManagement > rhq.communications.connector.security.keystore.type = JKS > rhq.communications.connector.security.secure-socket-protocol = TLS > rhq.communications.connector.security.truststore.file = ${jboss.server.config.dir}/rhq.truststore > rhq.communications.connector.security.truststore.password = RHQManagement > rhq.communications.connector.security.truststore.type = JKS > rhq.communications.connector.transport = servlet > rhq.communications.connector.transport-params = /jboss-remoting-servlet-invoker/ServerInvokerServlet > rhq.communications.global-concurrency-limit = 30 > rhq.communications.multicast-detector.bind-address = > rhq.communications.multicast-detector.enabled = false > rhq.communications.multicast-detector.multicast-address = 224.16.16.16 > rhq.communications.multicast-detector.port = 16162 > rhq.server.agent-downloads-limit = 45 > rhq.server.client-downloads-limit = 5 > rhq.server.client.security.keystore.alias = RHQ > rhq.server.client.security.keystore.file = ${jboss.server.config.dir}/rhq.keystore > rhq.server.client.security.keystore.key-password = RHQManagement > rhq.server.client.security.keystore.password = RHQManagement > rhq.server.client.security.keystore.type = JKS > rhq.server.client.security.secure-socket-protocol = TLS > rhq.server.client.security.server-auth-mode-enabled = false > rhq.server.client.security.truststore.file = ${jboss.server.config.dir}/rhq.truststore > rhq.server.client.security.truststore.password = RHQManagement > rhq.server.client.security.truststore.type = JKS > rhq.server.concurrency-limit.availability-report = 25 > rhq.server.concurrency-limit.configuration-update = 10 > rhq.server.concurrency-limit.content-download = 5 > rhq.server.concurrency-limit.content-report = 5 > rhq.server.concurrency-limit.inventory-report = 5 > rhq.server.concurrency-limit.inventory-sync = 10 > rhq.server.concurrency-limit.measurement-report = 10 > rhq.server.concurrency-limit.measurement-schedule-request = 10 > rhq.server.content.filesystem = ${jboss.server.data.dir}/packagebits > rhq.server.database.connection-url = jdbc:postgresql://10.16.23.89:5432/rhq > rhq.server.database.db-name = rhq > rhq.server.database.password = 1eeb2f255e832171df8592078de921bc > rhq.server.database.port = 5432 > rhq.server.database.server-name = 10.16.23.89 > rhq.server.database.type-mapping = PostgreSQL > rhq.server.database.user-name = rhqadmin > rhq.server.email.from-address = rhqadmin@localhost > rhq.server.email.smtp-host = localhost > rhq.server.email.smtp-port = 25 > rhq.server.high-availability.name = > rhq.server.home = /home/hudson/jon-server-3.2.0.CR1 > rhq.server.log-level = INFO > rhq.server.maintenance-mode-at-startup = false > rhq.server.management.password = > rhq.server.operation-timeout = 600 > rhq.server.plugin-scan-period-ms = 300000 > rhq.server.quartz.driverDelegateClass = org.quartz.impl.jdbcjobstore.PostgreSQLDelegate > rhq.server.quartz.lockHandlerClass = org.quartz.impl.jdbcjobstore.StdRowLockSemaphore > rhq.server.quartz.selectWithLockSQL = SELECT * FROM {0}LOCKS ROWLOCK WHERE LOCK_NAME = ? FOR UPDATE > rhq.server.socket.binding.port.ajp = 7009 > rhq.server.socket.binding.port.http = 7080 > rhq.server.socket.binding.port.https = 7443 > rhq.server.socket.binding.port.jacorb = 2528 > rhq.server.socket.binding.port.jacorb-ssl = 2529 > rhq.server.socket.binding.port.messaging = 4449 > rhq.server.socket.binding.port.messaging-throughput = 4455 > rhq.server.socket.binding.port.osgi-http = 7090 > rhq.server.socket.binding.port.remoting = 3447 > rhq.server.socket.binding.port.txn-recovery-environment = 3712 > rhq.server.socket.binding.port.txn-status-manager = 3713 > rhq.server.startup.web.max-connections = 200 > rhq.server.tomcat.security.client-auth-mode = false > rhq.server.tomcat.security.keystore.alias = RHQ > rhq.server.tomcat.security.keystore.file = ${jboss.server.config.dir}/rhq.keystore > rhq.server.tomcat.security.keystore.password = RHQManagement > rhq.server.tomcat.security.keystore.type = JKS > rhq.server.tomcat.security.secure-socket-protocol = TLS > rhq.server.tomcat.security.truststore.file = ${jboss.server.config.dir}/rhq.truststore > rhq.server.tomcat.security.truststore.password = RHQManagement > rhq.server.tomcat.security.truststore.type = JKS > rhq.storage.cql-port = 9142 > rhq.storage.gossip-port = 7100 > rhq.storage.nodes = joner7.bc.jonqe.lab.eng.bos.redhat.com > rhq.storage.password = > rhq.storage.username = > rhq.sync.endpoint-address = false > sun.arch.data.model = 64 > sun.boot.class.path = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/netx.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/plugin.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/classes > sun.boot.library.path = /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64 > sun.cpu.endian = little > sun.cpu.isalist = > sun.io.unicode.encoding = UnicodeLittle > sun.java.command = /home/hudson/jon-server-3.2.0.CR1/jbossas/jboss-modules.jar -mp /home/hudson/jon-server-3.2.0.CR1/modules:/home/hudson/jon-server-3.2.0.CR1/jbossas/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/home/hudson/jon-server-3.2.0.CR1/jbossas -Djboss.server.base.dir=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone -P /home/hudson/jon-server-3.2.0.CR1/bin/rhq-server.properties > sun.java.launcher = SUN_STANDARD > sun.jnu.encoding = UTF-8 > sun.lang.ClassLoader.allowArraySyntax = true > sun.management.compiler = HotSpot 64-Bit Tiered Compilers > sun.os.patch.level = unknown > sun.rmi.dgc.client.gcInterval = 3600000 > sun.rmi.dgc.server.gcInterval = 3600000 > user.country = GB > user.dir = /home/hudson/jon-server-3.2.0.CR1/jbossas/bin > user.home = /home/hudson > user.language = en > user.name = hudson > user.timezone = America/New_York >04:43:47,219 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -XX:+UseCompressedOops -Dapp.name=rhq-server -Xms1024M -Xmx1024M -XX:PermSize=256M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Drhq.server.home=/home/hudson/jon-server-3.2.0.CR1 -Djboss.server.log.dir=/home/hudson/jon-server-3.2.0.CR1/logs -Djava.awt.headless=true -Dsun.lang.ClassLoader.allowArraySyntax=true -Djboss.server.default.config=standalone-full.xml -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.security.manager -Djava.security.policy==/home/hudson/jon-server-3.2.0.CR1/bin/internal/rhq-server.security-policy -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on -Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION_MIME_TYPES=text/javascript,text/css,text/html -Dorg.jboss.boot.log.file=/home/hudson/jon-server-3.2.0.CR1/logs/server.log -Dlogging.configuration=file:/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/configuration/logging.properties >04:43:49,946 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1 >04:43:49,965 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1 >04:43:49,967 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) >04:43:49,987 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.16.GA-redhat-1 >04:43:50,173 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem. >04:43:50,178 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem >04:43:50,267 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012605: Activated the following JSF Implementations: [main, 1.2] >04:43:50,302 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem >04:43:50,343 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem >04:43:50,385 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension >04:43:50,509 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service >04:43:50,561 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2 >04:43:50,872 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2) >04:43:50,888 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) >04:43:51,132 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory >04:43:51,317 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default] >04:43:51,848 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.4.Final-redhat-7 >04:43:52,371 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080 >04:43:52,426 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080 >04:43:53,257 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started >04:43:53,998 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingpaging) >04:43:54,013 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221006: Waiting to obtain live lock >04:43:54,221 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221013: Using NIO Journal >04:43:54,279 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started >04:43:54,417 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/deployments >04:43:54,419 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] >04:43:54,712 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221034: Waiting to obtain live lock >04:43:54,712 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221035: Live Server Obtained live lock >04:43:55,029 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:6999 >04:43:55,053 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0:4447 >04:43:56,628 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 0.0.0.0:5455 for CORE protocol >04:43:56,635 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 0.0.0.0:5445 for CORE protocol >04:43:56,648 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221007: Server is now live >04:43:56,649 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [486044ce-5cc8-11e3-a2cf-979e3c98f2cd] >04:43:56,692 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 58) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "joner7.bc.jonqe.lab.eng.bos.redhat.com". If this new address is incorrect please manually configure the connector to use the proper one. >04:43:56,837 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory >04:43:56,842 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory >04:43:56,965 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA >04:43:57,076 INFO [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started >04:43:57,077 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra >04:43:57,081 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] >04:43:57,230 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:6990/management >04:43:57,231 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:6990 >04:43:57,231 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started in 11327ms - Started 145 of 207 services (61 services are passive or on-demand) >04:44:17,036 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:7443 >04:44:17,043 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:7443 >04:44:17,640 INFO [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 3) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2) >04:44:17,783 INFO [org.jboss.as.connector.subsystems.datasources] (management-handler-thread - 1) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2) >04:44:18,135 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/NoTxRHQDS] >04:44:18,246 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/RHQDS] >04:44:18,349 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.AlertConditionQueue >04:44:18,418 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/AlertConditionQueue >04:44:18,521 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftChangesetQueue >04:44:18,534 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftChangesetQueue >04:44:18,621 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftFileQueue >04:44:18,634 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftFileQueue >04:44:18,801 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS015888: Creating http management service using socket-binding (management-http) >04:44:18,804 INFO [org.apache.catalina.core] (MSC service thread 1-1) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started >04:44:18,909 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] >04:44:20,136 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started >04:44:20,145 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/RHQDS] >04:44:20,157 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:7443 >04:44:20,159 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/0.0.0.0:8080 >04:44:20,159 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:8080 >04:44:20,160 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/0.0.0.0:7443 >04:44:20,171 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/NoTxRHQDS] >04:44:20,188 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] >04:44:20,194 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014002: UnBinding JAXR ConnectionFactory: java:jboss/jaxr/ConnectionFactory >04:44:20,208 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory >04:44:20,231 INFO [org.hornetq.ra] (MSC service thread 1-2) HQ151003: HornetQ resource adaptor stopped >04:44:20,234 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011605: Unbound messaging object to jndi name java:/queue/DriftChangesetQueue >04:44:20,241 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011605: Unbound messaging object to jndi name java:/queue/DriftFileQueue >04:44:20,254 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011605: Unbound messaging object to jndi name java:/ConnectionFactory >04:44:20,257 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011605: Unbound messaging object to jndi name java:/queue/AlertConditionQueue >04:44:20,316 INFO [org.hornetq.core.server] (MSC service thread 1-2) HQ221002: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [486044ce-5cc8-11e3-a2cf-979e3c98f2cd] stopped >04:44:35,177 WARN [org.jboss.as.controller] (MSC service thread 1-1) JBAS014618: Graceful shutdown of the handler used for native management requests did not complete within [15000] ms but shutdown of the underlying communication channel is proceeding >04:44:35,178 WARN [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014626: Operation was interrupted before stability could be reached >04:44:35,202 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015401: Unbound mail session [java:jboss/mail/Default] >04:44:35,239 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) stopped in 15132ms >04:44:35,241 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting >04:44:35,506 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) >04:44:35,537 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem >04:44:35,543 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem >04:44:35,546 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem >04:44:35,536 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem. >04:44:35,568 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2) >04:44:35,548 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension >04:44:35,646 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2 >04:44:35,656 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) >04:44:35,672 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service >04:44:35,704 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.2) >04:44:35,711 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2) >04:44:35,765 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.4.Final-redhat-7 >04:44:35,756 INFO [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory >04:44:35,774 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default] >04:44:35,808 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started >04:44:35,834 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:7080 >04:44:35,839 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:7080 >04:44:35,841 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingjournal,bindingsDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingbindings,largeMessagesDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messaginglargemessages,pagingDirectory=/home/hudson/jon-server-3.2.0.CR1/jbossas/standalone/data/messagingpaging) >04:44:35,841 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221006: Waiting to obtain live lock >04:44:35,849 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221013: Using NIO Journal >04:44:35,848 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:7443 >04:44:35,861 INFO [org.apache.coyote.http11] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:7443 >04:44:35,904 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221034: Waiting to obtain live lock >04:44:35,905 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221035: Live Server Obtained live lock >04:44:35,935 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started >04:44:36,018 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:6999 >04:44:36,020 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:3447 >04:44:36,032 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/NoTxRHQDS] >04:44:36,034 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/RHQDS] >04:44:36,384 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 127.0.0.1:4449 for CORE protocol >04:44:36,389 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 127.0.0.1:4455 for CORE protocol >04:44:36,392 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221007: Server is now live >04:44:36,392 INFO [org.hornetq.core.server] (MSC service thread 1-1) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [486044ce-5cc8-11e3-a2cf-979e3c98f2cd] >04:44:36,397 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.queue.AlertConditionQueue >04:44:36,409 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/queue/AlertConditionQueue >04:44:36,412 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory >04:44:36,413 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory >04:44:36,414 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.DriftChangesetQueue >04:44:36,415 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/queue/DriftChangesetQueue >04:44:36,415 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.DriftFileQueue >04:44:36,416 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/DriftFileQueue >04:44:36,422 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA >04:44:36,448 INFO [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started >04:44:36,449 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra >04:44:36,450 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] >04:44:36,538 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:6990/management >04:44:36,539 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled >04:44:36,539 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started in 1297ms - Started 155 of 232 services (71 services are passive or on-demand) >04:44:38,365 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "rhq.ear" (runtime-name: "rhq.ear") >04:44:47,029 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb-api.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:47,030 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:47,031 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jsr173_1.0_api.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:47,031 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxb1-impl.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:47,054 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-agentupdate.war") >04:44:47,055 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-server.jar") >04:44:47,056 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-remoting.war") >04:44:47,056 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-rest.war") >04:44:47,057 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-rest-examples.war") >04:44:47,058 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-portal.war") >04:44:47,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-content_http.war") >04:44:47,059 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-core-domain-ejb3.jar") >04:44:47,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "coregui.war") >04:44:47,058 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-downloads.war") >04:44:47,061 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "rhq-client.war") >04:44:47,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry lib/postgresql-9.2-1002.jdbc4.jar in /home/hudson/jon-server-3.2.0.CR1/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar does not point to a valid jar for a Class-Path reference. >04:44:47,085 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry lib/activation-1.1.1.jar in /home/hudson/jon-server-3.2.0.CR1/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar does not point to a valid jar for a Class-Path reference. >04:44:47,086 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry lib/snakeyaml-1.8.jar in /home/hudson/jon-server-3.2.0.CR1/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-server.jar does not point to a valid jar for a Class-Path reference. >04:44:49,995 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry commons-beanutils.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:49,996 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry commons-digester.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:50,000 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry commons-fileupload.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:50,000 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry commons-logging.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:50,001 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry commons-validator.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:50,001 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jakarta-oro.jar in /home/hudson/jon-server-3.2.0.CR1/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. >04:44:50,831 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for rhqpu >04:44:52,985 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:52,985 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:52,985 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:52,986 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:52,986 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice. >04:44:52,986 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.infinispan:main") which may be changed or removed in future versions without notice. >04:44:52,995 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice. >04:44:52,996 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.rhq.ear" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice. >04:44:53,003 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. >04:44:53,003 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-1) JBAS018568: Deployment "deployment.rhq.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. >04:44:53,003 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,004 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,074 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,075 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,075 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,075 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,076 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,076 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,077 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,077 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,095 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,095 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,104 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:53,108 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:54,666 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:54,667 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) 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. >04:44:58,533 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,533 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,540 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,540 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,540 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,541 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,541 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,547 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.MeasurementBaselineManagerLocal > java:app/rhq-server/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerLocal > java:module/MeasurementBaselineManagerBean!org.rhq.enterprise.server.measurement.MeasurementBaselineManagerLocal > 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 > >04:44:58,547 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.SynchronizationManagerLocal > java:app/rhq-server/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerLocal > java:module/SynchronizationManagerBean!org.rhq.enterprise.server.sync.SynchronizationManagerLocal > 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 > >04:44:58,548 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,553 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.MeasurementScheduleManagerLocal > java:app/rhq-server/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerLocal > java:module/MeasurementScheduleManagerBean!org.rhq.enterprise.server.measurement.MeasurementScheduleManagerLocal > 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 > >04:44:58,554 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,554 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,555 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,556 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,557 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,557 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,558 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,562 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,563 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,563 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,564 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,568 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,569 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,569 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,569 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,570 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,570 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,574 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,575 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,575 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,575 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,576 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,576 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,581 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,582 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,582 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,582 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,583 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,583 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,587 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,588 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,588 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,588 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.ClusterManagerLocal > java:app/rhq-server/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerLocal > java:module/ClusterManagerBean!org.rhq.enterprise.server.resource.cluster.ClusterManagerLocal > 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 > >04:44:58,589 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,589 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,593 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,594 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,594 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,594 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,595 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,595 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,599 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,600 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,600 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,603 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,604 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,604 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,604 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,604 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,605 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,605 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.ResourceGroupManagerLocal > java:app/rhq-server/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerLocal > java:module/ResourceGroupManagerBean!org.rhq.enterprise.server.resource.group.ResourceGroupManagerLocal > 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 > >04:44:58,611 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.BundleManagerLocal > java:app/rhq-server/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerLocal > java:module/BundleManagerBean!org.rhq.enterprise.server.bundle.BundleManagerLocal > 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 > >04:44:58,611 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,611 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,612 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,612 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,612 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,612 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,613 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,613 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,618 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,618 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,618 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,619 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,619 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,623 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,624 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,624 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,624 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,625 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,625 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,629 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,629 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,630 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,630 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,631 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,631 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,632 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,632 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,635 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,636 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,636 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,636 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,637 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.SupportManagerLocal > java:app/rhq-server/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerLocal > java:module/SupportManagerBean!org.rhq.enterprise.server.support.SupportManagerLocal > 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 > >04:44:58,640 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,641 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.MeasurementDataManagerLocal > java:app/rhq-server/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerLocal > java:module/MeasurementDataManagerBean!org.rhq.enterprise.server.measurement.MeasurementDataManagerLocal > 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 > >04:44:58,641 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,641 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,642 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,642 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,642 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,643 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,643 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,645 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,645 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,645 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,646 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,646 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,646 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.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 > 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 > >04:44:58,647 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,647 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,647 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,648 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,648 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,651 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,652 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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.OperationManagerLocal > java:app/rhq-server/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerLocal > java:module/OperationManagerBean!org.rhq.enterprise.server.operation.OperationManagerLocal > 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 > >04:44:58,652 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,652 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,653 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,653 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,653 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,654 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,654 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,659 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,660 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,660 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:58,660 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) 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 > >04:44:59,007 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 63) JBAS011402: Starting Persistence Unit Service 'rhq.ear/rhq-core-domain-ejb3.jar#rhqpu' >04:44:59,208 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 63) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2} >04:44:59,215 INFO [org.hibernate.Version] (ServerService Thread Pool -- 63) HHH000412: Hibernate Core {4.2.0.SP1-redhat-1} >04:44:59,217 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 63) HHH000206: hibernate.properties not found >04:44:59,219 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 63) HHH000021: Bytecode provider name : javassist >04:44:59,253 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 63) HHH000204: Processing PersistenceUnitInfo [ > name: rhqpu > ...] >04:45:02,798 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 63) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider >04:45:04,369 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 63) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect >04:45:04,421 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 >04:45:04,464 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 63) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory >04:45:04,599 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 63) HV000001: Hibernate Validator 4.3.1.Final-redhat-1 >04:45:29,074 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'AlertConditionConsumerBean' with 'hornetq-ra' resource adapter >04:45:29,076 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) JBAS014142: Started message driven bean 'DriftChangesetBean' with 'hornetq-ra' resource adapter >04:45:29,088 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'DriftFileBean' with 'hornetq-ra' resource adapter >04:45:29,985 INFO [org.rhq.enterprise.server.core.CoreServer] (ServerService Thread Pool -- 77) Version=[4.9.0.JON320CR1], Build Number=[d0dc0b6], Build Date=[03.Dec.2013 12.00.37 EST] >04:45:30,058 INFO [org.rhq.enterprise.server.scheduler.SchedulerService] (ServerService Thread Pool -- 65) Scheduler has a default operation timeout of [600] seconds. >04:45:31,426 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /portal >04:45:31,475 INFO [org.apache.catalina.core] (ServerService Thread Pool -- 65) JBWEB001093: The listener com.sun.faces.config.ConfigureListener is already configured for this context, the duplicate definition has been ignored >04:45:31,633 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 65) Initializing Mojarra (1.2_15-b01-redhat-3) for context '/portal' >04:45:34,663 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 65) JSF1051: Service entry 'org.jboss.as.jsf.injection.JSFInjectionProvider' does not extend DiscoverableInjectionProvider. Entry will be ignored. >04:45:34,663 INFO [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 65) JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed. >04:45:35,731 INFO [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 65) Initialized response-time filter for webapp with context root 'portal'. >04:45:35,759 INFO [org.ajax4jsf.cache.CacheManager] (ServerService Thread Pool -- 65) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory >04:45:35,762 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 65) 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/ReportsHandlerBean;org.rhq.enterprise.server.rest.ReportsHandlerBean;true,java:app/rhq-server/OperationsHandlerBean;org.rhq.enterprise.server.rest.OperationsHandlerBean;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} >04:45:35,763 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 65) Creating LRUMap cache instance of default capacity >04:45:35,793 INFO [org.ajax4jsf.cache.CacheManager] (ServerService Thread Pool -- 65) Selected [org.ajax4jsf.cache.LRUMapCacheFactory] cache factory >04:45:35,793 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 65) 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/ReportsHandlerBean;org.rhq.enterprise.server.rest.ReportsHandlerBean;true,java:app/rhq-server/OperationsHandlerBean;org.rhq.enterprise.server.rest.OperationsHandlerBean;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} >04:45:35,794 INFO [org.ajax4jsf.cache.LRUMapCacheFactory] (ServerService Thread Pool -- 65) Creating LRUMap cache instance of default capacity >04:45:37,513 INFO [org.apache.struts.tiles.TilesPlugin] (ServerService Thread Pool -- 65) Tiles definition factory loaded for module ''. >04:45:37,594 INFO [org.apache.struts.validator.ValidatorPlugIn] (ServerService Thread Pool -- 65) Loading validation rules file from '/WEB-INF/validation/validator-rules.xml' >04:45:37,600 INFO [org.apache.struts.validator.ValidatorPlugIn] (ServerService Thread Pool -- 65) Loading validation rules file from '/WEB-INF/validation/validation.xml' >04:45:38,122 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /client >04:45:38,375 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018210: Register web context: /downloads >04:45:38,384 INFO [org.rhq.enterprise.gui.download.DownloadServlet] (ServerService Thread Pool -- 66) Starting the RHQ download servlet... >04:45:38,402 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /agentupdate >04:45:38,411 INFO [org.rhq.enterprise.gui.agentupdate.AgentUpdateServlet] (ServerService Thread Pool -- 65) Starting the RHQ agent update servlet >04:45:38,669 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018210: Register web context: /content >04:45:38,687 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 66) Initializing Mojarra 2.1.19-jbossorg-1 20130304-0420 for context '/content' >04:45:42,845 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /rest >04:45:42,868 INFO [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 65) Initialized response-time filter for webapp with context root 'rest'. >04:45:42,904 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /rest-examples >04:45:42,957 INFO [org.jboss.web] (ServerService Thread Pool -- 65) JBAS018210: Register web context: /jboss-remoting-servlet-invoker >04:45:43,083 INFO [org.jboss.web] (ServerService Thread Pool -- 66) JBAS018210: Register web context: /coregui >04:45:43,127 INFO [org.rhq.helpers.rtfilter.filter.RtFilter] (ServerService Thread Pool -- 66) Initialized response-time filter for webapp with context root 'coregui'. >04:45:43,257 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018559: Deployed "rhq.ear" (runtime-name : "rhq.ear") >04:45:49,592 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-remoting-servlet-invoker]] (http-/0.0.0.0:7080-1) ServerInvokerServlet: invokerObjectNameQuery=jboss.remoting:service=invoker,rhq.communications.connector.rhqtype=server,* >04:45:49,619 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-remoting-servlet-invoker].[ServerInvokerServlet]] (http-/0.0.0.0:7080-1) JBWEB000235: Allocate exception for servlet ServerInvokerServlet: javax.servlet.ServletException: Could not find the remoting servlet invoker: jboss.remoting:service=invoker,rhq.communications.connector.rhqtype=server,* - need to wait for remoting to be initialized later > at org.rhq.enterprise.communications.servlet.ServerInvokerServlet.getInvokerFromInvokerName(ServerInvokerServlet.java:78) [classes:] > at org.jboss.remoting.transport.servlet.web.ServerInvokerServlet.init(ServerInvokerServlet.java:78) [jboss-remoting-2.5.4.SP5.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_24] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.6.0_24] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.6.0_24] > at java.lang.reflect.Method.invoke(Method.java:616) [rt.jar:1.6.0_24] > at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:263) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:261) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_24] > at javax.security.auth.Subject.doAsPrivileged(Subject.java:537) [rt.jar:1.6.0_24] > at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:295) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:155) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:108) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1188) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] > >04:45:53,128 INFO [org.rhq.enterprise.server.naming.NamingHack] (pool-9-thread-1) Modifying the naming subsystem to enable secure execution of scripts inside the server... >04:45:53,157 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) All business tier deployments are complete - finishing the startup... >04:45:53,656 INFO [org.rhq.enterprise.server.storage.StorageClientManagerBean] (pool-9-thread-1) Initializing storage client subsystem >04:45:53,697 WARN [org.rhq.enterprise.server.system.SystemManagerBean] (pool-9-thread-1) MasterServerPluginContainer is not started yet >04:45:53,833 INFO [org.rhq.cassandra.schema.VersionManager] (pool-9-thread-1) Preparing to check storage schema compatibility. >04:45:53,833 INFO [org.rhq.cassandra.schema.SessionManager] (pool-9-thread-1) Initializing session for [username: tqccmzrb, cqlPort: 9142, nodes: [joner7-ha-master.bc.jonqe.lab.eng.bos.redhat.com]] >04:45:55,057 INFO [org.rhq.cassandra.schema.VersionManager] (pool-9-thread-1) Completed storage schema compatibility check. >04:45:55,057 INFO [org.rhq.cassandra.schema.SessionManager] (pool-9-thread-1) Shutting down cluster >04:45:55,760 INFO [org.rhq.server.metrics.MetricsDAO] (pool-9-thread-1) Initializing prepared statements >04:45:55,803 INFO [org.rhq.server.metrics.MetricsDAO] (pool-9-thread-1) Finished initializing prepared statements in 43 ms >04:45:56,118 INFO [org.rhq.server.metrics.MetricsServer] (pool-9-thread-1) Did not find any raw data in the storage database since the last server shutdown. Raw data aggregate computations are up to date. >04:45:56,119 INFO [org.rhq.enterprise.server.storage.StorageClientManagerBean] (pool-9-thread-1) Storage client subsystem is now initialized >04:45:56,270 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Starting hibernate statistics monitoring... >04:45:56,293 INFO [org.rhq.core.domain.server.PersistenceUtility] (pool-9-thread-1) Hibernate statistics enable flag set to [true] >04:45:56,294 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Initializing the scheduler.... >04:45:56,355 INFO [org.quartz.impl.StdSchedulerFactory] (pool-9-thread-1) Using custom data access locking (synchronization): org.quartz.impl.jdbcjobstore.StdRowLockSemaphore >04:45:56,379 INFO [org.quartz.core.SchedulerSignalerImpl] (pool-9-thread-1) Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl >04:45:56,380 INFO [org.quartz.core.QuartzScheduler] (pool-9-thread-1) Quartz Scheduler v.1.6.5 created. >04:45:56,381 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (pool-9-thread-1) JobStoreCMT initialized. >04:45:56,382 INFO [org.quartz.impl.StdSchedulerFactory] (pool-9-thread-1) Quartz scheduler 'RHQScheduler' initialized from an externally provided properties instance. >04:45:56,382 INFO [org.quartz.impl.StdSchedulerFactory] (pool-9-thread-1) Quartz scheduler version: 1.6.5 >04:45:56,382 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Starting the agent/server plugin deployer... >04:45:56,398 INFO [org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner] (pool-9-thread-1) user plugin dir=/home/hudson/jon-server-3.2.0.CR1/plugins >04:45:56,398 INFO [org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner] (pool-9-thread-1) agent plugin dir=/home/hudson/jon-server-3.2.0.CR1/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-downloads/rhq-plugins >04:45:56,398 INFO [org.rhq.enterprise.server.core.plugin.PluginDeploymentScanner] (pool-9-thread-1) server plugin dir=/home/hudson/jon-server-3.2.0.CR1/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-serverplugins >04:46:03,953 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [RHQAgent] >04:46:04,334 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [Platforms] >04:46:04,825 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [RHQStorage] >04:46:05,212 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [Cassandra] >04:46:05,429 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [AntBundlePlugin] >04:46:05,640 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [Database] >04:46:06,202 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [Script] >04:46:06,508 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [IIS] >04:46:06,876 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (pool-9-thread-1) Discovered agent plugin [JMX] >04:46:07,026 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [DiskContentSourcePlugin], version 4.9.0.JON320CR1 >04:46:07,041 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-email], version 4.9.0.JON320CR1 >04:46:07,057 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-operations], version 4.9.0.JON320CR1 >04:46:07,072 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [packagetype-cli], version 4.9.0.JON320CR1 >04:46:07,099 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-roles], version 4.9.0.JON320CR1 >04:46:07,124 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [JBossASPatchContentSourcePlugin], version 4.9.0.JON320CR1 >04:46:07,162 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [AlertDefinitionPlugin], version 1.0 >04:46:07,177 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [UrlContentSourcePlugin], version 4.9.0.JON320CR1 >04:46:07,191 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-snmp], version 4.9.0.JON320CR1 >04:46:07,206 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-cli], version 4.9.0.JON320CR1 >04:46:07,237 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [AntBundleServerPlugin], version 4.9.0.JON320CR1 >04:46:07,253 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [drift-jpa], version 1.0 >04:46:07,273 INFO [org.rhq.enterprise.server.core.plugin.ServerPluginScanner] (pool-9-thread-1) Registered server plugin [alert-subject], version 1.0 >04:46:07,289 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Starting the master server plugin container... >04:46:07,348 INFO [org.quartz.core.SchedulerSignalerImpl] (pool-9-thread-1) Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl >04:46:07,348 INFO [org.quartz.core.QuartzScheduler] (pool-9-thread-1) Quartz Scheduler v.1.6.5 created. >04:46:07,348 INFO [org.quartz.simpl.RAMJobStore] (pool-9-thread-1) RAMJobStore initialized. >04:46:07,348 INFO [org.quartz.impl.StdSchedulerFactory] (pool-9-thread-1) Quartz scheduler 'RHQServerPluginsJobs' initialized from an externally provided properties instance. >04:46:07,349 INFO [org.quartz.impl.StdSchedulerFactory] (pool-9-thread-1) Quartz scheduler version: 1.6.5 >04:46:07,349 INFO [org.quartz.core.QuartzScheduler] (pool-9-thread-1) Scheduler RHQServerPluginsJobs_$_NON_CLUSTERED started. >04:46:09,290 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-email] >04:46:09,330 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [drift-jpa] >04:46:09,343 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [DiskContentSourcePlugin] >04:46:09,352 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-operations] >04:46:09,360 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [JBossASPatchContentSourcePlugin] >04:46:09,370 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [UrlContentSourcePlugin] >04:46:09,375 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-snmp] >04:46:09,377 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-roles] >04:46:09,422 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [AlertDefinitionPlugin] >04:46:09,449 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [packagetype-cli] >04:46:09,491 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-cli] >04:46:09,497 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [alert-subject] >04:46:09,676 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Preloaded server plugin [AntBundleServerPlugin] >04:46:09,676 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Drift Plugin] >04:46:09,677 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Bundle Plugin] >04:46:10,453 INFO [org.rhq.enterprise.server.plugin.pc.content.ContentProviderManager] (pool-9-thread-1) Initializing content source adapter for [ContentSource: id=[101], name=[JBoss CP Patch Feed]] of type [ContentSourceType: name=[JBossASPatchSource]] >04:46:10,478 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Content Plugin] >04:46:10,484 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Alert Plugin] >04:46:10,484 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Package Type Plugin] >04:46:10,801 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master PC started server plugin container for plugin type [Generic Plugin] >04:46:10,806 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master server plugin container has been initialized >04:46:10,861 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Starting the server-agent communications services... >04:46:11,274 INFO [org.rhq.enterprise.communications.ServiceContainer] (pool-9-thread-1) {ServiceContainer.global-concurrency-limit-set}Global concurrency limit has been set - no more than [30] incoming commands will be accepted at the same time >04:46:11,473 INFO [org.rhq.enterprise.communications.ServiceContainer] (pool-9-thread-1) {ServiceContainer.started}Service container started - ready to accept incoming commands >04:46:11,481 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Starting the scheduler... >04:46:11,482 INFO [org.rhq.enterprise.server.scheduler.SchedulerService] (pool-9-thread-1) Scheduler service will start Quartz scheduler now - jobs will begin executing. >04:46:11,537 INFO [org.quartz.core.QuartzScheduler] (pool-9-thread-1) Scheduler RHQScheduler_$_joner7.bc.jonqe.lab.eng.bos.redhat.com1386150356360 started. >04:46:11,537 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Scheduling asynchronous jobs... >04:46:11,631 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.SavedSearchResultCountRecalculationJob:org.rhq.enterprise.server.scheduler.jobs.SavedSearchResultCountRecalculationJob] to fire next at [Wed Dec 04 04:47:11 EST 2013] and repeat every [60000] milliseconds >04:46:11,661 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.AsyncResourceDeleteJob:org.rhq.enterprise.server.scheduler.jobs.AsyncResourceDeleteJob] to fire next at [Wed Dec 04 04:47:11 EST 2013] and repeat every [300000] milliseconds >04:46:11,706 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.PurgeResourceTypesJob:org.rhq.enterprise.server.scheduler.jobs.PurgeResourceTypesJob] to fire next at [Wed Dec 04 04:47:11 EST 2013] and repeat every [300000] milliseconds >04:46:11,750 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.PurgePluginsJob:org.rhq.enterprise.server.scheduler.jobs.PurgePluginsJob] to fire next at [Wed Dec 04 04:47:11 EST 2013] and repeat every [300000] milliseconds >04:46:11,784 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.DynaGroupAutoRecalculationJob:org.rhq.enterprise.server.scheduler.jobs.DynaGroupAutoRecalculationJob] to fire next at [Wed Dec 04 04:47:11 EST 2013] and repeat every [60000] milliseconds >04:46:11,822 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.CloudManagerJob:org.rhq.enterprise.server.scheduler.jobs.CloudManagerJob] to fire next at [Wed Dec 04 04:48:11 EST 2013] and repeat every [30000] milliseconds >04:46:11,862 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.CheckForSuspectedAgentsJob:org.rhq.enterprise.server.scheduler.jobs.CheckForSuspectedAgentsJob] to fire next at [Wed Dec 04 04:56:11 EST 2013] and repeat every [60000] milliseconds >04:46:11,904 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutOperationsJob:org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutOperationsJob] to fire next at [Wed Dec 04 04:49:11 EST 2013] and repeat every [600000] milliseconds >04:46:11,944 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutConfigUpdatesJob:org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutConfigUpdatesJob] to fire next at [Wed Dec 04 04:50:11 EST 2013] and repeat every [600000] milliseconds >04:46:11,974 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled job [org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutContentRequestsJob:org.rhq.enterprise.server.scheduler.jobs.CheckForTimedOutContentRequestsJob] to fire next at [Wed Dec 04 04:51:11 EST 2013] and repeat every [900000] milliseconds >04:46:12,019 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled cron job [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob:org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] to fire next at [Wed Dec 04 05:00:00 EST 2013] with the cron string [0 0 * * * ?]. >04:46:12,108 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled cron job [380816c0--d225257a:syncContentSource] to fire next at [Wed Jan 01 00:00:00 EST 2014] with the cron string [0 0 0 1 * ?]. >04:46:12,174 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled cron job [4c1228d:syncRepo] to fire next at [Sun Dec 08 01:00:00 EST 2013] with the cron string [0 0 1 ? * 1]. >04:46:12,250 INFO [org.rhq.enterprise.server.plugin.pc.MasterServerPluginContainer] (pool-9-thread-1) Master server plugin container scheduled all jobs >04:46:12,270 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (pool-9-thread-1) note: volatile jobs are effectively non-volatile in a clustered environment. >04:46:12,272 INFO [org.quartz.impl.jdbcjobstore.JobStoreCMT] (pool-9-thread-1) note: volatile triggers are effectively non-volatile in a clustered environment. >04:46:12,277 INFO [org.rhq.enterprise.server.scheduler.EnhancedSchedulerImpl] (pool-9-thread-1) Scheduled cron job [org.rhq.enterprise.server.scheduler.jobs.StorageClusterReadRepairJob:org.rhq.enterprise.server.scheduler.jobs.StorageClusterReadRepairJob] to fire next at [Sun Dec 08 00:30:00 EST 2013] with the cron string [0 30 0 ? * SUN *]. >04:46:12,314 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) Creating timer to begin scanning for plugins... >04:46:12,332 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) -------------------------------------------------- >04:46:12,333 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) JBoss Operations Network 3.2.0.CR1 (build 6ecd678:d0dc0b6) Server started. >04:46:12,333 INFO [org.rhq.enterprise.server.core.StartupBean] (pool-9-thread-1) -------------------------------------------------- >04:46:49,700 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-remoting-servlet-invoker]] (http-/0.0.0.0:7080-1) ServerInvokerServlet: invokerObjectNameQuery=jboss.remoting:service=invoker,rhq.communications.connector.rhqtype=server,* >04:46:49,701 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-remoting-servlet-invoker]] (http-/0.0.0.0:7080-1) ServerInvokerServlet: Found RHQ remoting servlet: jboss.remoting:service=invoker,transport=servlet,host=joner7.bc.jonqe.lab.eng.bos.redhat.com,port=7080,rhq.communications.connector.rhqtype=server >04:46:49,827 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-1) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.security-token=YX1LS1HB7AmGun3BGCoCwZnBm1a1mxCsmd2TQp1s5Ra+t8pbWACcJoFPHOWuUEOPLrY=, rhq.externalizable-strategy=AGENT}]; params=[{invocation=NameBasedInvocation[connectAgent], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:46:51,107 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-1) Got agent registration request for new agent: joner7.bc.jonqe.lab.eng.bos.redhat.com[10.16.23.61:16163][4.9.0.JON320CR1(d0dc0b6)] >04:46:51,178 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-2) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:46:53,199 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-2) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:46:55,230 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-2) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:46:57,247 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-2) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:46:59,259 WARN [org.rhq.enterprise.communications.command.server.CommandProcessor] (http-/0.0.0.0:7080-2) {CommandProcessor.failed-authentication}Command failed to be authenticated! This command will be ignored and not processed: Command: type=[remotepojo]; cmd-in-response=[false]; config=[{rhq.agent-name=joner7.bc.jonqe.lab.eng.bos.redhat.com, rhq.externalizable-strategy=AGENT, rhq.send-throttle=true}]; params=[{invocation=NameBasedInvocation[getLatestPlugins], targetInterfaceName=org.rhq.core.clientapi.server.core.CoreServerService}] >04:47:00,952 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-4) Agent [joner7.bc.jonqe.lab.eng.bos.redhat.com][4.9.0.JON320CR1(d0dc0b6)] would like to connect to this server >04:47:01,176 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-4) Agent [joner7.bc.jonqe.lab.eng.bos.redhat.com] has connected to this server at Wed Dec 04 04:47:01 EST 2013 >04:47:23,944 INFO [org.rhq.enterprise.server.cloud.StorageNodeManagerBean] (http-/0.0.0.0:7080-4) Linking Resource[id=10113, uuid=dc14266a-eea4-4053-920b-a94eb59cd732, type={RHQStorage}RHQ Storage Node, key=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), name=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), parent=joner7.bc.jonqe.lab.eng.bos.redhat.com, version=4.9.0.JON320CR1] to storage node at joner7.bc.jonqe.lab.eng.bos.redhat.com >04:47:24,023 INFO [org.rhq.enterprise.server.cloud.StorageNodeManagerBean] (http-/0.0.0.0:7080-4) Did not find storage node with address [joner7.bc.jonqe.lab.eng.bos.redhat.com] Searching by IP address [10.16.23.61] >04:47:24,046 INFO [org.rhq.enterprise.server.cloud.StorageNodeManagerBean] (http-/0.0.0.0:7080-4) Scheduling cluster maintenance to deploy StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=INSTALLED, mtime=1386150444044] into the storage cluster... >04:47:24,047 INFO [org.rhq.enterprise.server.cloud.StorageNodeManagerBean] (http-/0.0.0.0:7080-4) Deploying StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=INSTALLED, mtime=1386150444044] >04:47:24,088 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (http-/0.0.0.0:7080-4) Announcing StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=ANNOUNCE, mtime=1386150444044] to storage node cluster. >04:47:24,103 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (http-/0.0.0.0:7080-4) Announcing StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=ANNOUNCE, mtime=1386150444044] to cluster node StorageNode[id=1001, address=joner7-ha-master.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=NORMAL, mtime=1386149798748] >04:47:41,689 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 10) joner7.bc.jonqe.lab.eng.bos.redhat.com took [94]ms to reload global cache >04:47:41,993 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 10) joner7.bc.jonqe.lab.eng.bos.redhat.com took [124]ms to reload cache for 1 agents >04:47:54,991 INFO [com.datastax.driver.core.Cluster] (Scheduled Tasks-0) New Cassandra host /10.16.23.61 added >04:47:55,019 INFO [org.rhq.server.metrics.StorageSession] (Scheduled Tasks-0) /10.16.23.61 added >04:47:55,023 INFO [org.rhq.server.metrics.StorageSession] (Scheduled Tasks-0) Storage cluster is up >04:47:55,023 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Scheduled Tasks-0) Storage cluster is up >04:47:55,023 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Scheduled Tasks-0) Storage node at 10.16.23.61 is up >04:47:55,139 INFO [org.rhq.server.metrics.StorageSession] (Cassandra Java Driver worker-1) /10.16.23.61 is down >04:47:55,139 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Cassandra Java Driver worker-1) Storage node at 10.16.23.61 is down >04:48:11,692 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [85]ms to reload global cache >04:48:11,813 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [93]ms to reload cache for 1 agents >04:48:20,102 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (EJB default - 8) The prepare for bootstrap operation completed successfully for StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=BOOTSTRAP, mtime=1386150444044] >04:48:22,375 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (EJB default - 8) Running addNodeMaintenance for storage node StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=ADD_MAINTENANCE, mtime=1386150444044] >04:48:59,690 INFO [org.rhq.server.metrics.StorageSession] (Reconnection-0) /10.16.23.61 is up >04:48:59,691 INFO [org.rhq.enterprise.server.storage.StorageClusterMonitor] (Reconnection-0) Storage node at 10.16.23.61 is up >04:51:56,293 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (EJB default - 8) Finished running add node maintenance for StorageNode[id=10001, address=joner7.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=ADD_MAINTENANCE, mtime=1386150444044] >04:51:56,309 INFO [org.rhq.enterprise.server.storage.StorageNodeOperationsHandlerBean] (EJB default - 8) Running addNodeMaintenance for storage node StorageNode[id=1001, address=joner7-ha-master.bc.jonqe.lab.eng.bos.redhat.com, cqlPort=9142, operationMode=NORMAL, mtime=1386149798748] >04:52:47,072 WARN [com.datastax.driver.core.Connection] (New I/O worker #5) Timeout while setting keyspace on connection to /10.16.23.61. This should not happen but is not critical (it will retried) >04:54:47,069 WARN [com.datastax.driver.core.Connection] (New I/O worker #5) Timeout while setting keyspace on connection to /10.16.23.61. This should not happen but is not critical (it will retried) >04:55:47,063 WARN [com.datastax.driver.core.Connection] (New I/O worker #5) Timeout while setting keyspace on connection to /10.16.23.61. This should not happen but is not critical (it will retried) >05:00:00,130 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Data Purge Job STARTING >05:00:00,139 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Measurement data compression starting at Wed Dec 04 05:00:00 EST 2013 >05:00:08,039 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-2) Finished computing aggregates for table [raw_metrics]7884 ms >05:00:09,728 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-2) Finished computing aggregates for table [one_hour_metrics] 0 ms >05:00:09,729 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-2) Finished computing aggregates for table [six_hour_metrics] 0 ms >05:00:09,729 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Measurement data compression completed in [9591]ms >05:00:09,730 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Measurement calltime data purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,746 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging calltime data that is older than Sun Nov 03 05:00:09 EST 2013 >05:00:09,762 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Calltime purged [0] - completed in [31]ms >05:00:09,763 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Event data purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,763 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging event data older than Wed Nov 20 05:00:09 EST 2013 >05:00:09,800 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Event data purged [0] - completed in [36]ms >05:00:09,800 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert data purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,801 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging alert data older than Sun Nov 03 05:00:09 EST 2013 >05:00:09,830 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert data purged [0] - completed in [30]ms >05:00:09,830 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert definition unused purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,844 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert definitions purged [0] - completed in [13]ms >05:00:09,844 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert condition orphan purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,858 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purged [0] orphan alert conditions - completed in [14]ms >05:00:09,859 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Alert notification orphan purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,875 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purged [0] orphan alert notifications - completed in [16]ms >05:00:09,875 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Trait data purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,876 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging traits that are older than Tue Dec 04 05:00:09 EST 2012 >05:00:09,888 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Traits data purged [0] - completed in [13]ms >05:00:09,891 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Availability data purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,892 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging availablities that are older than Tue Dec 04 05:00:09 EST 2012 >05:00:09,923 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Availability data purged [0] - completed in [34]ms >05:00:09,924 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Drift file orphan purge starting at Wed Dec 04 05:00:09 EST 2013 >05:00:09,928 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purging orphaned drift files older than Sun Nov 03 05:00:09 EST 2013 >05:00:09,992 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Purged [0] orphaned drift files - completed in [68]ms >05:00:09,993 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Database maintenance starting at Wed Dec 04 05:00:09 EST 2013 >05:00:10,003 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Performing hourly database maintenance >05:00:11,940 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Database maintenance completed in [1947]ms >05:00:11,941 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Auto-calculation of baselines starting at Wed Dec 04 05:00:11 EST 2013 >05:00:11,969 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-2) Calculating auto baselines >05:00:11,969 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-2) Deleting baselines computations older than Sun Dec 01 05:00:11 EST 2013 >05:00:11,970 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-2) Inserting new baselines using last 7 days of 1H data >05:00:11,976 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-2) Removed [0] old baselines - they will now be recalculated (6)ms >05:00:22,893 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-2) Calculated and inserted [1648] new baselines. (10917)ms >05:00:22,941 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Auto-calculation of baselines completed in [11000]ms >05:00:22,942 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Auto-calculation of OOBs starting >05:00:22,954 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-2) Removed [0] outdated OOBs >05:00:22,981 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-2) Computing OOBs >05:00:27,752 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-2) Finished calculating 0 OOBs in 4770 ms >05:00:27,753 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Auto-calculation of OOBs completed in [4811]ms >05:00:27,753 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-2) Data Purge Job FINISHED [27624]ms >05:00:41,674 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [87]ms to reload cache for 1 agents >06:00:00,023 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Data Purge Job STARTING >06:00:00,035 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Measurement data compression starting at Wed Dec 04 06:00:00 EST 2013 >06:00:04,371 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-4) Finished computing aggregates for table [raw_metrics]4335 ms >06:00:09,300 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-4) Finished computing aggregates for table [one_hour_metrics] 3851 ms >06:00:10,277 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-4) Finished computing aggregates for table [six_hour_metrics] 0 ms >06:00:10,277 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Measurement data compression completed in [10242]ms >06:00:10,278 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Measurement calltime data purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,278 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging calltime data that is older than Sun Nov 03 06:00:10 EST 2013 >06:00:10,282 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Calltime purged [0] - completed in [4]ms >06:00:10,283 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Event data purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,283 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging event data older than Wed Nov 20 06:00:10 EST 2013 >06:00:10,288 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Event data purged [0] - completed in [5]ms >06:00:10,289 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert data purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,289 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging alert data older than Sun Nov 03 06:00:10 EST 2013 >06:00:10,299 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert data purged [0] - completed in [10]ms >06:00:10,299 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert definition unused purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,305 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert definitions purged [0] - completed in [6]ms >06:00:10,305 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert condition orphan purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,309 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purged [0] orphan alert conditions - completed in [4]ms >06:00:10,309 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Alert notification orphan purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,312 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purged [0] orphan alert notifications - completed in [3]ms >06:00:10,313 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Trait data purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,313 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging traits that are older than Tue Dec 04 06:00:10 EST 2012 >06:00:10,317 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Traits data purged [0] - completed in [4]ms >06:00:10,317 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Availability data purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,318 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging availablities that are older than Tue Dec 04 06:00:10 EST 2012 >06:00:10,323 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Availability data purged [0] - completed in [6]ms >06:00:10,324 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Drift file orphan purge starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,324 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purging orphaned drift files older than Sun Nov 03 06:00:10 EST 2013 >06:00:10,340 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Purged [0] orphaned drift files - completed in [16]ms >06:00:10,341 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Database maintenance starting at Wed Dec 04 06:00:10 EST 2013 >06:00:10,341 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Performing hourly database maintenance >06:00:13,024 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Database maintenance completed in [2683]ms >06:00:13,025 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Auto-calculation of baselines starting at Wed Dec 04 06:00:13 EST 2013 >06:00:13,036 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-4) Calculating auto baselines >06:00:13,041 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-4) Deleting baselines computations older than Sun Dec 01 06:00:13 EST 2013 >06:00:13,041 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-4) Inserting new baselines using last 7 days of 1H data >06:00:13,050 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-4) Removed [0] old baselines - they will now be recalculated (9)ms >06:00:14,573 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-4) Calculated and inserted [435] new baselines. (1523)ms >06:00:14,606 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Auto-calculation of baselines completed in [1581]ms >06:00:14,606 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Auto-calculation of OOBs starting >06:00:14,611 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-4) Removed [0] outdated OOBs >06:00:14,633 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-4) Computing OOBs >06:00:19,703 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-4) Finished calculating 11 OOBs in 5070 ms >06:00:19,703 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Auto-calculation of OOBs completed in [5097]ms >06:00:19,703 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-4) Data Purge Job FINISHED [19680]ms >06:00:41,697 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 1) joner7.bc.jonqe.lab.eng.bos.redhat.com took [88]ms to reload cache for 1 agents >07:00:11,779 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 4) joner7.bc.jonqe.lab.eng.bos.redhat.com took [147]ms to reload cache for 1 agents >08:00:00,052 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Data Purge Job STARTING >08:00:00,059 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Measurement data compression starting at Wed Dec 04 08:00:00 EST 2013 >08:00:03,866 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-3) Finished computing aggregates for table [raw_metrics]3807 ms >08:00:04,735 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-3) Finished computing aggregates for table [one_hour_metrics] 0 ms >08:00:04,736 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-3) Finished computing aggregates for table [six_hour_metrics] 0 ms >08:00:04,736 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Measurement data compression completed in [4677]ms >08:00:04,737 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Measurement calltime data purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,737 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging calltime data that is older than Sun Nov 03 08:00:04 EST 2013 >08:00:04,741 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Calltime purged [0] - completed in [4]ms >08:00:04,741 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Event data purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,741 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging event data older than Wed Nov 20 08:00:04 EST 2013 >08:00:04,745 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Event data purged [0] - completed in [4]ms >08:00:04,745 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert data purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,745 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging alert data older than Sun Nov 03 08:00:04 EST 2013 >08:00:04,753 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert data purged [0] - completed in [8]ms >08:00:04,754 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert definition unused purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,758 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert definitions purged [0] - completed in [4]ms >08:00:04,758 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert condition orphan purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,761 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purged [0] orphan alert conditions - completed in [3]ms >08:00:04,762 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Alert notification orphan purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,765 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purged [0] orphan alert notifications - completed in [3]ms >08:00:04,766 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Trait data purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,766 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging traits that are older than Tue Dec 04 08:00:04 EST 2012 >08:00:04,769 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Traits data purged [0] - completed in [3]ms >08:00:04,770 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Availability data purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,770 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging availablities that are older than Tue Dec 04 08:00:04 EST 2012 >08:00:04,774 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Availability data purged [0] - completed in [4]ms >08:00:04,774 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Drift file orphan purge starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,775 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purging orphaned drift files older than Sun Nov 03 08:00:04 EST 2013 >08:00:04,789 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Purged [0] orphaned drift files - completed in [15]ms >08:00:04,790 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Database maintenance starting at Wed Dec 04 08:00:04 EST 2013 >08:00:04,790 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Performing hourly database maintenance >08:00:07,230 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Database maintenance completed in [2440]ms >08:00:07,231 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Auto-calculation of baselines starting at Wed Dec 04 08:00:07 EST 2013 >08:00:07,238 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-3) Calculating auto baselines >08:00:07,238 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-3) Deleting baselines computations older than Sun Dec 01 08:00:07 EST 2013 >08:00:07,238 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-3) Inserting new baselines using last 7 days of 1H data >08:00:07,243 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-3) Removed [0] old baselines - they will now be recalculated (4)ms >08:00:07,589 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-3) Calculated and inserted [276] new baselines. (345)ms >08:00:07,640 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Auto-calculation of baselines completed in [409]ms >08:00:07,640 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Auto-calculation of OOBs starting >08:00:07,645 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-3) Removed [0] outdated OOBs >08:00:07,888 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-3) Computing OOBs >08:00:11,794 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 8) joner7.bc.jonqe.lab.eng.bos.redhat.com took [137]ms to reload cache for 1 agents >08:00:13,585 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-3) Finished calculating 42 OOBs in 5697 ms >08:00:13,586 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Auto-calculation of OOBs completed in [5946]ms >08:00:13,586 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-3) Data Purge Job FINISHED [13534]ms >08:11:12,326 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (EJB default - 5) Found agent plugin in the DB that we do not yet have: JBossAS7 >08:11:13,445 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 5) Discovered agent plugin [JBossAS7] >08:13:11,681 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [90]ms to reload cache for 1 agents >08:13:43,828 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: RHQServer >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: JBossAS5 >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: JBossCache3 >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: JBossAS >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: JBossCache >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: HornetQ >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: Hibernate >08:13:43,830 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: Augeas >08:13:43,831 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginScanner] (http-/0.0.0.0:7080-2) Found agent plugin in the DB that we do not yet have: Apache >08:14:04,736 INFO [org.rhq.enterprise.server.discovery.DiscoveryBossBean] (http-/0.0.0.0:7080-2) Resource [Resource[id=10113, uuid=dc14266a-eea4-4053-920b-a94eb59cd732, type={RHQStorage}RHQ Storage Node, key=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), name=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), parent=joner7.bc.jonqe.lab.eng.bos.redhat.com, version=4.9.0.JON320CR1]] upgraded itsto become [Resource[id=10113, uuid=dc14266a-eea4-4053-920b-a94eb59cd732, type={RHQStorage}RHQ Storage Node, key=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), name=RHQ Storage Node(joner7.bc.jonqe.lab.eng.bos.redhat.com), parent=joner7.bc.jonqe.lab.eng.bos.redhat.com, version=4.9.0.JON320CR1]] >08:16:14,453 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [JBossAS7] >08:16:14,454 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [JBossAS7] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:14,595 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [RHQServer] >08:16:15,021 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [JBossAS5] >08:16:15,303 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [JBossCache3] >08:16:15,462 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [JBossAS] >08:16:15,596 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [JBossCache] >08:16:15,742 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [HornetQ] >08:16:15,878 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [Hibernate] >08:16:16,053 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [Augeas] >08:16:16,316 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Discovered agent plugin [Apache] >08:16:16,615 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [Augeas] >08:16:16,615 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [Augeas] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:16,751 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [HornetQ] >08:16:16,751 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [HornetQ] plugin found (version 2.0.0.Final) - older version (2.0.0.Final) will be ignored. >08:16:16,900 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [JBossAS] >08:16:16,901 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [JBossAS] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:17,028 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [JBossCache] >08:16:17,028 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [JBossCache] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:17,159 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [RHQServer] >08:16:17,159 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [RHQServer] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:17,505 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [JBossAS5] >08:16:17,523 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [JBossAS5] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:17,795 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [Hibernate] >08:16:17,795 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [Hibernate] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:17,923 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [JBossCache3] >08:16:17,924 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [JBossCache3] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:16:18,091 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Rediscovered agent plugin [Apache] >08:16:18,091 INFO [org.rhq.enterprise.server.core.plugin.ProductPluginDeployer] (EJB default - 7) Newer version of [Apache] plugin found (version 4.9.0.JON320CR1) - older version (4.9.0.JON320CR1) will be ignored. >08:26:41,740 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [103]ms to reload cache for 1 agents >08:27:20,168 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 1) joner7.bc.jonqe.lab.eng.bos.redhat.com took [120]ms to reload cache for 1 agents >08:27:20,678 INFO [org.rhq.enterprise.server.util.concurrent.InventoryReportSerializer] (http-/0.0.0.0:7080-3) tid=362; agent=joner7.bc.jonqe.lab.eng.bos.redhat.com: releasing write lock after being locked for millis=11219 >08:27:55,610 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 8) joner7.bc.jonqe.lab.eng.bos.redhat.com took [190]ms to reload cache for 1 agents >08:28:10,478 WARN [org.rhq.enterprise.server.discovery.DiscoveryServerServiceImpl] (http-/0.0.0.0:7080-3) Performance: inventory merge (34034)ms >08:28:10,479 INFO [org.rhq.enterprise.server.util.concurrent.InventoryReportSerializer] (http-/0.0.0.0:7080-3) tid=362; agent=joner7.bc.jonqe.lab.eng.bos.redhat.com: releasing write lock after being locked for millis=34035 >08:28:12,278 INFO [org.rhq.enterprise.server.util.concurrent.AvailabilityReportSerializer] (http-/0.0.0.0:7080-1) tid=329; agent=joner7.bc.jonqe.lab.eng.bos.redhat.com: releasing write lock after being locked for millis=13313 >08:28:41,789 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 1) joner7.bc.jonqe.lab.eng.bos.redhat.com took [197]ms to reload cache for 1 agents >08:32:11,662 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 10) joner7.bc.jonqe.lab.eng.bos.redhat.com took [75]ms to reload global cache >08:36:41,661 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 1) joner7.bc.jonqe.lab.eng.bos.redhat.com took [67]ms to reload global cache >08:37:11,641 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 8) joner7.bc.jonqe.lab.eng.bos.redhat.com took [48]ms to reload global cache >08:43:03,770 INFO [org.rhq.enterprise.server.core.AgentManagerBean] (http-/0.0.0.0:7080-1) Agent with name [joner7.bc.jonqe.lab.eng.bos.redhat.com] just went down >08:43:09,865 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-1) Agent [joner7.bc.jonqe.lab.eng.bos.redhat.com][4.9.0.JON320CR1(d0dc0b6)] would like to connect to this server >08:43:10,073 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-1) Agent [joner7.bc.jonqe.lab.eng.bos.redhat.com] has connected to this server at Wed Dec 04 08:43:10 EST 2013 >08:43:11,292 INFO [org.rhq.enterprise.server.core.CoreServerServiceImpl] (http-/0.0.0.0:7080-1) Got agent registration request for existing agent: joner7.bc.jonqe.lab.eng.bos.redhat.com[10.16.23.61:16163][4.9.0.JON320CR1(d0dc0b6)] - Will not regenerate a new token >08:44:26,328 INFO [org.rhq.enterprise.server.util.concurrent.AvailabilityReportSerializer] (http-/0.0.0.0:7080-3) tid=362; agent=joner7.bc.jonqe.lab.eng.bos.redhat.com: releasing write lock after being locked for millis=8616 >08:46:41,939 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 3) joner7.bc.jonqe.lab.eng.bos.redhat.com took [327]ms to reload cache for 1 agents >08:48:11,720 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 10) joner7.bc.jonqe.lab.eng.bos.redhat.com took [120]ms to reload cache for 1 agents >08:48:41,700 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 6) joner7.bc.jonqe.lab.eng.bos.redhat.com took [87]ms to reload cache for 1 agents >08:49:11,679 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 8) joner7.bc.jonqe.lab.eng.bos.redhat.com took [86]ms to reload cache for 1 agents >08:49:41,681 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 1) joner7.bc.jonqe.lab.eng.bos.redhat.com took [82]ms to reload cache for 1 agents >08:51:11,752 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 6) joner7.bc.jonqe.lab.eng.bos.redhat.com took [144]ms to reload global cache >08:51:11,873 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 6) joner7.bc.jonqe.lab.eng.bos.redhat.com took [89]ms to reload cache for 1 agents >09:00:41,720 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 3) joner7.bc.jonqe.lab.eng.bos.redhat.com took [107]ms to reload cache for 1 agents >09:01:41,646 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 3) joner7.bc.jonqe.lab.eng.bos.redhat.com took [57]ms to reload global cache >09:01:41,747 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 3) joner7.bc.jonqe.lab.eng.bos.redhat.com took [74]ms to reload cache for 1 agents >09:01:43,075 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (Thread-94) joner7.bc.jonqe.lab.eng.bos.redhat.com took [65]ms to reload global cache >09:01:43,182 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (Thread-94) joner7.bc.jonqe.lab.eng.bos.redhat.com took [80]ms to reload cache for 1 agents >10:00:00,040 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Data Purge Job STARTING >10:00:00,155 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Measurement data compression starting at Wed Dec 04 10:00:00 EST 2013 >10:00:17,325 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-5) Finished computing aggregates for table [raw_metrics]17135 ms >10:00:21,487 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-5) Finished computing aggregates for table [one_hour_metrics] 0 ms >10:00:21,487 INFO [org.rhq.server.metrics.MetricsServer] (RHQScheduler_Worker-5) Finished computing aggregates for table [six_hour_metrics] 0 ms >10:00:21,489 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Measurement data compression completed in [21333]ms >10:00:22,008 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Measurement calltime data purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,008 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging calltime data that is older than Sun Nov 03 10:00:22 EST 2013 >10:00:22,050 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Calltime purged [0] - completed in [42]ms >10:00:22,129 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Event data purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,129 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging event data older than Wed Nov 20 10:00:22 EST 2013 >10:00:22,141 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Event data purged [0] - completed in [12]ms >10:00:22,150 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert data purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,150 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging alert data older than Sun Nov 03 10:00:22 EST 2013 >10:00:22,355 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert data purged [0] - completed in [205]ms >10:00:22,367 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert definition unused purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,403 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert definitions purged [0] - completed in [36]ms >10:00:22,404 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert condition orphan purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,409 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purged [0] orphan alert conditions - completed in [5]ms >10:00:22,422 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Alert notification orphan purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,446 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purged [0] orphan alert notifications - completed in [24]ms >10:00:22,447 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Trait data purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,447 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging traits that are older than Tue Dec 04 10:00:22 EST 2012 >10:00:22,451 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Traits data purged [0] - completed in [4]ms >10:00:22,458 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Availability data purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,459 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging availablities that are older than Tue Dec 04 10:00:22 EST 2012 >10:00:22,557 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Availability data purged [0] - completed in [99]ms >10:00:22,558 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Drift file orphan purge starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,558 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purging orphaned drift files older than Sun Nov 03 10:00:22 EST 2013 >10:00:22,687 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Purged [0] orphaned drift files - completed in [129]ms >10:00:22,687 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Database maintenance starting at Wed Dec 04 10:00:22 EST 2013 >10:00:22,687 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Performing hourly database maintenance >10:00:26,611 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Database maintenance completed in [3924]ms >10:00:26,651 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Auto-calculation of baselines starting at Wed Dec 04 10:00:26 EST 2013 >10:00:26,672 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-5) Calculating auto baselines >10:00:26,673 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-5) Deleting baselines computations older than Sun Dec 01 10:00:26 EST 2013 >10:00:26,673 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-5) Inserting new baselines using last 7 days of 1H data >10:00:26,731 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-5) Removed [0] old baselines - they will now be recalculated (58)ms >10:00:50,303 INFO [org.rhq.enterprise.server.measurement.MeasurementBaselineManagerBean] (RHQScheduler_Worker-5) Calculated and inserted [5821] new baselines. (23572)ms >10:00:50,338 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Auto-calculation of baselines completed in [23687]ms >10:00:50,338 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Auto-calculation of OOBs starting >10:00:50,390 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-5) Removed [0] outdated OOBs >10:00:50,426 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-5) Computing OOBs >10:01:09,582 INFO [org.rhq.enterprise.server.measurement.MeasurementOOBManagerBean] (RHQScheduler_Worker-5) Finished calculating 73 OOBs in 19156 ms >10:01:09,582 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Auto-calculation of OOBs completed in [19244]ms >10:01:09,582 INFO [org.rhq.enterprise.server.scheduler.jobs.DataPurgeJob] (RHQScheduler_Worker-5) Data Purge Job FINISHED [69542]ms >10:01:11,686 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 7) joner7.bc.jonqe.lab.eng.bos.redhat.com took [85]ms to reload cache for 1 agents >10:29:28,172 INFO [org.rhq.enterprise.server.alert.engine.jms.AlertConditionConsumerBean] (Thread-126) AlertCondition[id=10071] has been removed after it was triggered; this message will be discarded >10:29:41,636 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [52]ms to reload global cache >10:29:41,733 INFO [org.rhq.enterprise.server.cloud.instance.CacheConsistencyManagerBean] (EJB default - 2) joner7.bc.jonqe.lab.eng.bos.redhat.com took [75]ms to reload cache for 1 agents
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1038202
:
832709
|
832710
|
832712
|
832713
| 832714