AnsweredAssumed Answered

I can not deploy ear using customizeACM

Question asked by Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= on Aug 1, 2016
Latest reply on Aug 2, 2016 by Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ=

Like • Show 0 Likes0
Comment • 2

Hi,

I installed the aveksa7.0.0.p03 patch successfully on two environments, but in the third environment it can not deploy the ear using the script ./customizeACM.sh, it still blocked in undeploy step (it take 2 days)

Note: I use a remote oracle database

any idea how can i do to resolve this issue?

Regards.

2 people also have this question

Outcomes

2 Replies

Daniel Cinnamon Aug 1, 2016 3:52 PM
Mark Correct
Correct Answer
Hmm... unfortunately it's really hard to tell without seeing any log what it's hung up on.

Basically what's happening at this point is that the wildfly application server is being told to remove the RSA "app", so that we can replace it with your new version.

This is the log file that will really show what the wildfly application server is doing. I'd recommend opening up a support ticket with this log attached:
/home/oracle/wildfly/standalone/log/server.log

Also, this command here will ask wildfly for information about the application- may be useful to run it to see what it returns (will tell you if it's already undeployed or not too).
/home/oracle/wildfly/bin/jboss-cli.sh -c --command="deployment-info --name=aveksa.ear"
Like • Show 1 Like1
Actions
- Dj4bIamQPv7HFSpC1lG08vP2ANE8fvnDUNK3hVdVlsQ= @ Daniel Cinnamon on Aug 2, 2016 3:33 AM
  Mark Correct
  Correct Answer
  Hi Daniel Cinnamon,
  We can not open a support case for that, cause we are on test and buy periods.
  
  The commande jboss-cli.sh doesn't return any results
  The content of wildfly/standalone/log/server.log
  
  2016-08-01 15:08:31,254 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,253 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutting down...
  2016-08-01 15:08:31,298 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,298 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown hook invoked. Any active monitors will be shut down.
  2016-08-01 15:08:31,315 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,315 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor actionq#ActionQ1#41
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1 shut down.
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor alertq#AlertQ1#40
  2016-08-01 15:08:31,387 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:08:31,400 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
  2016-08-01 15:08:31,410 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,410 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1 shut down.
  2016-08-01 15:08:31,411 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,411 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor jobq#JobQ1#39
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,470 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1 shut down.
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,471 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown is complete.
  2016-08-01 15:08:31,543 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 93) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue
  2016-08-01 15:08:31,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /wpConsole
  2016-08-01 15:08:31,721 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wpQMonitor
  2016-08-01 15:08:31,761 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /wp
  2016-08-01 15:08:31,805 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /aveksa
  2016-08-01 15:08:32,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avdwdb]
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/jdbc/acmdb]
  2016-08-01 15:08:32,738 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avperf]
  2016-08-01 15:08:32,754 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  2016-08-01 15:08:32,868 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 101) JBAS011605: Unbound messaging object to jndi name java:/topic/acmMessageTopic
  2016-08-01 15:15:10,262 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
  2016-08-01 15:15:11,249 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
  2016-08-01 15:15:11,538 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
  2016-08-01 15:15:11,555 DEBUG [org.jboss.as.config] (MSC service thread 1-3) Configured system properties:
          [Standalone] =
          awt.toolkit = sun.awt.X11.XToolkit
          com.sun.net.ssl.enableECC = false
          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/oracle/wildfly/jboss-modules.jar
          java.class.version = 51.0
          java.endorsed.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/endorsed
          java.ext.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
          java.home = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre
          java.io.tmpdir = /tmp
          java.library.path = /home/oracle/instantclient_12_1::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
          java.runtime.name = OpenJDK Runtime Environment
          java.runtime.version = 1.7.0_79-b14
          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_79
          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.79-b02
          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/oracle/wildfly
          jboss.host.name = gdc1diagapp001
          jboss.modules.dir = /home/oracle/wildfly/modules
          jboss.node.name = gdc1diagapp001
          jboss.qualified.host.name = gdc1diagapp001
          jboss.server.base.dir = /home/oracle/wildfly/standalone
          jboss.server.config.dir = /home/oracle/wildfly/standalone/configuration
          jboss.server.data.dir = /home/oracle/wildfly/standalone/data
          jboss.server.deploy.dir = /home/oracle/wildfly/standalone/data/content
          jboss.server.log.dir = /home/oracle/wildfly/standalone/log
          jboss.server.name = gdc1diagapp001
          jboss.server.persist.config = true
          jboss.server.temp.dir = /home/oracle/wildfly/standalone/tmp
          line.separator =
  
          logging.configuration = file:/home/oracle/wildfly/standalone/configuration/logging.properties
          module.path = /home/oracle/wildfly/modules
          org.jboss.boot.log.file = /home/oracle/wildfly/standalone/log/server.log
          org.jboss.resolver.warning = true
          org.xml.sax.driver = __redirected.__XMLReaderFactory
          os.arch = amd64
          os.name = Linux
          os.version = 2.6.32-504.el6.x86_64
          path.separator = :
          sun.arch.data.model = 64
          sun.boot.class.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/classes
          sun.boot.library.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/amd64
          sun.cpu.endian = little
          sun.cpu.isalist =
          sun.io.unicode.encoding = UnicodeLittle
          sun.java.command = /home/oracle/wildfly/jboss-modules.jar -mp /home/oracle/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/home/oracle/wildfly -Djboss.server.base.dir=/home/oracle/wildfly/standalone --server-config=aveksa-standalone-full.xml
          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/oracle
          user.home = /home/oracle
          user.language = en
          user.name = oracle
          user.timezone = Etc/GMT+1
  2016-08-01 15:15:11,562 DEBUG [org.jboss.as.config] (MSC service thread 1-3) VM Arguments: -D[Standalone] -Xmx2006m -XX:MaxPermSize=354m -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/oracle -Dorg.jboss.boot.log.file=/home/oracle/wildfly/standalone/log/server.log -Dlogging.configuration=file:/home/oracle/wildfly/standalone/configuration/logging.properties
  2016-08-01 15:15:15,542 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute interface is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,545 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute port is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,883 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
  2016-08-01 15:15:15,899 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
  2016-08-01 15:15:15,902 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
  2016-08-01 15:15:15,970 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
  2016-08-01 15:15:15,999 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
  2016-08-01 15:15:16,006 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
  2016-08-01 15:15:16,042 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
  2016-08-01 15:15:16,032 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
  2016-08-01 15:15:16,032 INFO [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem
  [root@GDC1DIAGAPP001 Aveksa_7.0.0_P03]# cat ../wildfly/standalone/log/server.log |grep 15:08 -B 2 -A 1000
          at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
  
  2016-08-01 15:08:31,254 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,253 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutting down...
  2016-08-01 15:08:31,298 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,298 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown hook invoked. Any active monitors will be shut down.
  2016-08-01 15:08:31,315 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,315 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor actionq#ActionQ1#41
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1 shut down.
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor alertq#AlertQ1#40
  2016-08-01 15:08:31,387 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:08:31,400 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
  2016-08-01 15:08:31,410 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,410 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1 shut down.
  2016-08-01 15:08:31,411 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,411 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor jobq#JobQ1#39
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,470 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1 shut down.
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,471 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown is complete.
  2016-08-01 15:08:31,543 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 93) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue
  2016-08-01 15:08:31,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /wpConsole
  2016-08-01 15:08:31,721 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wpQMonitor
  2016-08-01 15:08:31,761 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /wp
  2016-08-01 15:08:31,805 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /aveksa
  2016-08-01 15:08:32,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avdwdb]
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/jdbc/acmdb]
  2016-08-01 15:08:32,738 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avperf]
  2016-08-01 15:08:32,754 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  2016-08-01 15:08:32,868 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 101) JBAS011605: Unbound messaging object to jndi name java:/topic/acmMessageTopic
  2016-08-01 15:15:10,262 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
  2016-08-01 15:15:11,249 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
  2016-08-01 15:15:11,538 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
  2016-08-01 15:15:11,555 DEBUG [org.jboss.as.config] (MSC service thread 1-3) Configured system properties:
          [Standalone] =
          awt.toolkit = sun.awt.X11.XToolkit
          com.sun.net.ssl.enableECC = false
          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/oracle/wildfly/jboss-modules.jar
          java.class.version = 51.0
          java.endorsed.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/endorsed
          java.ext.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
          java.home = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre
          java.io.tmpdir = /tmp
          java.library.path = /home/oracle/instantclient_12_1::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
          java.runtime.name = OpenJDK Runtime Environment
          java.runtime.version = 1.7.0_79-b14
          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_79
          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.79-b02
          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/oracle/wildfly
          jboss.host.name = gdc1diagapp001
          jboss.modules.dir = /home/oracle/wildfly/modules
          jboss.node.name = gdc1diagapp001
          jboss.qualified.host.name = gdc1diagapp001
          jboss.server.base.dir = /home/oracle/wildfly/standalone
          jboss.server.config.dir = /home/oracle/wildfly/standalone/configuration
          jboss.server.data.dir = /home/oracle/wildfly/standalone/data
          jboss.server.deploy.dir = /home/oracle/wildfly/standalone/data/content
          jboss.server.log.dir = /home/oracle/wildfly/standalone/log
          jboss.server.name = gdc1diagapp001
          jboss.server.persist.config = true
          jboss.server.temp.dir = /home/oracle/wildfly/standalone/tmp
          line.separator =
  
          logging.configuration = file:/home/oracle/wildfly/standalone/configuration/logging.properties
          module.path = /home/oracle/wildfly/modules
          org.jboss.boot.log.file = /home/oracle/wildfly/standalone/log/server.log
          org.jboss.resolver.warning = true
          org.xml.sax.driver = __redirected.__XMLReaderFactory
          os.arch = amd64
          os.name = Linux
          os.version = 2.6.32-504.el6.x86_64
          path.separator = :
          sun.arch.data.model = 64
          sun.boot.class.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/classes
          sun.boot.library.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/amd64
          sun.cpu.endian = little
          sun.cpu.isalist =
          sun.io.unicode.encoding = UnicodeLittle
          sun.java.command = /home/oracle/wildfly/jboss-modules.jar -mp /home/oracle/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/home/oracle/wildfly -Djboss.server.base.dir=/home/oracle/wildfly/standalone --server-config=aveksa-standalone-full.xml
          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/oracle
          user.home = /home/oracle
          user.language = en
          user.name = oracle
          user.timezone = Etc/GMT+1
  2016-08-01 15:15:11,562 DEBUG [org.jboss.as.config] (MSC service thread 1-3) VM Arguments: -D[Standalone] -Xmx2006m -XX:MaxPermSize=354m -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/oracle -Dorg.jboss.boot.log.file=/home/oracle/wildfly/standalone/log/server.log -Dlogging.configuration=file:/home/oracle/wildfly/standalone/configuration/logging.properties
  2016-08-01 15:15:15,542 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute interface is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,545 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute port is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,883 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
  2016-08-01 15:15:15,899 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
  2016-08-01 15:15:15,902 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
  2016-08-01 15:15:15,970 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
  2016-08-01 15:15:15,999 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
  2016-08-01 15:15:16,006 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
  2016-08-01 15:15:16,042 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
  2016-08-01 15:15:16,032 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
  2016-08-01 15:15:16,032 INFO [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem
  2016-08-01 15:15:16,062 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem
  2016-08-01 15:15:16,069 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.21.Final
  2016-08-01 15:15:16,079 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
  2016-08-01 15:15:16,075 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implementations: [main]
  2016-08-01 15:15:16,190 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017502: Undertow 1.1.0.Final starting
  2016-08-01 15:15:16,190 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.1.0.Final starting
  2016-08-01 15:15:16,415 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
  2016-08-01 15:15:16,432 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
  2016-08-01 15:15:16,445 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
  2016-08-01 15:15:16,574 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
  2016-08-01 15:15:16,625 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2
  2016-08-01 15:15:16,878 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path /home/oracle/wildfly/welcome-content
  2016-08-01 15:15:16,967 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017525: Started server default-server.
  2016-08-01 15:15:17,150 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
  2016-08-01 15:15:17,209 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:15:17,217 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:15:17,254 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = OracleXADriver
  2016-08-01 15:15:17,254 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = OracleDriver
  2016-08-01 15:15:17,490 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
  2016-08-01 15:15:17,872 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
  2016-08-01 15:15:18,085 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
  2016-08-01 15:15:18,328 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/oracle/wildfly/standalone/deployments
  2016-08-01 15:15:18,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "aveksa.ear" (runtime-name: "aveksa.ear")
  2016-08-01 15:15:18,470 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016328: CORBA Naming Service started
  2016-08-01 15:15:18,953 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener https listening on /0.0.0.0:8443
  2016-08-01 15:15:18,963 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/avperf]
  2016-08-01 15:15:18,963 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/WPDS3]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/WPDS2]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/avdb]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/avdwdb]
  2016-08-01 15:15:18,965 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/WPDS]
  2016-08-01 15:15:18,966 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTPS listener agent-ssl listening on /0.0.0.0:8444
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/acmdb]
  2016-08-01 15:15:19,061 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/oracle/wildfly/standalone/data/messagingjournal,bindingsDirectory=/home/oracle/wildfly/standalone/data/messagingbindings,largeMessagesDirectory=/home/oracle/wildfly/standalone/data/messaginglargemessages,pagingDirectory=/home/oracle/wildfly/standalone/data/messagingpaging)
  2016-08-01 15:15:19,068 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock
  2016-08-01 15:15:19,155 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221012: Using AIO Journal
  2016-08-01 15:15:19,317 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 56) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
  2016-08-01 15:15:19,404 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE
  2016-08-01 15:15:19,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP
  2016-08-01 15:15:19,496 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP
  2016-08-01 15:15:19,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock
  2016-08-01 15:15:19,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock
  2016-08-01 15:15:20,658 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221019: Deleting unreferenced message id=15,032,747,109 from the journal
  2016-08-01 15:15:20,691 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
  2016-08-01 15:15:20,772 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
  2016-08-01 15:15:20,772 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
  2016-08-01 15:15:20,902 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live
  2016-08-01 15:15:20,903 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [f525012e-320f-11e6-b1f0-e930b287ebf0]
  2016-08-01 15:15:20,914 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
  2016-08-01 15:15:20,961 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
  2016-08-01 15:15:20,971 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.wpEventQueue
  2016-08-01 15:15:20,972 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name queue/wpEventQueue
  2016-08-01 15:15:20,973 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpEventQueue
  2016-08-01 15:15:20,975 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.DLQ
  2016-08-01 15:15:20,976 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
  2016-08-01 15:15:20,977 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.wpServAutoActQueue
  2016-08-01 15:15:20,978 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name queue/wpServAutoActQueue
  2016-08-01 15:15:20,979 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpServAutoActQueue
  2016-08-01 15:15:20,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 63) HQ221003: trying to deploy queue jms.queue.wpUtilQueue
  2016-08-01 15:15:20,982 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name queue/wpUtilQueue
  2016-08-01 15:15:20,982 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpUtilQueue
  2016-08-01 15:15:21,014 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/acmConnectionFactory
  2016-08-01 15:15:21,015 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name jms/acmConnectionFactory
  2016-08-01 15:15:21,018 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name acmConnectionFactory
  2016-08-01 15:15:21,031 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 60) HQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "GDC1DIAGAPP001". If this new address is incorrect please manually configure the connector to use the proper one.
  2016-08-01 15:15:21,033 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
  2016-08-01 15:15:21,037 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
  2016-08-01 15:15:21,039 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name wpConnectionFactory
  2016-08-01 15:15:21,040 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory
  2016-08-01 15:15:21,040 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name jms/wpConnectionFactory
  2016-08-01 15:15:21,041 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.topic.acmMessageTopic
  2016-08-01 15:15:21,052 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name topic/acmMessageTopic
  2016-08-01 15:15:21,054 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/acmMessageTopic
  2016-08-01 15:15:21,157 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
  2016-08-01 15:15:21,256 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
  2016-08-01 15:15:21,256 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
  2016-08-01 15:15:21,259 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
  2016-08-01 15:15:21,259 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
  2016-08-01 15:15:53,288 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jide-dock.jar in /content/aveksa.ear/APP-INF/lib/jide-action.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,291 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxp-api.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,291 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jax-qname.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,292 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry servlet.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry lib/jcommon-1.0.0.jar in /content/aveksa.ear/APP-INF/lib/jfreechart-1.0.0.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xmlsec.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,393 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,395 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-impl.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry wss-provider-update.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,521 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /content/aveksa.ear/APP-INF/lib/saaj-impl-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,561 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb1-impl.jar in /content/aveksa.ear/APP-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,591 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "server.jar")
  2016-08-01 15:15:53,591 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpClientServletLite.war")
  2016-08-01 15:15:53,592 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "aveksa.war")
  2016-08-01 15:15:53,592 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpServer.jar")
  2016-08-01 15:15:53,593 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpQMonitor.war")
  2016-08-01 15:15:53,593 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "wpConsole.war")
  2016-08-01 15:15:53,685 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/log4j.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/bsf.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,693 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/js.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,833 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry APP-INF/lib/log4j.jar in /content/aveksa.ear/wpConsole.war/WEB-INF/lib/wpConsole.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015850: /content/aveksa.ear/aveksa.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.
  2016-08-01 15:15:55,125 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxp-api.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,125 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jax-qname.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,126 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,129 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry servlet.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:58,824 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment aveksa.ear
  2016-08-01 15:15:59,227 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.1.3.Final
  2016-08-01 15:15:59,847 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment wpConsole.war
  2016-08-01 15:15:59,862 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment server.jar
  2016-08-01 15:15:59,879 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment wpClientServletLite.war
  2016-08-01 15:16:00,041 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment wpQMonitor.war
  2016-08-01 15:16:01,036 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment wpServer.jar
  2016-08-01 15:16:01,048 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UtilityPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:app/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:module/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:jboss/exported/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:global/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
          java:app/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
          java:module/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
  
  2016-08-01 15:16:01,050 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named PriorityUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:app/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:module/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:global/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:app/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:module/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:jboss/exported/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
  
  2016-08-01 15:16:01,051 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named GroupTypeUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:app/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:global/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:app/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:jboss/exported/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
  
  2016-08-01 15:16:01,051 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MailUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:app/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:module/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:global/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:app/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:module/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:jboss/exported/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
  
  2016-08-01 15:16:01,052 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named TablePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:app/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:module/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:global/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:app/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:module/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:jboss/exported/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
  
  2016-08-01 15:16:01,054 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named EventPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:app/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:module/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:global/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:app/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:module/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:jboss/exported/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
  
  2016-08-01 15:16:01,055 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named HolCalPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:app/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:module/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:jboss/exported/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:global/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
          java:app/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
          java:module/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
  
  2016-08-01 15:16:01,056 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UniqueIDUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:app/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:jboss/exported/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:global/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
          java:app/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
          java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
  
  2016-08-01 15:16:01,064 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ForceActionUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:app/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:module/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:jboss/exported/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:global/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
          java:app/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
          java:module/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
  
  2016-08-01 15:16:01,067 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MailPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:app/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:module/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:jboss/exported/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:global/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
          java:app/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
          java:module/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
  
  2016-08-01 15:16:01,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named SchemaPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:app/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:module/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:jboss/exported/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:global/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
          java:app/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
          java:module/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
  
  2016-08-01 15:16:01,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CompletionCodeUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:app/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:global/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:app/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:jboss/exported/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
  
  2016-08-01 15:16:01,073 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:app/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:module/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:jboss/exported/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:global/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
          java:app/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
          java:module/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
  
  2016-08-01 15:16:01,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProfileUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:app/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:module/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:global/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:app/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:module/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:jboss/exported/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
  
  2016-08-01 15:16:01,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AlertPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:app/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:global/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:app/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:jboss/exported/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
  
  2016-08-01 15:16:01,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CategoryUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:app/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:module/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:global/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:app/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:module/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:jboss/exported/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
  
  2016-08-01 15:16:01,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProcessUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:app/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:module/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:jboss/exported/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:global/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
          java:app/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
          java:module/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
  
  2016-08-01 15:16:01,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named HolCalUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:app/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:module/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:global/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:app/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:module/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:jboss/exported/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
  
  2016-08-01 15:16:01,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CategoryPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:app/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:module/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:jboss/exported/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:global/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
          java:app/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
          java:module/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
  
  2016-08-01 15:16:01,079 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AlertUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:app/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:module/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:jboss/exported/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:global/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
          java:app/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
          java:module/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
  
  2016-08-01 15:16:01,080 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptExecutePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:app/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:module/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:jboss/exported/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:global/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
          java:app/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
          java:module/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
  
  2016-08-01 15:16:01,081 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named BusCalUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:app/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:module/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:jboss/exported/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:global/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
          java:app/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
          java:module/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
  
  2016-08-01 15:16:01,082 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named TableUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:app/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:module/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:global/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:app/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:module/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:jboss/exported/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
  
  2016-08-01 15:16:01,083 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:app/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:module/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:global/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:app/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:module/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:jboss/exported/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
  
  2016-08-01 15:16:01,084 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named BusCalPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:app/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:module/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:global/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:app/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:module/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:jboss/exported/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
  
  2016-08-01 15:16:01,085 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProfilePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:app/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:module/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:global/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:app/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:module/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:jboss/exported/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
  
  2016-08-01 15:16:01,086 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptExecAsyncPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:app/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:jboss/exported/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:global/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
          java:app/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
          java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
  
  2016-08-01 15:16:01,087 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CompletionCodePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:app/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:module/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:global/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:app/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:module/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:jboss/exported/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
  
  2016-08-01 15:16:01,088 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ServerConfigPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:app/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:module/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:global/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:app/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:module/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:jboss/exported/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
  
  2016-08-01 15:16:01,089 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named JobPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:app/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:module/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:global/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:app/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:module/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:jboss/exported/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
  
  2016-08-01 15:16:01,090 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named EventUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:app/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:module/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:global/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:app/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:module/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:jboss/exported/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
  
  2016-08-01 15:16:01,091 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named PriorityPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:app/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:module/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:global/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:app/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:module/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:jboss/exported/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
  
  2016-08-01 15:16:01,092 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ResourcePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:app/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:module/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:global/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:app/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:module/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:jboss/exported/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
  
  2016-08-01 15:16:01,093 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named WorkItemPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:app/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:module/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:jboss/exported/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:global/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
          java:app/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
          java:module/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
  
  2016-08-01 15:16:01,094 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named SchemaUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:app/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:module/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:global/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:app/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:module/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:jboss/exported/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
  
  2016-08-01 15:16:01,095 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named JobUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:app/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:module/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:global/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:app/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:module/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:jboss/exported/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
  
  2016-08-01 15:16:01,096 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named WorkItemUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:app/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:jboss/exported/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:global/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
          java:app/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
          java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
  
  2016-08-01 15:16:01,098 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named GroupTypePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:app/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:module/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:global/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:app/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:module/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:jboss/exported/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
  
  2016-08-01 15:16:01,098 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MonitorPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:app/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:module/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:jboss/exported/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:global/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
          java:app/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
          java:module/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
  
  2016-08-01 15:16:01,099 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UniqueIDPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:app/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:module/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:jboss/exported/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:global/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
          java:app/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
          java:module/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
  
  2016-08-01 15:16:01,100 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named FormPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:app/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:jboss/exported/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:global/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
          java:app/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
          java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
  
  2016-08-01 15:16:01,101 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProcessPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:app/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:module/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:jboss/exported/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:global/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
          java:app/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
          java:module/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
  
  2016-08-01 15:16:01,101 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named FormUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:app/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:module/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:global/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:app/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:module/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:jboss/exported/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
  
  2016-08-01 15:16:01,257 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment aveksa.war
  2016-08-01 15:16:01,548 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:16:01,549 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: aveksa.ear
  2016-08-01 15:16:01,712 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.2.6 (Final)
  2016-08-01 15:16:01,729 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:16:01,744 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment aveksa.ear
  2016-08-01 15:16:06,377 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'ServerAutomatedActivityMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:06,390 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'UtilityMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:06,401 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'EventMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:08,765 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=com.aveksa.server.ws.AccessRequestWebServiceProvider
  address=http://localhost:8080/server/AccessRequestWebService/AccessRequestWebServiceProvider
  implementor=com.aveksa.server.ws.AccessRequestWebServiceProvider
  serviceName={http://aveksa.com/services/Global}AccessRequestWebService
  portName={http://aveksa.com/services/Global}AccessRequestWebServicePort
  annotationWsdlLocation=null
  wsdlLocationOverride=null
  mtomEnabled=false
  2016-08-01 15:16:09,521 ERROR [stderr] (MSC service thread 1-3) log4j:WARN No appenders could be found for logger (com.aveksa.server.ws.AccessRequestWebServiceProvider).
  2016-08-01 15:16:09,522 ERROR [stderr] (MSC service thread 1-3) log4j:WARN Please initialize the log4j system properly.
  2016-08-01 15:16:09,628 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://aveksa.com/services/Global}AccessRequestWebService from class com.aveksa.server.ws.AccessRequestWebService
  2016-08-01 15:16:11,255 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/server/AccessRequestWebService/AccessRequestWebServiceProvider
  2016-08-01 15:16:11,475 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/oracle/wildfly-8.2.0.Final/standalone/data/wsdl/aveksa.ear/server.jar/AccessRequestWebService.wsdl
  2016-08-01 15:16:11,486 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  2016-08-01 15:16:11,500 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'SubscriberMDB' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:47,493 INFO [org.xnio] (Thread-132) XNIO version 3.2.2.Final
  2016-08-01 15:16:47,522 INFO [org.xnio.nio] (Thread-132) XNIO NIO Implementation Version 3.2.2.Final
  2016-08-01 15:16:47,748 INFO [org.jboss.remoting] (Thread-132) JBoss Remoting version (unknown)
  2016-08-01 15:16:52,559 INFO [org.jboss.ejb.client] (MSC service thread 1-3) JBoss EJB Client version 2.0.1.Final
  2016-08-01 15:18:11,956 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (MSC service thread 1-3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:347)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:354)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.access$200(LocalManagedConnectionFactory.java:63)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:263)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:254)
          at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_79]
          at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_79]
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:253)
          at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:1166)
          at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:446)
          at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:461)
          at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:433)
          at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:379)
          at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:421)
          at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:515)
          at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
          at com.aveksa.server.utils.PerfStatUtil.getNewPerfConnection(PerfStatUtil.java:100) [server.jar:]
          at com.aveksa.server.utils.PerfStatUtil.hasConnection(PerfStatUtil.java:113) [server.jar:]
          at com.aveksa.server.runtime.AveksaSystem.initialize(AveksaSystem.java:333) [server.jar:]
          at com.aveksa.init.Startup.init(Startup.java:41) [classes:]
          at com.aveksa.gui.core.ACMFramework.init(ACMFramework.java:84) [classes:]
          at com.aveksa.gui.core.ACMFramework.initInstance(ACMFramework.java:73) [classes:]
          at com.aveksa.init.InitServlet.init(InitServlet.java:42) [classes:]
          at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.handle(RunAsLifecycleInterceptor.java:66)
          at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:77)
          at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:220) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:125) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:508) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
          at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
          at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
  Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
  
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:573) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:431) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:366) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:752) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:366) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) [ojdbc5.jar:11.2.0.2.0]
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:322)
          ... 36 more
  
  2016-08-01 15:18:14,310 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /aveksa
  2016-08-01 15:18:14,436 INFO [stdout] (MSC service thread 1-4) 2016-08-01 15:18:14,434 [MSC service thread 1-4] INFO com.workpoint.servlet.client.WpClientServlet - Loaded properties from vfs:/content/aveksa.ear/APP-INF/lib/acmConfig.jar/workpoint-server.properties
  2016-08-01 15:18:14,438 INFO [stdout] (MSC service thread 1-4) 2016-08-01 15:18:14,438 [MSC service thread 1-4] INFO com.workpoint.servlet.client.WpClientServlet - PRODUCT = Workpoint; VERSION = 3.5; BUILD = 20101207.P024; BUILD DATE = February 21, 2014
  2016-08-01 15:18:14,444 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /wp
  2016-08-01 15:18:14,661 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:18:14,661 [MSC service thread 1-1] INFO com.workpoint.queue.WpQMonitors - PRODUCT = Workpoint; VERSION = 3.5; BUILD = 20101207.P024; BUILD DATE = February 21, 2014
  2016-08-01 15:18:14,662 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:18:14,662 [MSC service thread 1-1] INFO com.workpoint.queue.WpQMonitors - Loaded queue monitor configuration from vfs:/content/aveksa.ear/APP-INF/lib/acmConfig.jar/wpqmonitor.xml
  2016-08-01 15:18:14,682 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /wpQMonitor
  2016-08-01 15:18:14,839 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /wpConsole
  2016-08-01 15:18:15,007 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "aveksa.ear" (runtime-name : "aveksa.ear")
  2016-08-01 15:18:15,070 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
  2016-08-01 15:18:15,070 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
  2016-08-01 15:18:15,071 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 186025ms - Started 3171 of 3261 services (172 services are lazy, passive or on-demand)
  2016-08-01 15:18:19,805 INFO [stdout] (Timer-5) 2016-08-01 15:18:19,803 [Timer-5] INFO com.workpoint.server.ServerProperties - ServerProperties.setProperty() invoked for property= calculated.db.offset.millis, value=1375
  2016-08-01 15:18:20,179 INFO [stdout] (Timer-4) 2016-08-01 15:18:20,151 [Timer-4] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1#42 successfully started.
  2016-08-01 15:18:20,199 INFO [stdout] (Timer-6) 2016-08-01 15:18:20,187 [Timer-6] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1#44 successfully started.
  2016-08-01 15:18:20,200 INFO [stdout] (Timer-5) 2016-08-01 15:18:20,151 [Timer-5] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1#43 successfully started.
  2016-08-01 15:20:32,828 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:20:32,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wpConsole
  2016-08-01 15:20:32,900 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /wpQMonitor
  2016-08-01 15:20:32,906 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,906 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor actionq#ActionQ1#42
  2016-08-01 15:20:32,952 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,952 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1 shut down.
  2016-08-01 15:20:32,953 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,953 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor alertq#AlertQ1#43
  2016-08-01 15:20:33,001 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,001 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1 shut down.
  2016-08-01 15:20:33,002 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,002 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor jobq#JobQ1#44
  2016-08-01 15:20:33,053 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,052 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1 shut down.
  2016-08-01 15:20:33,083 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wp
  2016-08-01 15:20:33,118 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /aveksa
  2016-08-01 15:20:34,129 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  [root@GDC1DIAGAPP001 Aveksa_7.0.0_P03]# cat ../wildfly/standalone/log/server.log |grep 15:08 -B 2 -A 1000> /tmp/
  agent_management.log         hsperfdata_root/             HXTT1831957940242233905.TMP HXTT3140373832271671920.TMP HXTT4231313829024240232.TMP HXTT530820418846547165.TMP   HXTT7198363750788888063.TMP HXTT88122673991580209.TMP
  aveksa/                      HXTT114866227524478656.TMP   HXTT2196290314031863079.TMP HXTT3484094667188709285.TMP HXTT4265459228337822032.TMP HXTT5625429965839289615.TMP HXTT7248988723058878069.TMP HXTT883721789044940344.TMP
  aveksa.ear/                  HXTT1327182950327586677.TMP HXTT2338388500862955552.TMP HXTT3536855439429431357.TMP HXTT4496428106517308854.TMP HXTT5884225782516125232.TMP HXTT7702222471421100558.TMP HXTT9041095966412824226.TMP
  client-p/                    HXTT1358086304895601494.TMP HXTT2355617171223044698.TMP HXTT3659572870185620259.TMP HXTT4522151038259334103.TMP HXTT6408480841883693960.TMP HXTT7750746325034387862.TMP HXTT9092693903080553502.TMP
  customizeACM/                HXTT1384643350515748072.TMP HXTT2699593099270569038.TMP HXTT3919360740074193640.TMP HXTT4826410173821352930.TMP HXTT6453904592097379843.TMP HXTT8113003145165524106.TMP HXTT9119739038976412732.TMP
  dbtime.tmp                   HXTT1384754835691399887.TMP HXTT2702409901569178489.TMP HXTT3957022377027651052.TMP HXTT4933792262025002522.TMP HXTT6604050281163873443.TMP HXTT8257534348138219825.TMP .ICE-unix/
  fifo                         HXTT1612956294309751701.TMP HXTT2792216329302784338.TMP HXTT4000668696896037386.TMP HXTT4985006002157510231.TMP HXTT6766169186597663092.TMP HXTT8481284255774885043.TMP vmware-root/
  hsperfdata_oracle/           HXTT1727149180531013060.TMP HXTT3101956477865026460.TMP HXTT4000953411466141053.TMP HXTT5000750928917798298.TMP HXTT6846149118396639242.TMP HXTT8719714323276333866.TMP vmware-tools-distrib/
  [root@GDC1DIAGAPP001 Aveksa_7.0.0_P03]# cat ../wildfly/standalone/log/server.log |grep 15:08 -B 2 -A 1000> /tmp/log.txt
  grep: option requires an argument -- 'A'
  Usage: grep [OPTION]... PATTERN [FILE]...
  Try `grep --help' for more information.
  [root@GDC1DIAGAPP001 Aveksa_7.0.0_P03]# cat ../wildfly/standalone/log/server.log |grep 15:08 -B 2 -A 1000 > /tmp/log.txt
  [root@GDC1DIAGAPP001 Aveksa_7.0.0_P03]# cat /tmp/log.txt
          at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
  
  2016-08-01 15:08:31,254 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,253 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutting down...
  2016-08-01 15:08:31,298 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,298 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown hook invoked. Any active monitors will be shut down.
  2016-08-01 15:08:31,315 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,315 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor actionq#ActionQ1#41
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1 shut down.
  2016-08-01 15:08:31,357 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,357 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor alertq#AlertQ1#40
  2016-08-01 15:08:31,387 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:08:31,400 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2
  2016-08-01 15:08:31,410 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,410 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1 shut down.
  2016-08-01 15:08:31,411 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,411 [Thread-255] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor jobq#JobQ1#39
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,470 [Thread-255] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1 shut down.
  2016-08-01 15:08:31,471 INFO [stdout] (Thread-255) 2016-08-01 15:08:31,471 [Thread-255] INFO com.workpoint.queue.WpQMonitors - Shutdown is complete.
  2016-08-01 15:08:31,543 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 93) JBAS011605: Unbound messaging object to jndi name java:/jms/queue/ExpiryQueue
  2016-08-01 15:08:31,546 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /wpConsole
  2016-08-01 15:08:31,721 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wpQMonitor
  2016-08-01 15:08:31,761 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /wp
  2016-08-01 15:08:31,805 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /aveksa
  2016-08-01 15:08:32,707 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avdwdb]
  2016-08-01 15:08:32,737 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/jdbc/acmdb]
  2016-08-01 15:08:32,738 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:/jdbc/avperf]
  2016-08-01 15:08:32,754 INFO [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  2016-08-01 15:08:32,868 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 101) JBAS011605: Unbound messaging object to jndi name java:/topic/acmMessageTopic
  2016-08-01 15:15:10,262 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
  2016-08-01 15:15:11,249 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
  2016-08-01 15:15:11,538 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
  2016-08-01 15:15:11,555 DEBUG [org.jboss.as.config] (MSC service thread 1-3) Configured system properties:
          [Standalone] =
          awt.toolkit = sun.awt.X11.XToolkit
          com.sun.net.ssl.enableECC = false
          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/oracle/wildfly/jboss-modules.jar
          java.class.version = 51.0
          java.endorsed.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/endorsed
          java.ext.dirs = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
          java.home = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre
          java.io.tmpdir = /tmp
          java.library.path = /home/oracle/instantclient_12_1::/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
          java.runtime.name = OpenJDK Runtime Environment
          java.runtime.version = 1.7.0_79-b14
          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_79
          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.79-b02
          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/oracle/wildfly
          jboss.host.name = gdc1diagapp001
          jboss.modules.dir = /home/oracle/wildfly/modules
          jboss.node.name = gdc1diagapp001
          jboss.qualified.host.name = gdc1diagapp001
          jboss.server.base.dir = /home/oracle/wildfly/standalone
          jboss.server.config.dir = /home/oracle/wildfly/standalone/configuration
          jboss.server.data.dir = /home/oracle/wildfly/standalone/data
          jboss.server.deploy.dir = /home/oracle/wildfly/standalone/data/content
          jboss.server.log.dir = /home/oracle/wildfly/standalone/log
          jboss.server.name = gdc1diagapp001
          jboss.server.persist.config = true
          jboss.server.temp.dir = /home/oracle/wildfly/standalone/tmp
          line.separator =
  
          logging.configuration = file:/home/oracle/wildfly/standalone/configuration/logging.properties
          module.path = /home/oracle/wildfly/modules
          org.jboss.boot.log.file = /home/oracle/wildfly/standalone/log/server.log
          org.jboss.resolver.warning = true
          org.xml.sax.driver = __redirected.__XMLReaderFactory
          os.arch = amd64
          os.name = Linux
          os.version = 2.6.32-504.el6.x86_64
          path.separator = :
          sun.arch.data.model = 64
          sun.boot.class.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/rhino.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/classes
          sun.boot.library.path = /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre/lib/amd64
          sun.cpu.endian = little
          sun.cpu.isalist =
          sun.io.unicode.encoding = UnicodeLittle
          sun.java.command = /home/oracle/wildfly/jboss-modules.jar -mp /home/oracle/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/home/oracle/wildfly -Djboss.server.base.dir=/home/oracle/wildfly/standalone --server-config=aveksa-standalone-full.xml
          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/oracle
          user.home = /home/oracle
          user.language = en
          user.name = oracle
          user.timezone = Etc/GMT+1
  2016-08-01 15:15:11,562 DEBUG [org.jboss.as.config] (MSC service thread 1-3) VM Arguments: -D[Standalone] -Xmx2006m -XX:MaxPermSize=354m -Dcom.sun.net.ssl.enableECC=false -Djava.awt.headless=true -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/home/oracle -Dorg.jboss.boot.log.file=/home/oracle/wildfly/standalone/log/server.log -Dlogging.configuration=file:/home/oracle/wildfly/standalone/configuration/logging.properties
  2016-08-01 15:15:15,542 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute interface is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,545 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute port is deprecated, and it might be removed in future version!
  2016-08-01 15:15:15,883 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
  2016-08-01 15:15:15,899 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
  2016-08-01 15:15:15,902 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
  2016-08-01 15:15:15,970 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
  2016-08-01 15:15:15,999 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
  2016-08-01 15:15:16,006 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
  2016-08-01 15:15:16,042 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
  2016-08-01 15:15:16,032 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
  2016-08-01 15:15:16,032 INFO [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem
  2016-08-01 15:15:16,062 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem
  2016-08-01 15:15:16,069 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013170: Current PicketBox version=4.0.21.Final
  2016-08-01 15:15:16,079 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
  2016-08-01 15:15:16,075 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implementations: [main]
  2016-08-01 15:15:16,190 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017502: Undertow 1.1.0.Final starting
  2016-08-01 15:15:16,190 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.1.0.Final starting
  2016-08-01 15:15:16,415 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
  2016-08-01 15:15:16,432 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
  2016-08-01 15:15:16,445 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
  2016-08-01 15:15:16,574 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
  2016-08-01 15:15:16,625 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2
  2016-08-01 15:15:16,878 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path /home/oracle/wildfly/welcome-content
  2016-08-01 15:15:16,967 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017525: Started server default-server.
  2016-08-01 15:15:17,150 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
  2016-08-01 15:15:17,209 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:15:17,217 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:15:17,254 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = OracleXADriver
  2016-08-01 15:15:17,254 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = OracleDriver
  2016-08-01 15:15:17,490 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
  2016-08-01 15:15:17,872 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
  2016-08-01 15:15:18,085 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
  2016-08-01 15:15:18,328 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/oracle/wildfly/standalone/deployments
  2016-08-01 15:15:18,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "aveksa.ear" (runtime-name: "aveksa.ear")
  2016-08-01 15:15:18,470 INFO [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016328: CORBA Naming Service started
  2016-08-01 15:15:18,953 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTPS listener https listening on /0.0.0.0:8443
  2016-08-01 15:15:18,963 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/avperf]
  2016-08-01 15:15:18,963 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/WPDS3]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/WPDS2]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/avdb]
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/avdwdb]
  2016-08-01 15:15:18,965 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/WPDS]
  2016-08-01 15:15:18,966 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017519: Undertow HTTPS listener agent-ssl listening on /0.0.0.0:8444
  2016-08-01 15:15:18,964 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:/jdbc/acmdb]
  2016-08-01 15:15:19,061 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/oracle/wildfly/standalone/data/messagingjournal,bindingsDirectory=/home/oracle/wildfly/standalone/data/messagingbindings,largeMessagesDirectory=/home/oracle/wildfly/standalone/data/messaginglargemessages,pagingDirectory=/home/oracle/wildfly/standalone/data/messagingpaging)
  2016-08-01 15:15:19,068 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock
  2016-08-01 15:15:19,155 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221012: Using AIO Journal
  2016-08-01 15:15:19,317 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 56) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
  2016-08-01 15:15:19,404 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE
  2016-08-01 15:15:19,478 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP
  2016-08-01 15:15:19,496 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP
  2016-08-01 15:15:19,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock
  2016-08-01 15:15:19,624 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock
  2016-08-01 15:15:20,658 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221019: Deleting unreferenced message id=15,032,747,109 from the journal
  2016-08-01 15:15:20,691 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
  2016-08-01 15:15:20,772 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
  2016-08-01 15:15:20,772 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
  2016-08-01 15:15:20,902 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live
  2016-08-01 15:15:20,903 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [f525012e-320f-11e6-b1f0-e930b287ebf0]
  2016-08-01 15:15:20,914 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
  2016-08-01 15:15:20,961 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
  2016-08-01 15:15:20,971 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.wpEventQueue
  2016-08-01 15:15:20,972 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name queue/wpEventQueue
  2016-08-01 15:15:20,973 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpEventQueue
  2016-08-01 15:15:20,975 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.DLQ
  2016-08-01 15:15:20,976 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
  2016-08-01 15:15:20,977 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.wpServAutoActQueue
  2016-08-01 15:15:20,978 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name queue/wpServAutoActQueue
  2016-08-01 15:15:20,979 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpServAutoActQueue
  2016-08-01 15:15:20,980 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 63) HQ221003: trying to deploy queue jms.queue.wpUtilQueue
  2016-08-01 15:15:20,982 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name queue/wpUtilQueue
  2016-08-01 15:15:20,982 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/wpUtilQueue
  2016-08-01 15:15:21,014 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/acmConnectionFactory
  2016-08-01 15:15:21,015 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name jms/acmConnectionFactory
  2016-08-01 15:15:21,018 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name acmConnectionFactory
  2016-08-01 15:15:21,031 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 60) HQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "GDC1DIAGAPP001". If this new address is incorrect please manually configure the connector to use the proper one.
  2016-08-01 15:15:21,033 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
  2016-08-01 15:15:21,037 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
  2016-08-01 15:15:21,039 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name wpConnectionFactory
  2016-08-01 15:15:21,040 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory
  2016-08-01 15:15:21,040 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name jms/wpConnectionFactory
  2016-08-01 15:15:21,041 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.topic.acmMessageTopic
  2016-08-01 15:15:21,052 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name topic/acmMessageTopic
  2016-08-01 15:15:21,054 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/acmMessageTopic
  2016-08-01 15:15:21,157 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA
  2016-08-01 15:15:21,256 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started
  2016-08-01 15:15:21,256 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra
  2016-08-01 15:15:21,259 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
  2016-08-01 15:15:21,259 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
  2016-08-01 15:15:53,288 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jide-dock.jar in /content/aveksa.ear/APP-INF/lib/jide-action.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,291 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxp-api.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,291 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jax-qname.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,292 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry servlet.jar in /content/aveksa.ear/APP-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry lib/jcommon-1.0.0.jar in /content/aveksa.ear/APP-INF/lib/jfreechart-1.0.0.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry xmlsec.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,393 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,395 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-impl.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,396 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry wss-provider-update.jar in /content/aveksa.ear/APP-INF/lib/xws-security-2.0-FCS.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,521 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry saaj-api.jar in /content/aveksa.ear/APP-INF/lib/saaj-impl-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,561 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry jaxb1-impl.jar in /content/aveksa.ear/APP-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,591 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "server.jar")
  2016-08-01 15:15:53,591 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpClientServletLite.war")
  2016-08-01 15:15:53,592 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "aveksa.war")
  2016-08-01 15:15:53,592 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpServer.jar")
  2016-08-01 15:15:53,593 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015973: Starting subdeployment (runtime-name: "wpQMonitor.war")
  2016-08-01 15:15:53,593 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "wpConsole.war")
  2016-08-01 15:15:53,685 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/log4j.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/bsf.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,693 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015960: Class Path entry APP-INF/lib/js.jar in /content/aveksa.ear/wpQMonitor.war/WEB-INF/lib/wpQMonitor.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:53,833 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry APP-INF/lib/log4j.jar in /content/aveksa.ear/wpConsole.war/WEB-INF/lib/wpConsole.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,116 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015850: /content/aveksa.ear/aveksa.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.
  2016-08-01 15:15:55,125 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jaxp-api.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,125 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry jax-qname.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,126 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry activation.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:55,129 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry servlet.jar in /content/aveksa.ear/aveksa.war/WEB-INF/lib/saaj-api-1.3.jar does not point to a valid jar for a Class-Path reference.
  2016-08-01 15:15:58,824 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment aveksa.ear
  2016-08-01 15:15:59,227 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.1.3.Final
  2016-08-01 15:15:59,847 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment wpConsole.war
  2016-08-01 15:15:59,862 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment server.jar
  2016-08-01 15:15:59,879 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment wpClientServletLite.war
  2016-08-01 15:16:00,041 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment wpQMonitor.war
  2016-08-01 15:16:01,036 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment wpServer.jar
  2016-08-01 15:16:01,048 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UtilityPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:app/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:module/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:jboss/exported/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvt
          java:global/aveksa/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
          java:app/wpServer/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
          java:module/UtilityPvt_EJB!com.workpoint.server.pojo.UtilityPvtLocal
  
  2016-08-01 15:16:01,050 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named PriorityUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:app/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:module/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvtLocal
          java:global/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:app/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:module/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
          java:jboss/exported/aveksa/wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.pojo.PriorityUpdatePvt
  
  2016-08-01 15:16:01,051 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named GroupTypeUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:app/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvtLocal
          java:global/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:app/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
          java:jboss/exported/aveksa/wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.pojo.GroupTypeUpdatePvt
  
  2016-08-01 15:16:01,051 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MailUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:app/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:module/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvtLocal
          java:global/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:app/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:module/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
          java:jboss/exported/aveksa/wpServer/MailUpdatePvt_EJB!com.workpoint.server.pojo.MailUpdatePvt
  
  2016-08-01 15:16:01,052 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named TablePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:app/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:module/TablePvt_EJB!com.workpoint.server.pojo.TablePvtLocal
          java:global/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:app/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:module/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
          java:jboss/exported/aveksa/wpServer/TablePvt_EJB!com.workpoint.server.pojo.TablePvt
  
  2016-08-01 15:16:01,054 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named EventPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:app/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:module/EventPvt_EJB!com.workpoint.server.pojo.EventPvtLocal
          java:global/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:app/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:module/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
          java:jboss/exported/aveksa/wpServer/EventPvt_EJB!com.workpoint.server.pojo.EventPvt
  
  2016-08-01 15:16:01,055 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named HolCalPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:app/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:module/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:jboss/exported/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvt
          java:global/aveksa/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
          java:app/wpServer/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
          java:module/HolCalPvt_EJB!com.workpoint.server.pojo.HolCalPvtLocal
  
  2016-08-01 15:16:01,056 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UniqueIDUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:app/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:jboss/exported/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvt
          java:global/aveksa/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
          java:app/wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
          java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.pojo.UniqueIDUpdatePvtLocal
  
  2016-08-01 15:16:01,064 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ForceActionUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:app/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:module/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:jboss/exported/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvt
          java:global/aveksa/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
          java:app/wpServer/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
          java:module/ForceActionUpdatePvt_EJB!com.workpoint.server.pojo.ForceActionUpdatePvtLocal
  
  2016-08-01 15:16:01,067 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MailPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:app/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:module/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:jboss/exported/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvt
          java:global/aveksa/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
          java:app/wpServer/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
          java:module/MailPvt_EJB!com.workpoint.server.pojo.MailPvtLocal
  
  2016-08-01 15:16:01,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named SchemaPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:app/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:module/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:jboss/exported/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvt
          java:global/aveksa/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
          java:app/wpServer/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
          java:module/SchemaPvt_EJB!com.workpoint.server.pojo.SchemaPvtLocal
  
  2016-08-01 15:16:01,070 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CompletionCodeUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:app/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvtLocal
          java:global/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:app/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
          java:jboss/exported/aveksa/wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.pojo.CompletionCodeUpdatePvt
  
  2016-08-01 15:16:01,073 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:app/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:module/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:jboss/exported/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvt
          java:global/aveksa/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
          java:app/wpServer/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
          java:module/ScriptPvt_EJB!com.workpoint.server.pojo.ScriptPvtLocal
  
  2016-08-01 15:16:01,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProfileUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:app/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:module/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvtLocal
          java:global/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:app/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:module/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
          java:jboss/exported/aveksa/wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.pojo.ProfileUpdatePvt
  
  2016-08-01 15:16:01,075 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AlertPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:app/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvtLocal
          java:global/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:app/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:module/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
          java:jboss/exported/aveksa/wpServer/AlertPvt_EJB!com.workpoint.server.pojo.AlertPvt
  
  2016-08-01 15:16:01,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CategoryUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:app/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:module/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvtLocal
          java:global/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:app/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:module/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
          java:jboss/exported/aveksa/wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.pojo.CategoryUpdatePvt
  
  2016-08-01 15:16:01,077 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProcessUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:app/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:module/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:jboss/exported/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvt
          java:global/aveksa/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
          java:app/wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
          java:module/ProcessUpdatePvt_EJB!com.workpoint.server.pojo.ProcessUpdatePvtLocal
  
  2016-08-01 15:16:01,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named HolCalUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:app/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:module/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvtLocal
          java:global/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:app/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:module/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
          java:jboss/exported/aveksa/wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.pojo.HolCalUpdatePvt
  
  2016-08-01 15:16:01,078 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CategoryPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:app/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:module/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:jboss/exported/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvt
          java:global/aveksa/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
          java:app/wpServer/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
          java:module/CategoryPvt_EJB!com.workpoint.server.pojo.CategoryPvtLocal
  
  2016-08-01 15:16:01,079 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named AlertUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:app/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:module/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:jboss/exported/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvt
          java:global/aveksa/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
          java:app/wpServer/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
          java:module/AlertUpdatePvt_EJB!com.workpoint.server.pojo.AlertUpdatePvtLocal
  
  2016-08-01 15:16:01,080 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptExecutePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:app/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:module/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:jboss/exported/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvt
          java:global/aveksa/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
          java:app/wpServer/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
          java:module/ScriptExecutePvt_EJB!com.workpoint.server.pojo.ScriptExecutePvtLocal
  
  2016-08-01 15:16:01,081 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named BusCalUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:app/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:module/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:jboss/exported/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvt
          java:global/aveksa/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
          java:app/wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
          java:module/BusCalUpdatePvt_EJB!com.workpoint.server.pojo.BusCalUpdatePvtLocal
  
  2016-08-01 15:16:01,082 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named TableUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:app/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:module/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvtLocal
          java:global/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:app/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:module/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
          java:jboss/exported/aveksa/wpServer/TableUpdatePvt_EJB!com.workpoint.server.pojo.TableUpdatePvt
  
  2016-08-01 15:16:01,083 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:app/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:module/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvtLocal
          java:global/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:app/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:module/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
          java:jboss/exported/aveksa/wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.pojo.ScriptUpdatePvt
  
  2016-08-01 15:16:01,084 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named BusCalPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:app/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:module/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvtLocal
          java:global/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:app/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:module/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
          java:jboss/exported/aveksa/wpServer/BusCalPvt_EJB!com.workpoint.server.pojo.BusCalPvt
  
  2016-08-01 15:16:01,085 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProfilePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:app/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:module/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvtLocal
          java:global/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:app/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:module/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
          java:jboss/exported/aveksa/wpServer/ProfilePvt_EJB!com.workpoint.server.pojo.ProfilePvt
  
  2016-08-01 15:16:01,086 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ScriptExecAsyncPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:app/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:jboss/exported/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvt
          java:global/aveksa/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
          java:app/wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
          java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.pojo.ScriptExecAsyncPvtLocal
  
  2016-08-01 15:16:01,087 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named CompletionCodePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:app/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:module/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvtLocal
          java:global/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:app/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:module/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
          java:jboss/exported/aveksa/wpServer/CompletionCodePvt_EJB!com.workpoint.server.pojo.CompletionCodePvt
  
  2016-08-01 15:16:01,088 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ServerConfigPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:app/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:module/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvtLocal
          java:global/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:app/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:module/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
          java:jboss/exported/aveksa/wpServer/ServerConfigPvt_EJB!com.workpoint.server.pojo.ServerConfigPvt
  
  2016-08-01 15:16:01,089 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named JobPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:app/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:module/JobPvt_EJB!com.workpoint.server.pojo.JobPvtLocal
          java:global/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:app/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:module/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
          java:jboss/exported/aveksa/wpServer/JobPvt_EJB!com.workpoint.server.pojo.JobPvt
  
  2016-08-01 15:16:01,090 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named EventUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:app/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:module/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvtLocal
          java:global/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:app/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:module/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
          java:jboss/exported/aveksa/wpServer/EventUpdatePvt_EJB!com.workpoint.server.pojo.EventUpdatePvt
  
  2016-08-01 15:16:01,091 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named PriorityPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:app/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:module/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvtLocal
          java:global/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:app/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:module/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
          java:jboss/exported/aveksa/wpServer/PriorityPvt_EJB!com.workpoint.server.pojo.PriorityPvt
  
  2016-08-01 15:16:01,092 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ResourcePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:app/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:module/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvtLocal
          java:global/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:app/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:module/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
          java:jboss/exported/aveksa/wpServer/ResourcePvt_EJB!com.workpoint.server.pojo.ResourcePvt
  
  2016-08-01 15:16:01,093 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named WorkItemPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:app/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:module/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:jboss/exported/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvt
          java:global/aveksa/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
          java:app/wpServer/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
          java:module/WorkItemPvt_EJB!com.workpoint.server.pojo.WorkItemPvtLocal
  
  2016-08-01 15:16:01,094 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named SchemaUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:app/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:module/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvtLocal
          java:global/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:app/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:module/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
          java:jboss/exported/aveksa/wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.pojo.SchemaUpdatePvt
  
  2016-08-01 15:16:01,095 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named JobUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:app/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:module/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvtLocal
          java:global/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:app/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:module/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
          java:jboss/exported/aveksa/wpServer/JobUpdatePvt_EJB!com.workpoint.server.pojo.JobUpdatePvt
  
  2016-08-01 15:16:01,096 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named WorkItemUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:app/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:jboss/exported/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvt
          java:global/aveksa/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
          java:app/wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
          java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.pojo.WorkItemUpdatePvtLocal
  
  2016-08-01 15:16:01,098 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named GroupTypePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:app/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:module/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvtLocal
          java:global/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:app/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:module/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
          java:jboss/exported/aveksa/wpServer/GroupTypePvt_EJB!com.workpoint.server.pojo.GroupTypePvt
  
  2016-08-01 15:16:01,098 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MonitorPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:app/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:module/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:jboss/exported/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvt
          java:global/aveksa/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
          java:app/wpServer/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
          java:module/MonitorPvt_EJB!com.workpoint.server.pojo.MonitorPvtLocal
  
  2016-08-01 15:16:01,099 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named UniqueIDPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:app/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:module/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:jboss/exported/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvt
          java:global/aveksa/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
          java:app/wpServer/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
          java:module/UniqueIDPvt_EJB!com.workpoint.server.pojo.UniqueIDPvtLocal
  
  2016-08-01 15:16:01,100 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named FormPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:app/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:jboss/exported/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvt
          java:global/aveksa/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
          java:app/wpServer/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
          java:module/FormPvt_EJB!com.workpoint.server.pojo.FormPvtLocal
  
  2016-08-01 15:16:01,101 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named ProcessPvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:app/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:module/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:jboss/exported/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvt
          java:global/aveksa/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
          java:app/wpServer/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
          java:module/ProcessPvt_EJB!com.workpoint.server.pojo.ProcessPvtLocal
  
  2016-08-01 15:16:01,101 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named FormUpdatePvt_EJB in deployment unit subdeployment "wpServer.jar" of deployment "aveksa.ear" are as follows:
  
          java:global/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:app/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:module/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvtLocal
          java:global/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:app/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:module/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
          java:jboss/exported/aveksa/wpServer/FormUpdatePvt_EJB!com.workpoint.server.pojo.FormUpdatePvt
  
  2016-08-01 15:16:01,257 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment aveksa.war
  2016-08-01 15:16:01,548 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
  2016-08-01 15:16:01,549 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: aveksa.ear
  2016-08-01 15:16:01,712 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.2.6 (Final)
  2016-08-01 15:16:01,729 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:16:01,744 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment aveksa.ear
  2016-08-01 15:16:06,377 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'ServerAutomatedActivityMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:06,390 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'UtilityMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:06,401 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) JBAS014142: Started message driven bean 'EventMDBean' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:08,765 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=com.aveksa.server.ws.AccessRequestWebServiceProvider
  address=http://localhost:8080/server/AccessRequestWebService/AccessRequestWebServiceProvider
  implementor=com.aveksa.server.ws.AccessRequestWebServiceProvider
  serviceName={http://aveksa.com/services/Global}AccessRequestWebService
  portName={http://aveksa.com/services/Global}AccessRequestWebServicePort
  annotationWsdlLocation=null
  wsdlLocationOverride=null
  mtomEnabled=false
  2016-08-01 15:16:09,521 ERROR [stderr] (MSC service thread 1-3) log4j:WARN No appenders could be found for logger (com.aveksa.server.ws.AccessRequestWebServiceProvider).
  2016-08-01 15:16:09,522 ERROR [stderr] (MSC service thread 1-3) log4j:WARN Please initialize the log4j system properly.
  2016-08-01 15:16:09,628 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://aveksa.com/services/Global}AccessRequestWebService from class com.aveksa.server.ws.AccessRequestWebService
  2016-08-01 15:16:11,255 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/server/AccessRequestWebService/AccessRequestWebServiceProvider
  2016-08-01 15:16:11,475 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-3) JBWS024074: WSDL published to: file:/home/oracle/wildfly-8.2.0.Final/standalone/data/wsdl/aveksa.ear/server.jar/AccessRequestWebService.wsdl
  2016-08-01 15:16:11,486 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015539: Starting service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  2016-08-01 15:16:11,500 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'SubscriberMDB' with 'hornetq-ra.rar' resource adapter
  2016-08-01 15:16:47,493 INFO [org.xnio] (Thread-132) XNIO version 3.2.2.Final
  2016-08-01 15:16:47,522 INFO [org.xnio.nio] (Thread-132) XNIO NIO Implementation Version 3.2.2.Final
  2016-08-01 15:16:47,748 INFO [org.jboss.remoting] (Thread-132) JBoss Remoting version (unknown)
  2016-08-01 15:16:52,559 INFO [org.jboss.ejb.client] (MSC service thread 1-3) JBoss EJB Client version 2.0.1.Final
  2016-08-01 15:18:11,956 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (MSC service thread 1-3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:347)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:354)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.access$200(LocalManagedConnectionFactory.java:63)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:263)
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:254)
          at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_79]
          at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_79]
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:253)
          at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:1166)
          at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:446)
          at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:461)
          at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:433)
          at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:379)
          at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:421)
          at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:515)
          at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
          at com.aveksa.server.utils.PerfStatUtil.getNewPerfConnection(PerfStatUtil.java:100) [server.jar:]
          at com.aveksa.server.utils.PerfStatUtil.hasConnection(PerfStatUtil.java:113) [server.jar:]
          at com.aveksa.server.runtime.AveksaSystem.initialize(AveksaSystem.java:333) [server.jar:]
          at com.aveksa.init.Startup.init(Startup.java:41) [classes:]
          at com.aveksa.gui.core.ACMFramework.init(ACMFramework.java:84) [classes:]
          at com.aveksa.gui.core.ACMFramework.initInstance(ACMFramework.java:73) [classes:]
          at com.aveksa.init.InitServlet.init(InitServlet.java:42) [classes:]
          at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.handle(RunAsLifecycleInterceptor.java:66)
          at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:77)
          at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:220) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:125) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:508) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
          at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:88)
          at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
          at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
  Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
  
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:573) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:431) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:366) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:752) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:366) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) [ojdbc5.jar:11.2.0.2.0]
          at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521) [ojdbc5.jar:11.2.0.2.0]
          at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:322)
          ... 36 more
  
  2016-08-01 15:18:14,310 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /aveksa
  2016-08-01 15:18:14,436 INFO [stdout] (MSC service thread 1-4) 2016-08-01 15:18:14,434 [MSC service thread 1-4] INFO com.workpoint.servlet.client.WpClientServlet - Loaded properties from vfs:/content/aveksa.ear/APP-INF/lib/acmConfig.jar/workpoint-server.properties
  2016-08-01 15:18:14,438 INFO [stdout] (MSC service thread 1-4) 2016-08-01 15:18:14,438 [MSC service thread 1-4] INFO com.workpoint.servlet.client.WpClientServlet - PRODUCT = Workpoint; VERSION = 3.5; BUILD = 20101207.P024; BUILD DATE = February 21, 2014
  2016-08-01 15:18:14,444 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /wp
  2016-08-01 15:18:14,661 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:18:14,661 [MSC service thread 1-1] INFO com.workpoint.queue.WpQMonitors - PRODUCT = Workpoint; VERSION = 3.5; BUILD = 20101207.P024; BUILD DATE = February 21, 2014
  2016-08-01 15:18:14,662 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:18:14,662 [MSC service thread 1-1] INFO com.workpoint.queue.WpQMonitors - Loaded queue monitor configuration from vfs:/content/aveksa.ear/APP-INF/lib/acmConfig.jar/wpqmonitor.xml
  2016-08-01 15:18:14,682 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /wpQMonitor
  2016-08-01 15:18:14,839 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /wpConsole
  2016-08-01 15:18:15,007 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "aveksa.ear" (runtime-name : "aveksa.ear")
  2016-08-01 15:18:15,070 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
  2016-08-01 15:18:15,070 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
  2016-08-01 15:18:15,071 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 186025ms - Started 3171 of 3261 services (172 services are lazy, passive or on-demand)
  2016-08-01 15:18:19,805 INFO [stdout] (Timer-5) 2016-08-01 15:18:19,803 [Timer-5] INFO com.workpoint.server.ServerProperties - ServerProperties.setProperty() invoked for property= calculated.db.offset.millis, value=1375
  2016-08-01 15:18:20,179 INFO [stdout] (Timer-4) 2016-08-01 15:18:20,151 [Timer-4] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1#42 successfully started.
  2016-08-01 15:18:20,199 INFO [stdout] (Timer-6) 2016-08-01 15:18:20,187 [Timer-6] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1#44 successfully started.
  2016-08-01 15:18:20,200 INFO [stdout] (Timer-5) 2016-08-01 15:18:20,151 [Timer-5] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1#43 successfully started.
  2016-08-01 15:20:32,828 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = aveksa.ear_oracle.jdbc.OracleDriver_11_2
  2016-08-01 15:20:32,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wpConsole
  2016-08-01 15:20:32,900 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017535: Unregistered web context: /wpQMonitor
  2016-08-01 15:20:32,906 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,906 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor actionq#ActionQ1#42
  2016-08-01 15:20:32,952 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,952 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor actionq#ActionQ1 shut down.
  2016-08-01 15:20:32,953 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:32,953 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor alertq#AlertQ1#43
  2016-08-01 15:20:33,001 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,001 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor alertq#AlertQ1 shut down.
  2016-08-01 15:20:33,002 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,002 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - A request has been received to shut down the Workpoint QMonitor jobq#JobQ1#44
  2016-08-01 15:20:33,053 INFO [stdout] (MSC service thread 1-1) 2016-08-01 15:20:33,052 [MSC service thread 1-1] INFO com.workpoint.queue.core.QMonitor - QMonitor jobq#JobQ1 shut down.
  2016-08-01 15:20:33,083 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017535: Unregistered web context: /wp
  2016-08-01 15:20:33,118 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /aveksa
  2016-08-01 15:20:34,129 INFO [org.jboss.as.webservices] (MSC service thread 1-2) JBAS015540: Stopping service jboss.ws.endpoint."aveksa.ear"."server.jar"."com.aveksa.server.ws.AccessRequestWebServiceProvider"
  Like • Show 0 Likes0
  Actions

I can not deploy ear using customizeACM

Outcomes

Related Content

Recommended Content