12:01:22,759 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1 12:01:22,932 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 12:01:23,013 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss BPM Suite 6.0.2.GA (AS 7.2.1.Final-redhat-10) starting 12:01:23,019 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties: [Standalone] = awt.toolkit = sun.awt.X11.XToolkit file.encoding = UTF-8 file.encoding.pkg = sun.io file.separator = / java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment java.awt.headless = true java.awt.printerjob = sun.print.PSPrinterJob java.class.path = /home/ibek/jboss/bpms603er1/jboss-modules.jar java.class.version = 51.0 java.endorsed.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/endorsed java.ext.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre java.io.tmpdir = /tmp java.library.path = /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.7.0_55-mockbuild_2014_04_16_06_38-b00 java.specification.name = Java Platform API Specification java.specification.vendor = Oracle Corporation java.specification.version = 1.7 java.util.logging.manager = org.jboss.logmanager.LogManager java.vendor = Oracle Corporation java.vendor.url = http://java.oracle.com/ java.vendor.url.bug = http://bugreport.sun.com/bugreport/ java.version = 1.7.0_55 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 = Oracle Corporation java.vm.specification.version = 1.7 java.vm.vendor = Oracle Corporation java.vm.version = 24.51-b03 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.home.dir = /home/ibek/jboss/bpms603er1 jboss.host.name = dhcp-4-149 jboss.modules.dir = /home/ibek/jboss/bpms603er1/modules jboss.modules.system.pkgs = org.jboss.byteman jboss.node.name = dhcp-4-149 jboss.qualified.host.name = dhcp-4-149.brq.redhat.com jboss.server.base.dir = /home/ibek/jboss/bpms603er1/standalone jboss.server.config.dir = /home/ibek/jboss/bpms603er1/standalone/configuration jboss.server.data.dir = /home/ibek/jboss/bpms603er1/standalone/data jboss.server.deploy.dir = /home/ibek/jboss/bpms603er1/standalone/data/content jboss.server.log.dir = /home/ibek/jboss/bpms603er1/standalone/log jboss.server.name = dhcp-4-149 jboss.server.persist.config = true jboss.server.temp.dir = /home/ibek/jboss/bpms603er1/standalone/tmp line.separator = logging.configuration = file:/home/ibek/jboss/bpms603er1/standalone/configuration/logging.properties module.path = /home/ibek/jboss/bpms603er1/modules org.jboss.boot.log.file = /home/ibek/jboss/bpms603er1/standalone/log/server.log org.jboss.resolver.warning = true org.xml.sax.driver = __redirected.__XMLReaderFactory os.arch = amd64 os.name = Linux os.version = 3.13.11-100.fc19.x86_64 path.separator = : sun.arch.data.model = 64 sun.boot.class.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/netx.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/plugin.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/classes sun.boot.library.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc19.x86_64/jre/lib/amd64 sun.cpu.endian = little sun.cpu.isalist = sun.desktop = gnome sun.io.unicode.encoding = UnicodeLittle sun.java.command = /home/ibek/jboss/bpms603er1/jboss-modules.jar -mp /home/ibek/jboss/bpms603er1/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=/home/ibek/jboss/bpms603er1 -Djboss.server.base.dir=/home/ibek/jboss/bpms603er1/standalone sun.java.launcher = SUN_STANDARD sun.jnu.encoding = UTF-8 sun.management.compiler = HotSpot 64-Bit Tiered Compilers sun.os.patch.level = unknown user.country = US user.dir = /home/ibek/jboss/bpms603er1/bin user.home = /home/ibek user.language = en user.name = ibek user.timezone = Europe/Prague 12:01:23,021 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -D[Standalone] -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/ibek/jboss/bpms603er1/standalone/log/server.log -Dlogging.configuration=file:/home/ibek/jboss/bpms603er1/standalone/configuration/logging.properties 12:01:23,886 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found dashbuilder.war in deployment directory. To trigger deployment create a file called dashbuilder.war.dodeploy 12:01:23,886 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found business-central.war in deployment directory. To trigger deployment create a file called business-central.war.dodeploy 12:01:23,902 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.7.GA-redhat-1 12:01:23,905 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 12:01:23,907 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.7.GA-redhat-1 12:01:23,913 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.16.GA-redhat-1 12:01:24,033 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010280: Activating Infinispan subsystem. 12:01:24,059 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem 12:01:24,060 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012605: Activated the following JSF Implementations: [main, 1.2] 12:01:24,064 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem 12:01:24,084 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2) 12:01:24,104 INFO [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.17.SP2-redhat-2 12:01:24,135 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 47) JBAS015537: Activating WebServices Extension 12:01:24,147 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service 12:01:24,150 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default] 12:01:24,259 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 12:01:24,403 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 12:01:24,542 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080 12:01:24,549 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080 12:01:24,579 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/ibek/jboss/bpms603er1/standalone/data/messagingjournal,bindingsDirectory=/home/ibek/jboss/bpms603er1/standalone/data/messagingbindings,largeMessagesDirectory=/home/ibek/jboss/bpms603er1/standalone/data/messaginglargemessages,pagingDirectory=/home/ibek/jboss/bpms603er1/standalone/data/messagingpaging) 12:01:24,585 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221006: Waiting to obtain live lock 12:01:24,618 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221013: Using NIO Journal 12:01:24,713 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /home/ibek/jboss/bpms603er1/standalone/deployments 12:01:24,720 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "dashbuilder.war" (runtime-name: "dashbuilder.war") 12:01:24,720 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "business-central.war" (runtime-name: "business-central.war") 12:01:24,755 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:4447 12:01:24,756 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 127.0.0.1:9999 12:01:24,836 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221034: Waiting to obtain live lock 12:01:24,836 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221035: Live Server Obtained live lock 12:01:25,086 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 12:01:25,901 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice. 12:01:25,902 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice. 12:01:25,902 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. 12:01:25,903 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. 12:01:25,903 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice. 12:01:25,904 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice. 12:01:25,904 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice. 12:01:25,905 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice. 12:01:25,917 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.dashbuilder.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. 12:01:25,917 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.dashbuilder.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. 12:01:25,918 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice. 12:01:25,918 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.dashbuilder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice. 12:01:25,919 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.dashbuilder.war" is using an unsupported module ("org.jdom:main") which may be changed or removed in future versions without notice. 12:01:25,919 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.dashbuilder.war" is using an unsupported module ("org.jdom:main") which may be changed or removed in future versions without notice. 12:01:26,028 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment dashbuilder.war 12:01:26,151 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 127.0.0.1:5455 for CORE protocol 12:01:26,174 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221020: Started Netty Acceptor version 3.6.6.Final-redhat-1-fd3c6b7 127.0.0.1:5445 for CORE protocol 12:01:26,185 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221007: Server is now live 12:01:26,185 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221001: HornetQ Server version 2.3.5.Final-redhat-2 (Monster Bee, 123) [f02adfe5-2d07-11e4-9518-8f6f55d2038b] 12:01:26,226 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 12:01:26,229 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory 12:01:26,294 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: dashbuilder.war 12:01:26,297 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/JmsXA 12:01:26,366 INFO [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started 12:01:26,367 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra 12:01:26,369 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 12:01:26,376 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.13 (redhat) 12:01:26,489 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment dashbuilder.war 12:01:26,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry xalan-2.7.1.redhat-7.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry serializer-2.7.1.redhat-7.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry xercesImpl-2.9.1-redhat-4.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry xml-apis-1.3.04.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry commons-lang-2.6-redhat-2.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry commons-io-2.1-redhat-2.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,557 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015960: Class Path entry log4j-1.2.16-redhat-2.jar in /home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/jbpmmigration-0.13-redhat-5.jar does not point to a valid jar for a Class-Path reference. 12:01:26,832 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for org.jbpm.domain 12:01:27,131 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("com.google.guava:main") which may be changed or removed in future versions without notice. 12:01:27,131 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("com.google.guava:main") which may be changed or removed in future versions without notice. 12:01:27,132 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("com.h2database.h2:main") which may be changed or removed in future versions without notice. 12:01:27,132 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("com.h2database.h2:main") which may be changed or removed in future versions without notice. 12:01:27,132 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice. 12:01:27,133 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("com.sun.xml.bind:main") which may be changed or removed in future versions without notice. 12:01:27,133 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice. 12:01:27,134 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.antlr:main") which may be changed or removed in future versions without notice. 12:01:27,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.cli:main") which may be changed or removed in future versions without notice. 12:01:27,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.cli:main") which may be changed or removed in future versions without notice. 12:01:27,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice. 12:01:27,135 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice. 12:01:27,136 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. 12:01:27,136 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice. 12:01:27,137 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice. 12:01:27,138 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice. 12:01:27,138 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice. 12:01:27,138 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice. 12:01:27,145 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice. 12:01:27,146 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.cxf.impl:main") which may be changed or removed in future versions without notice. 12:01:27,147 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 12:01:27,147 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.httpcomponents:main") which may be changed or removed in future versions without notice. 12:01:27,147 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.james.mime4j:main") which may be changed or removed in future versions without notice. 12:01:27,147 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.james.mime4j:main") which may be changed or removed in future versions without notice. 12:01:27,148 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.neethi:main") which may be changed or removed in future versions without notice. 12:01:27,148 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.neethi:main") which may be changed or removed in future versions without notice. 12:01:27,149 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.velocity:main") which may be changed or removed in future versions without notice. 12:01:27,149 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.velocity:main") which may be changed or removed in future versions without notice. 12:01:27,149 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.xml-resolver:main") which may be changed or removed in future versions without notice. 12:01:27,150 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.apache.xml-resolver:main") which may be changed or removed in future versions without notice. 12:01:27,150 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 12:01:27,150 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-core-asl:main") which may be changed or removed in future versions without notice. 12:01:27,151 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-jaxrs:main") which may be changed or removed in future versions without notice. 12:01:27,151 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-jaxrs:main") which may be changed or removed in future versions without notice. 12:01:27,151 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 12:01:27,152 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main") which may be changed or removed in future versions without notice. 12:01:27,152 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-xc:main") which may be changed or removed in future versions without notice. 12:01:27,152 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jackson.jackson-xc:main") which may be changed or removed in future versions without notice. 12:01:27,153 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. 12:01:27,153 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.jettison:main") which may be changed or removed in future versions without notice. 12:01:27,153 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.woodstox:main") which may be changed or removed in future versions without notice. 12:01:27,153 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.codehaus.woodstox:main") which may be changed or removed in future versions without notice. 12:01:27,154 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. 12:01:27,154 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice. 12:01:27,155 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice. 12:01:27,156 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.javassist:main") which may be changed or removed in future versions without notice. 12:01:27,156 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice. 12:01:27,156 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.jboss.as.web:main") which may be changed or removed in future versions without notice. 12:01:27,157 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice. 12:01:27,158 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) JBAS018567: Deployment "deployment.business-central.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice. 12:01:27,161 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.jdom:main") which may be changed or removed in future versions without notice. 12:01:27,161 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.jdom:main") which may be changed or removed in future versions without notice. 12:01:27,161 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.jgroups:main") which may be changed or removed in future versions without notice. 12:01:27,161 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.jgroups:main") which may be changed or removed in future versions without notice. 12:01:27,163 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice. 12:01:27,164 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice. 12:01:27,176 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.yaml.snakeyaml:main") which may be changed or removed in future versions without notice. 12:01:27,177 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-5) JBAS018568: Deployment "deployment.business-central.war" is using an unsupported module ("org.yaml.snakeyaml:main") which may be changed or removed in future versions without notice. 12:01:27,593 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment business-central.war 12:01:27,733 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named SimpleAsyncExecutorService in deployment unit deployment "business-central.war" are as follows: java:global/business-central/SimpleAsyncExecutorService!org.uberfire.commons.async.SimpleAsyncExecutorService java:app/business-central/SimpleAsyncExecutorService!org.uberfire.commons.async.SimpleAsyncExecutorService java:module/SimpleAsyncExecutorService!org.uberfire.commons.async.SimpleAsyncExecutorService java:global/business-central/SimpleAsyncExecutorService java:app/business-central/SimpleAsyncExecutorService java:module/SimpleAsyncExecutorService 12:01:27,734 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ConfigServiceWatchServiceExecutorImpl in deployment unit deployment "business-central.war" are as follows: java:global/business-central/ConfigServiceWatchServiceExecutorImpl!org.uberfire.backend.server.config.watch.ConfigServiceWatchServiceExecutor java:app/business-central/ConfigServiceWatchServiceExecutorImpl!org.uberfire.backend.server.config.watch.ConfigServiceWatchServiceExecutor java:module/ConfigServiceWatchServiceExecutorImpl!org.uberfire.backend.server.config.watch.ConfigServiceWatchServiceExecutor java:global/business-central/ConfigServiceWatchServiceExecutorImpl java:app/business-central/ConfigServiceWatchServiceExecutorImpl java:module/ConfigServiceWatchServiceExecutorImpl 12:01:27,734 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named WebSphereRoleProviderServices in deployment unit deployment "business-central.war" are as follows: java:global/business-central/WebSphereRoleProviderServices!org.uberfire.security.server.auth.source.adapter.WebSphereRoleProviderServices java:app/business-central/WebSphereRoleProviderServices!org.uberfire.security.server.auth.source.adapter.WebSphereRoleProviderServices java:module/WebSphereRoleProviderServices!org.uberfire.security.server.auth.source.adapter.WebSphereRoleProviderServices java:global/business-central/WebSphereRoleProviderServices java:app/business-central/WebSphereRoleProviderServices java:module/WebSphereRoleProviderServices 12:01:27,735 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named IOWatchServiceExecutorImpl in deployment unit deployment "business-central.war" are as follows: java:global/business-central/IOWatchServiceExecutorImpl!org.uberfire.backend.server.io.watch.IOWatchServiceExecutor java:app/business-central/IOWatchServiceExecutorImpl!org.uberfire.backend.server.io.watch.IOWatchServiceExecutor java:module/IOWatchServiceExecutorImpl!org.uberfire.backend.server.io.watch.IOWatchServiceExecutor java:global/business-central/IOWatchServiceExecutorImpl java:app/business-central/IOWatchServiceExecutorImpl java:module/IOWatchServiceExecutorImpl 12:01:27,735 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RetryTrackerSingleton in deployment unit deployment "business-central.war" are as follows: java:global/business-central/RetryTrackerSingleton!org.kie.remote.services.jms.RetryTrackerSingleton java:app/business-central/RetryTrackerSingleton!org.kie.remote.services.jms.RetryTrackerSingleton java:module/RetryTrackerSingleton!org.kie.remote.services.jms.RetryTrackerSingleton java:global/business-central/RetryTrackerSingleton java:app/business-central/RetryTrackerSingleton java:module/RetryTrackerSingleton 12:01:27,735 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named IncrementalBuilderExecutorManager in deployment unit deployment "business-central.war" are as follows: java:global/business-central/IncrementalBuilderExecutorManager!org.guvnor.common.services.builder.IncrementalBuilderExecutorManager java:app/business-central/IncrementalBuilderExecutorManager!org.guvnor.common.services.builder.IncrementalBuilderExecutorManager java:module/IncrementalBuilderExecutorManager!org.guvnor.common.services.builder.IncrementalBuilderExecutorManager java:global/business-central/IncrementalBuilderExecutorManager java:app/business-central/IncrementalBuilderExecutorManager java:module/IncrementalBuilderExecutorManager 12:01:27,736 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named MailboxProcessOutgoingExecutorManager in deployment unit deployment "business-central.war" are as follows: java:global/business-central/MailboxProcessOutgoingExecutorManager!org.guvnor.inbox.backend.server.MailboxProcessOutgoingExecutorManager java:app/business-central/MailboxProcessOutgoingExecutorManager!org.guvnor.inbox.backend.server.MailboxProcessOutgoingExecutorManager java:module/MailboxProcessOutgoingExecutorManager!org.guvnor.inbox.backend.server.MailboxProcessOutgoingExecutorManager java:global/business-central/MailboxProcessOutgoingExecutorManager java:app/business-central/MailboxProcessOutgoingExecutorManager java:module/MailboxProcessOutgoingExecutorManager 12:01:28,021 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: business-central.war 12:01:28,094 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 51) HQ221003: trying to deploy queue jms.queue.KIE.AUDIT 12:01:28,097 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011402: Starting Persistence Unit Service 'business-central.war#org.jbpm.domain' 12:01:28,098 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016008: Starting weld service for deployment business-central.war 12:01:28,215 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) JBAS014142: Started message driven bean 'KieSessionRequesMessageBean' with 'hornetq-ra' resource adapter 12:01:28,218 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'TaskServiceRequesMessageBean' with 'hornetq-ra' resource adapter 12:01:28,234 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'JMSAuditProcessor' with 'hornetq-ra' resource adapter 12:01:28,286 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/KIE.AUDIT 12:01:28,287 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:/queue/KIE.AUDIT.ALL 12:01:28,288 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 53) HQ221003: trying to deploy queue jms.queue.KIE.TASK 12:01:28,289 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/KIE.TASK 12:01:28,290 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:/queue/KIE.TASK.ALL 12:01:28,290 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 52) HQ221003: trying to deploy queue jms.queue.KIE.RESPONSE 12:01:28,292 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/KIE.RESPONSE 12:01:28,300 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:/queue/KIE.RESPONSE.ALL 12:01:28,301 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221003: trying to deploy queue jms.queue.KIE.SESSION 12:01:28,302 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/KIE.SESSION 12:01:28,303 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/queue/KIE.SESSION.ALL 12:01:28,408 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons Annotations {4.0.1.Final-redhat-2} 12:01:28,417 INFO [org.hibernate.Version] (ServerService Thread Pool -- 50) HHH000412: Hibernate Core {4.2.0.SP1-redhat-1} 12:01:28,419 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000206: hibernate.properties not found 12:01:28,431 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000021: Bytecode provider name : javassist 12:01:28,462 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [ name: org.jbpm.domain ...] 12:01:30,062 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 12:01:30,480 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect 12:01:30,638 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory 12:01:30,671 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory 12:01:30,687 INFO [org.jboss.web] (ServerService Thread Pool -- 56) JBAS018210: Register web context: /dashbuilder 12:01:30,757 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 50) HV000001: Hibernate Validator 4.3.1.Final-redhat-1 12:01:30,892 INFO [org.jboss.dashboard.ui.controller.ControllerServlet] (ServerService Thread Pool -- 56) Application Directory: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/. 12:01:30,893 INFO [org.jboss.dashboard.ui.controller.ControllerServlet] (ServerService Thread Pool -- 56) Application Config Directory: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc 12:01:30,942 INFO [org.jboss.dashboard.factory.Factory] (ServerService Thread Pool -- 56) Configuring Factory from directory: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/factory 12:01:31,022 INFO [org.jboss.dashboard.factory.Factory] (ServerService Thread Pool -- 56) Factory configured. 12:01:31,244 INFO [org.hibernate.cfg.Configuration] (ServerService Thread Pool -- 56) HHH000042: Configuring from file: hibernate.cfg.xml 12:01:31,260 INFO [org.hibernate.cfg.Configuration] (ServerService Thread Pool -- 56) HHH000041: Configured SessionFactory: null 12:01:31,262 INFO [org.jboss.dashboard.database.hibernate.HibernateInitializer] (ServerService Thread Pool -- 56) The underlying database is: h2 12:01:31,509 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 50) HHH000228: Running hbm2ddl schema update 12:01:31,510 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 50) HHH000102: Fetching database metadata 12:01:31,522 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 50) HHH000396: Updating schema 12:01:31,527 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Attachment 12:01:31,529 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: BAMTaskSummary 12:01:31,531 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: BooleanExpression 12:01:31,533 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Content 12:01:31,535 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ContextMappingInfo 12:01:31,536 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: CorrelationKeyInfo 12:01:31,541 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: CorrelationPropertyInfo 12:01:31,543 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Deadline 12:01:31,545 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Delegation_delegates 12:01:31,547 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ErrorInfo 12:01:31,550 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Escalation 12:01:31,551 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: EventTypes 12:01:31,553 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: I18NText 12:01:31,555 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: NodeInstanceLog 12:01:31,557 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification 12:01:31,559 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_BAs 12:01:31,561 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_Recipients 12:01:31,563 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_email_header 12:01:31,565 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: OrganizationalEntity 12:01:31,566 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_BAs 12:01:31,569 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_ExclOwners 12:01:31,573 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_PotOwners 12:01:31,575 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_Recipients 12:01:31,577 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_Stakeholders 12:01:31,579 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ProcessInstanceInfo 12:01:31,581 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ProcessInstanceLog 12:01:31,583 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Reassignment 12:01:31,585 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Reassignment_potentialOwners 12:01:31,588 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: RequestInfo 12:01:31,590 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: SessionInfo 12:01:31,592 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Task 12:01:31,594 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: TaskDef 12:01:31,596 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: TaskEvent 12:01:31,600 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: VariableInstanceLog 12:01:31,606 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: WorkItemInfo 12:01:31,609 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: email_header 12:01:31,611 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: task_comment 12:01:31,613 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Attachment 12:01:31,615 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: BAMTaskSummary 12:01:31,619 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: BooleanExpression 12:01:31,621 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Content 12:01:31,623 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ContextMappingInfo 12:01:31,626 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: CorrelationKeyInfo 12:01:31,629 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: CorrelationPropertyInfo 12:01:31,631 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Deadline 12:01:31,638 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Delegation_delegates 12:01:31,642 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ErrorInfo 12:01:31,645 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Escalation 12:01:31,647 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: EventTypes 12:01:31,653 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: I18NText 12:01:31,656 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: NodeInstanceLog 12:01:31,658 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification 12:01:31,662 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_BAs 12:01:31,669 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_Recipients 12:01:31,671 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Notification_email_header 12:01:31,673 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: OrganizationalEntity 12:01:31,676 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_BAs 12:01:31,678 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_ExclOwners 12:01:31,680 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_PotOwners 12:01:31,683 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_Recipients 12:01:31,686 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: PeopleAssignments_Stakeholders 12:01:31,688 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ProcessInstanceInfo 12:01:31,691 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: ProcessInstanceLog 12:01:31,694 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Reassignment 12:01:31,699 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Reassignment_potentialOwners 12:01:31,702 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: RequestInfo 12:01:31,704 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: SessionInfo 12:01:31,707 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: Task 12:01:31,709 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: TaskDef 12:01:31,712 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: TaskEvent 12:01:31,714 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: VariableInstanceLog 12:01:31,717 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: WorkItemInfo 12:01:31,720 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: email_header 12:01:31,723 INFO [java.sql.DatabaseMetaData] (ServerService Thread Pool -- 50) HHH000262: Table not found: task_comment 12:01:32,016 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 56) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect 12:01:32,017 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 56) HHH000431: Unable to determine H2 database version, certain features may not work 12:01:32,027 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 56) HHH000399: Using default transaction strategy (direct JDBC transactions) 12:01:32,029 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 56) HHH000397: Using ASTQueryTranslatorFactory 12:01:32,044 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 50) HHH000232: Schema update complete 12:01:32,410 WARN [org.jboss.dashboard.database.DatabaseAutoSynchronizer] (ServerService Thread Pool -- 56) Running file 1-create-h2.sql 12:01:32,607 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Starting org.jboss.dashboard.workspace.SkinsManagerImpl 12:01:32,615 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Skin /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/skins/Default_Skin.zip 12:01:32,739 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Skin Default_Skin 12:01:32,752 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Starting org.jboss.dashboard.workspace.EnvelopesManagerImpl 12:01:32,757 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Envelope /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/envelopes/jbpmEnvelope.zip 12:01:32,767 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Envelope /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/envelopes/Default_Envelope.zip 12:01:32,779 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Envelope Default_Envelope 12:01:32,784 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Envelope jbpmEnvelope 12:01:32,800 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Loading panels. Scanning dir: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/WEB-INF/etc/panels 12:01:32,801 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/dashboard/kpi/dashb_kpi.panel 12:01:32,823 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/dashboard/dataProviderManager/dashb_providermgr.panel 12:01:32,825 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/dashboard/htmlEditor/dashb_html_editor.panel 12:01:32,828 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/dashboard/dashboardFilter/dashb_filter.panel 12:01:32,831 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/system/dashboardImport/dashb_import.panel 12:01:32,833 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/system/dataSourceManagement/DataSourceManager.panel 12:01:32,835 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/system/workspaceExport/workspaceImportexport.panel 12:01:32,838 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/system/dashboardExport/dashb_export.panel 12:01:32,840 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_language_horiz.panel 12:01:32,843 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_sections_horiz.panel 12:01:32,844 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_workspace_vert.panel 12:01:32,845 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/tree/treeMenu.panel 12:01:32,847 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/logout/logout.panel 12:01:32,848 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_sections.panel 12:01:32,850 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_workspace.panel 12:01:32,852 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_workspace_horiz.panel 12:01:32,855 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/breadCrumb/breadCrumb.panel 12:01:32,857 INFO [org.jboss.dashboard.workspace.PanelsProvidersManagerImpl] (ServerService Thread Pool -- 56) Reading file: /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/panels/navigation/navigator_sections_vert.panel 12:01:33,038 INFO [org.jboss.dashboard.cluster.ClusterNodesManager] (ServerService Thread Pool -- 56) Registering cluster node with ip address 10.40.3.177 12:01:33,048 INFO [org.jboss.dashboard.cluster.ClusterNodesManager] (ServerService Thread Pool -- 56) Successfully registered cluster node with ip address 10.40.3.177 and identifier 1003 12:01:33,048 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Starting org.jboss.dashboard.workspace.LayoutsManagerImpl 12:01:33,053 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/Default_template_with_sliding_menu.zip 12:01:33,086 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/Template_75-25.zip 12:01:33,095 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/jbpmLayout.zip 12:01:33,105 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/Template_25-75.zip 12:01:33,117 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/Template_25-50-25.zip 12:01:33,127 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Deploying to database Layout /home/ibek/jboss/bpms603er1/standalone/deployments/dashbuilder.war/./WEB-INF/etc/layouts/Default_Layout.zip 12:01:33,140 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout Default_Layout 12:01:33,142 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout Default_template_with_sliding_menu 12:01:33,144 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout Template_25-50-25 12:01:33,145 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout Template_25-75 12:01:33,147 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout Template_75-25 12:01:33,148 INFO [org.jboss.dashboard.ui.resources.GraphicElement] (ServerService Thread Pool -- 56) Deploying files for org.jboss.dashboard.ui.resources.Layout jbpmLayout 12:01:33,277 INFO [org.jboss.dashboard.workspace.GraphicElementManagerImpl] (ServerService Thread Pool -- 56) Starting org.jboss.dashboard.workspace.ResourceGalleryManagerImpl 12:01:33,304 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) Parsing KPI's XML file: WEB-INF/etc/appdata/initialData/jbpmKPIs.xml 12:01:35,764 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Solder Config XML provider starting... 12:01:35,767 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Loading XmlDocumentProvider: org.jboss.solder.config.xml.bootstrap.ResourceLoaderXmlDocumentProvider 12:01:35,801 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Reading XML file: vfs:/home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/uberfire-security-server-0.3.3-redhat-5.jar/META-INF/beans.xml 12:01:35,808 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Reading XML file: jar:file:/home/ibek/jboss/bpms603er1/modules/system/layers/bpms/org/jbpm/main/jbpm-kie-services-6.0.3-redhat-5.jar!/META-INF/beans.xml 12:01:35,810 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Reading XML file: vfs:/home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/uberfire-api-0.3.3-redhat-5.jar/META-INF/beans.xml 12:01:35,812 INFO [org.jboss.solder.config.xml.bootstrap.XmlConfigExtension] (MSC service thread 1-2) Reading XML file: vfs:/home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar/META-INF/beans.xml 12:01:35,814 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) starting errai cdi ... 12:01:35,831 INFO [org.jboss.solder.Version] (MSC service thread 1-2) Solder 3.2.1.Final (build id: 3.2.1.Final) 12:01:35,942 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.enums.backend.server.EnumServiceImpl 12:01:35,951 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00000 - Data provider created. dataprovider_30861353511610610, jBPM Count Processes. 12:01:35,951 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00000 - Data provider created. dataprovider_29781353670809093, jBPM Process Summary. 12:01:35,951 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00000 - Data provider created. dataprovider_31171353947281370, jBPM Task Summary. 12:01:35,951 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_29741354189063608, Tasks completed by date. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30361353506582146, Tasks by status. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30531353942661507, Process instances by status. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_21261373392004451, Process initiated by date. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_29671354183712341, Process duration. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30751353944093386, Process completed by date. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_21351361956566198, Number of tasks per user. 12:01:35,952 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_31261353948417434, Number of task instances. 12:01:35,953 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30571353683160264, Instances started by user. 12:01:35,953 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_31331353949095782, Instances by status. 12:01:35,953 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_29771353670707848, Instances by process. 12:01:35,953 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_31361353949675344, By version. 12:01:35,953 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_29711354187660609, Tasks duration. 12:01:35,954 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_31201353947556129, Tasks started by date. 12:01:35,954 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_31291353948572804, Users with tasks. 12:01:36,035 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.globals.backend.server.GlobalsEditorServiceImpl 12:01:36,225 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.m2repo.backend.server.M2RepoServiceImpl 12:01:36,237 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.scorecardxls.backend.server.ScoreCardXLSServiceImpl 12:01:36,259 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.es.backend.server.ExecutorServiceEntryPointImpl 12:01:36,307 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.builder.BuildServiceImpl 12:01:36,520 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.screens.projecteditor.backend.server.ProjectScreenServiceImpl 12:01:36,611 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.services.datamodel.backend.server.IncrementalDataModelServiceImpl 12:01:36,676 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.guided.template.server.GuidedRuleTemplateEditorServiceImpl 12:01:36,707 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.drltext.backend.server.DRLTextEditorServiceImpl 12:01:36,766 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.screens.explorer.backend.server.ExplorerServiceImpl 12:01:38,173 INFO [org.jboss.errai.common.metadata.MetaDataScanner] (Thread-76) added class scanning extensions: org.jboss.errai.common.metadata.JbossVFsTypeHandler 12:01:40,642 INFO [org.jboss.errai.reflections.Reflections] (Thread-76) Reflections took 2466 ms to scan 92 urls, producing 2665 keys and 16431 values [using 2 cores] 12:01:40,654 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) Parsing KPI's XML file: WEB-INF/etc/appdata/initialData/showcaseKPIs.xml 12:01:43,398 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.testscenario.backend.server.ScenarioTestEditorServiceImpl 12:01:43,418 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.screens.datamodeller.backend.server.DataModelerServiceImpl 12:01:43,850 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.dashboard.renderer.service.impl.DashboardRendererServiceImpl 12:01:43,860 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.screens.search.backend.server.SearchServiceImpl 12:01:44,300 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.project.backend.server.ProjectServiceImpl 12:01:44,303 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.project.backend.server.KModuleServiceImpl 12:01:44,313 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.project.backend.server.POMServiceImpl 12:01:44,341 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.guided.dtable.backend.server.GuidedDecisionTableEditorServiceImpl 12:01:44,382 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.screens.defaulteditor.backend.server.DefaultEditorServiceImpl 12:01:44,396 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.workitems.backend.server.WorkItemsEditorServiceImpl 12:01:44,417 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.services.backend.source.SourceServicesImpl 12:01:44,428 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.services.backend.rulename.RuleNameServiceImpl 12:01:44,432 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.services.backend.security.KieWorkbenchSecurityServiceImpl 12:01:44,437 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.kie.workbench.common.services.backend.validation.ValidationServiceImpl 12:01:45,052 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00000 - Data provider created. dataprovider_63791223772073037, Expense reports demo. 12:01:45,053 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00000 - Data provider created. dataprovider_29881353499006573, Sales dashboard demo. 12:01:45,053 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_64011223773089901, Expense evolution. 12:01:45,053 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30301353506280659, Expected pipeline. 12:01:45,054 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30361353506582145, By status. 12:01:45,054 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30651353683614640, By sales person. 12:01:45,054 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30331353506453066, By sales person. 12:01:45,055 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30831353686700387, By product. 12:01:45,055 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30391353506887646, By product. 12:01:45,056 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30801353685378049, By customer. 12:01:45,056 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30281353675541472, By country. 12:01:45,056 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_21591363786594721, Amount by status. 12:01:45,056 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30861353687605533, Amount by probability (%). 12:01:45,057 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30771353684719633, - New indicator -. 12:01:45,057 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_64061223773274641, Expense reports table. 12:01:45,058 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_63931223772633377, Expenses by department USD. 12:01:45,058 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_63901223772516707, Expenses by office USD. 12:01:45,058 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30461354643057084, Expenses by user. 12:01:45,059 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30441353507392054, Opportunities by closing date (USD). 12:01:45,059 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30101353505177974, Opportunities by country. 12:01:45,059 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30041353504912610, Opportunities by employee. 12:01:45,060 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30011353503663716, Opportunities by status. 12:01:45,060 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30251353675275870, Pipeline status. 12:01:45,060 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_30621353683547916, Sales evolution. 12:01:45,060 INFO [org.jboss.dashboard.kpi.KPIInitialModule] (ServerService Thread Pool -- 56) BAM_00001 - Business indicator created. kpi_29761353668431694, Sales report table. 12:01:45,124 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.designer.server.service.DefaultDesignerAssetService 12:01:45,280 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.inbox.backend.server.InboxServiceImpl 12:01:45,468 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.backend.config.ResourceConfigServiceImpl 12:01:45,477 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.backend.version.VersionServiceImpl 12:01:45,492 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service class org.guvnor.common.services.backend.file.RenameServiceImpl 12:01:45,498 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.backend.metadata.MetadataServiceImpl 12:01:45,504 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service class org.guvnor.common.services.backend.file.CopyServiceImpl 12:01:45,506 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.backend.config.AppConfigServiceImpl 12:01:45,515 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service class org.guvnor.common.services.backend.file.DeleteServiceImpl 12:01:45,531 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.guvnor.common.services.backend.metadata.CategoryServiceImpl 12:01:45,681 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.dsltext.backend.server.DSLTextEditorServiceImpl 12:01:45,772 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.bd.backend.server.DataServiceEntryPointImpl 12:01:45,775 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.bd.backend.server.KieSessionEntryPointImpl 12:01:45,796 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl 12:01:45,812 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.guided.scorecard.backend.server.GuidedScoreCardEditorServiceImpl 12:01:45,824 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.formModeler.panels.modeler.backend.FormModelerServiceImpl 12:01:45,978 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.WorkbenchServicesImpl 12:01:45,989 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.VFSServicesServerImpl 12:01:46,001 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.plugin.RuntimePluginsServiceServerImpl 12:01:46,003 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.repositories.RepositoryServiceEditorImpl 12:01:46,014 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.FileNavigatorServiceImpl 12:01:46,040 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.organizationalunit.OrganizationalUnitServiceImpl 12:01:46,043 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.uberfire.backend.server.repositories.RepositoryServiceImpl 12:01:46,110 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.guided.rule.backend.server.GuidedRuleEditorServiceImpl 12:01:46,120 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.guided.rule.backend.server.EnumDropdownServiceImpl 12:01:46,233 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @SessionScoped class org.jbpm.formModeler.renderer.backend.service.FormRenderingServiceImpl 12:01:46,236 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.formModeler.renderer.backend.service.FormRendererIncluderServiceImpl 12:01:46,254 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.ht.backend.server.FormModelerProcessStarterEntryPointImpl 12:01:46,257 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.ht.backend.server.TypeRoleServiceEntryPointImpl 12:01:46,263 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.ht.backend.server.TaskServiceEntryPointImpl 12:01:46,270 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.ht.backend.server.FormServiceEntryPointImpl 12:01:46,273 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.jbpm.console.ng.ht.backend.server.UserServiceEntryPointImpl 12:01:46,328 INFO [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-2) discovered errai service: public@Service @ApplicationScoped class org.drools.workbench.screens.dtablexls.backend.server.DecisionTableXLSServiceImpl 12:01:46,738 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-2) Found kmodule: vfs:/home/ibek/jboss/bpms603er1/standalone/deployments/business-central.war/WEB-INF/lib/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar/META-INF/kmodule.xml 12:01:46,740 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-2) Virtual file physical path = /home/ibek/jboss/bpms603er1/standalone/tmp/vfs/deployment3dfc29313c1e6a38/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar-749be8814da91be3/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar 12:01:46,792 INFO [org.drools.compiler.kie.builder.impl.KieRepositoryImpl] (MSC service thread 1-2) KieModule was added:ZipKieModule[ ReleaseId=org.drools:drools-wb-rest-defaultapprover:6.0.3-redhat-5file=/home/ibek/jboss/bpms603er1/standalone/tmp/vfs/deployment3dfc29313c1e6a38/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar-749be8814da91be3/drools-wb-rest-defaultapprover-6.0.3-redhat-5.jar] 12:01:48,592 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.SessionScoped() used on injection point [field] @Inject @SessionScoped private org.kie.workbench.common.screens.explorer.backend.server.ExplorerServiceImpl.identity 12:01:48,593 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.SessionScoped() used on injection point [field] @Inject @SessionScoped private org.kie.workbench.common.screens.explorer.backend.server.ExplorerServiceImpl.sessionInfo 12:01:48,681 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.RequestScoped() used on injection point [field] @Inject @RequestScoped private org.jbpm.designer.repository.vfs.VFSRepository.descriptor 12:01:48,695 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.SessionScoped() used on injection point [field] @Inject @SessionScoped private org.guvnor.inbox.backend.server.InboxServiceImpl.identity 12:01:48,729 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.RequestScoped() used on injection point [field] @Inject @Named @RequestScoped private org.jbpm.console.ng.bd.backend.server.DeploymentManagerEntryPointImpl.deploymentUnits 12:01:48,763 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-2) WELD-001440 Scope type @javax.enterprise.context.SessionScoped() used on injection point [field] @Inject @SessionScoped private org.uberfire.backend.server.UserServicesImpl.identity 12:01:48,913 INFO [org.apache.sshd.common.util.SecurityUtils] (MSC service thread 1-2) BouncyCastle not registered, using the default JCE provider 12:01:49,927 INFO [org.guvnor.m2repo.backend.server.GuvnorM2Repository] (MSC service thread 1-2) Maven Repository root set to: repositories/kie 12:01:49,927 INFO [org.guvnor.m2repo.backend.server.GuvnorM2Repository] (MSC service thread 1-2) Creating Maven Repository root: repositories/kie 12:01:49,934 WARN [org.kie.scanner.embedder.MavenSettings] (MSC service thread 1-2) Environment variable M2_HOME is not set 12:01:50,043 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'type' to 'kjar'. 12:01:50,043 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'drools.dateformat' to 'dd-MMM-yyyy'. 12:01:50,043 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'drools.defaultlanguage' to 'en'. 12:01:50,043 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'rule-modeller-onlyShowDSLStatements' to 'false'. 12:01:50,044 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'designer.context' to 'designer'. 12:01:50,044 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'drools.defaultcountry' to 'US'. 12:01:50,044 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'drools.datetimeformat' to 'dd-MMM-yyyy hh:mm:ss'. 12:01:50,044 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'build.enable-incremental' to 'true'. 12:01:50,044 INFO [org.guvnor.common.services.backend.config.ApplicationPreferencesLoader] (MSC service thread 1-2) Setting preference 'designer.profile' to 'jbpm'. 12:01:50,061 INFO [org.jbpm.executor.impl.ExecutorImpl] (MSC service thread 1-2) Starting Executor Component ... - Thread Pool Size: 1 - Interval: 3 Seconds - Retries per Request: 3 12:01:50,109 INFO [org.kie.remote.services.jms.RetryTrackerSingleton] (ServerService Thread Pool -- 53) JMS message retry limit set to 2 12:01:50,124 INFO [org.jboss.web] (ServerService Thread Pool -- 54) JBAS018210: Register web context: /business-central 12:01:50,329 INFO [solder-servlet] (ServerService Thread Pool -- 54) Catch Integration for Servlets enabled 12:01:50,431 INFO [org.guvnor.common.services.builder.ResourceChangeIncrementalBuilder] (Thread-81) Batch incremental build request received. 12:01:50,590 INFO [org.jboss.errai.bus.server.cluster.noop.NoopClusteringProvider] (ServerService Thread Pool -- 54) clustering support not configured. 12:01:50,604 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (ServerService Thread Pool -- 54) starting errai bus ... 12:01:50,606 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (ServerService Thread Pool -- 54) authentication adapter configured: org.jboss.errai.bus.server.security.auth.JAASAdapter 12:01:50,616 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (ServerService Thread Pool -- 54) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher 12:01:50,628 INFO [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (ServerService Thread Pool -- 54) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider 12:01:50,654 INFO [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (ServerService Thread Pool -- 54) searching for errai extensions ... 12:01:50,688 INFO [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (ServerService Thread Pool -- 54) errai bus started. 12:01:50,821 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "business-central.war" (runtime-name : "business-central.war") 12:01:50,822 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) JBAS018559: Deployed "dashbuilder.war" (runtime-name : "dashbuilder.war") 12:01:51,107 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 12:01:51,107 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 12:01:51,107 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss BPM Suite 6.0.2.GA (AS 7.2.1.Final-redhat-10) started in 28652ms - Started 668 of 738 services (69 services are passive or on-demand) 13:06:52,796 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,797 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8e63cf-2d07-11e4-9518-8f6f55d2038b 13:06:52,800 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8e63cf-2d07-11e4-9518-8f6f55d2038b 13:06:52,816 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,816 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff917119-2d07-11e4-9518-8f6f55d2038b 13:06:52,817 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff917119-2d07-11e4-9518-8f6f55d2038b 13:06:52,817 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,816 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:52,817 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8cdd27-2d07-11e4-9518-8f6f55d2038b 13:06:52,835 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:52,833 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8cdd27-2d07-11e4-9518-8f6f55d2038b 13:06:52,905 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,906 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff91e64f-2d07-11e4-9518-8f6f55d2038b 13:06:52,908 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff91e64f-2d07-11e4-9518-8f6f55d2038b 13:06:52,909 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,909 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8aba38-2d07-11e4-9518-8f6f55d2038b 13:06:52,910 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8aba38-2d07-11e4-9518-8f6f55d2038b 13:06:52,910 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,910 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8ae14b-2d07-11e4-9518-8f6f55d2038b 13:06:52,914 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8ae14b-2d07-11e4-9518-8f6f55d2038b 13:06:52,914 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,915 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff9540be-2d07-11e4-9518-8f6f55d2038b 13:06:52,934 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff9540be-2d07-11e4-9518-8f6f55d2038b 13:06:52,935 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,935 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff94cb8b-2d07-11e4-9518-8f6f55d2038b 13:06:52,939 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff94cb8b-2d07-11e4-9518-8f6f55d2038b 13:06:52,941 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,942 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff9344e5-2d07-11e4-9518-8f6f55d2038b 13:06:52,943 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff9344e5-2d07-11e4-9518-8f6f55d2038b 13:06:52,950 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,950 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff853bef-2d07-11e4-9518-8f6f55d2038b 13:06:52,951 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff853bef-2d07-11e4-9518-8f6f55d2038b 13:06:52,977 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,978 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8bcbb1-2d07-11e4-9518-8f6f55d2038b 13:06:52,978 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8bcbb1-2d07-11e4-9518-8f6f55d2038b 13:06:52,984 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,984 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8ba49e-2d07-11e4-9518-8f6f55d2038b 13:06:52,985 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8ba49e-2d07-11e4-9518-8f6f55d2038b 13:06:52,986 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,986 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff781c7d-2d07-11e4-9518-8f6f55d2038b 13:06:52,987 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff781c7d-2d07-11e4-9518-8f6f55d2038b 13:06:52,987 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:52,989 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff905fa3-2d07-11e4-9518-8f6f55d2038b 13:06:52,999 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff905fa3-2d07-11e4-9518-8f6f55d2038b 13:06:53,003 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,004 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff786a9f-2d07-11e4-9518-8f6f55d2038b 13:06:53,005 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff786a9f-2d07-11e4-9518-8f6f55d2038b 13:06:53,005 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,006 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff6e3167-2d07-11e4-9518-8f6f55d2038b 13:06:53,007 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff6e3167-2d07-11e4-9518-8f6f55d2038b 13:06:53,025 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,025 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff80f62c-2d07-11e4-9518-8f6f55d2038b 13:06:53,026 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff80f62c-2d07-11e4-9518-8f6f55d2038b 13:06:53,030 ERROR [org.hornetq.core.server] (Thread-5 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,030 ERROR [org.hornetq.core.server] (Thread-7 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,033 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,033 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff80cf1b-2d07-11e4-9518-8f6f55d2038b 13:06:53,033 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,033 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff80cf1b-2d07-11e4-9518-8f6f55d2038b 13:06:53,034 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,035 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff7cb065-2d07-11e4-9518-8f6f55d2038b 13:06:53,035 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff7cb065-2d07-11e4-9518-8f6f55d2038b 13:06:53,036 ERROR [org.hornetq.core.server] (Thread-6 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,040 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,040 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff7c6243-2d07-11e4-9518-8f6f55d2038b 13:06:53,040 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff7c6243-2d07-11e4-9518-8f6f55d2038b 13:06:53,040 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,041 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8a4504-2d07-11e4-9518-8f6f55d2038b 13:06:53,041 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8a4504-2d07-11e4-9518-8f6f55d2038b 13:06:53,041 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,041 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff6e5878-2d07-11e4-9518-8f6f55d2038b 13:06:53,041 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff6e5878-2d07-11e4-9518-8f6f55d2038b 13:06:53,044 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,044 ERROR [org.hornetq.core.server] (Thread-11 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,045 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff89a8c2-2d07-11e4-9518-8f6f55d2038b 13:06:53,044 ERROR [org.hornetq.core.server] (Thread-7 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,045 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff89a8c2-2d07-11e4-9518-8f6f55d2038b 13:06:53,046 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,046 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff9086b5-2d07-11e4-9518-8f6f55d2038b 13:06:53,046 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff9086b5-2d07-11e4-9518-8f6f55d2038b 13:06:53,046 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,047 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8e15ad-2d07-11e4-9518-8f6f55d2038b 13:06:53,048 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8e15ad-2d07-11e4-9518-8f6f55d2038b 13:06:53,048 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,049 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff6f90f9-2d07-11e4-9518-8f6f55d2038b 13:06:53,052 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff6f90f9-2d07-11e4-9518-8f6f55d2038b 13:06:53,053 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,053 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8d796a-2d07-11e4-9518-8f6f55d2038b 13:06:53,054 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8d796a-2d07-11e4-9518-8f6f55d2038b 13:06:53,054 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,054 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff925a81-2d07-11e4-9518-8f6f55d2038b 13:06:53,046 ERROR [org.hornetq.core.server] (Thread-12 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,054 ERROR [org.hornetq.core.server] (Thread-11 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,058 ERROR [org.hornetq.core.server] (Thread-10 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,056 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,056 ERROR [org.hornetq.core.server] (Thread-12 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,067 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,069 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff925a81-2d07-11e4-9518-8f6f55d2038b 13:06:53,056 ERROR [org.hornetq.core.server] (Thread-9 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,068 ERROR [org.hornetq.core.server] (Thread-8 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,066 ERROR [org.hornetq.core.server] (Thread-11 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,072 ERROR [org.hornetq.core.server] (Thread-10 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,071 ERROR [org.hornetq.core.server] (Thread-6 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.AUDIT] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,071 ERROR [org.hornetq.core.server] (Thread-13 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,077 ERROR [org.hornetq.core.server] (Thread-15 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,070 ERROR [org.hornetq.core.server] (Thread-12 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,069 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,070 ERROR [org.hornetq.core.server] (Thread-7 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,068 ERROR [org.hornetq.core.server] (Thread-5 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,075 ERROR [org.hornetq.core.server] (Thread-14 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,076 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,074 ERROR [org.hornetq.core.server] (Thread-8 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,080 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff9344e7-2d07-11e4-9518-8f6f55d2038b 13:06:53,082 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff9344e7-2d07-11e4-9518-8f6f55d2038b 13:06:53,082 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,083 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff91982c-2d07-11e4-9518-8f6f55d2038b 13:06:53,074 ERROR [org.hornetq.core.server] (Thread-9 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,083 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff91982c-2d07-11e4-9518-8f6f55d2038b 13:06:53,083 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:53,084 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session ff8c8f04-2d07-11e4-9518-8f6f55d2038b 13:06:53,084 WARN [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session ff8c8f04-2d07-11e4-9518-8f6f55d2038b 13:06:53,088 ERROR [org.hornetq.core.server] (Thread-8 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,089 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:53,089 ERROR [org.hornetq.core.server] (Thread-9 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1809) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.HornetQServerImpl.createQueue(HornetQServerImpl.java:1100) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.server.impl.ServerSessionImpl.createQueue(ServerSessionImpl.java:437) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:237) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:631) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:547) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:523) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:564) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:160) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] 13:06:59,088 WARN [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT] 13:06:59,089 WARN [org.hornetq.jms.server] (Thread-12 (HornetQ-client-global-threads-661509336)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119006: Channel disconnected] at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:418) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:214) [hornetq-server-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:106) [hornetq-core-client-2.3.5.Final-redhat-2.jar:2.3.5.Final-redhat-2] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]