Symantec IGA

  • 1.  Unable to launch IDM Management Console

    Posted Jul 15, 2015 01:20 PM

    Hi,

    Installed CA Identity Manager 12.6 with JBoss 6.3 GA application server. There are no errrors in both installations.

     

    Only one warning for JBoss installation "Bean.xml not found"

     

    But when tried to launch the management console, it throws error stating "No connection found". When tired with the local host ip then the message will be " HttP 404 Not found".

     

    I am able open JBoss console with out issues. All JAR and WAR files were deployed successfully. All CA services are up and running.


    Can anyone help me to fix this issue?



  • 2.  Re: Unable to launch IDM Management Console
    Best Answer

    Broadcom Employee
    Posted Jul 16, 2015 02:43 AM

    For Jboss 6.3 in the application server log you should see:

    JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started

     

    The rest of that line is important.

     

    basically we need to see the log, can you attach it here. if this is something we can read and make a suggestion on we will, but you may need to open a support issue.

     

    Thanks,

    Bill Patton



  • 3.  Re: Unable to launch IDM Management Console

    Posted Jul 16, 2015 03:45 AM

    Hi Bill,

     

    Thank you. Please find the below JBoss log file for your verification.

     

    Thanks,

    Murali

     

    13:05:14,601 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1

    13:05:16,052 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

    13:05:16,270 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting

    13:05:16,286 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:

      awt.toolkit = sun.awt.windows.WToolkit

      file.encoding = Cp1252

      file.encoding.pkg = sun.io

      file.separator = \

      java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

      java.awt.printerjob = sun.awt.windows.WPrinterJob

      java.class.path = C:\JBoss\jboss-eap-6.3\jboss-modules.jar

      java.class.version = 51.0

      java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\endorsed

      java.ext.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

      java.home = C:\Program Files\Java\jdk1.7.0\jre

      java.io.tmpdir = C:\Users\478993\AppData\Local\Temp\2\

      java.library.path = C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.7.0;C:\Program Files\HP\NCU;C:\svn;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Windows Imaging\;D:\ESecurity_vss\svn\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\PROGRA~1\CA\SHARED~1\CAM\bin;H:\Program Files\CA\Directory\dxserver\bin;.

      java.net.preferIPv4Stack = true

      java.runtime.name = Java(TM) SE Runtime Environment

      java.runtime.version = 1.7.0-b147

      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

      java.vm.info = mixed mode

      java.vm.name = Java HotSpot(TM) Client 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 = 21.0-b17

      javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

      javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

      javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

      javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

      javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

      javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

      javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

      javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

      javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

      javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

      jboss.bind.address = 0.0.0.0

      jboss.home.dir = C:\JBoss\jboss-eap-6.3

      jboss.host.name = ctsinnvlsdsg

      jboss.modules.dir = C:\JBoss\jboss-eap-6.3\modules

      jboss.modules.policy-permissions = true

      jboss.modules.system.pkgs = org.jboss.byteman

      jboss.node.name = ctsinnvlsdsg

      jboss.qualified.host.name = ctsinnvlsdsg

      jboss.server.base.dir = C:\JBoss\jboss-eap-6.3\standalone

      jboss.server.config.dir = C:\JBoss\jboss-eap-6.3\standalone\configuration

      jboss.server.data.dir = C:\JBoss\jboss-eap-6.3\standalone\data

      jboss.server.deploy.dir = C:\JBoss\jboss-eap-6.3\standalone\data\content

      jboss.server.log.dir = C:\JBoss\jboss-eap-6.3\standalone\log

      jboss.server.name = ctsinnvlsdsg

      jboss.server.persist.config = true

      jboss.server.temp.dir = C:\JBoss\jboss-eap-6.3\standalone\tmp

      line.separator =

     

     

      logging.configuration = file:C:\JBoss\jboss-eap-6.3\standalone/configuration/logging.properties

      module.path = C:\JBoss\jboss-eap-6.3\modules

      nete.j2ee.vendor = jboss

      org.jboss.boot.log.file = C:\JBoss\jboss-eap-6.3\standalone\log\server.log

      org.jboss.resolver.warning = true

      org.xml.sax.driver = __redirected.__XMLReaderFactory

      os.arch = x86

      os.name = Windows Server 2008

      os.version = 6.0

      path.separator = ;

      program.name = standalone.bat

      sun.arch.data.model = 32

      sun.boot.class.path = C:\Program Files\Java\jdk1.7.0\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0\jre\classes

      sun.boot.library.path = C:\Program Files\Java\jdk1.7.0\jre\bin

      sun.cpu.endian = little

      sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

      sun.desktop = windows

      sun.io.unicode.encoding = UnicodeLittle

      sun.java.command = C:\JBoss\jboss-eap-6.3\jboss-modules.jar -mp C:\JBoss\jboss-eap-6.3\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\JBoss\jboss-eap-6.3 -c standalone-full.xml -b 0.0.0.0 -Dnete.j2ee.vendor=jboss

      sun.java.launcher = SUN_STANDARD

      sun.jnu.encoding = Cp1252

      sun.management.compiler = HotSpot Client Compiler

      sun.os.patch.level = Service Pack 2

      user.country = US

      user.dir = C:\JBoss\jboss-eap-6.3\bin

      user.home = C:\Users\478993

      user.language = en

      user.name = 478993

      user.script =

      user.timezone = Asia/Calcutta

      user.variant =

    13:05:16,317 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.policy-permissions=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=C:\JBoss\jboss-eap-6.3\standalone\log\server.log -Dlogging.configuration=file:C:\JBoss\jboss-eap-6.3\standalone/configuration/logging.properties

    13:05:23,556 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found castylesr5.1.1.ear in deployment directory. To trigger deployment create a file called castylesr5.1.1.ear.dodeploy

    13:05:23,556 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_im.ear in deployment directory. To trigger deployment create a file called iam_im.ear.dodeploy

    13:05:23,618 INFO  [org.xnio] (MSC service thread 1-17) XNIO Version 3.0.10.GA-redhat-1

    13:05:23,634 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

    13:05:23,649 INFO  [org.xnio.nio] (MSC service thread 1-17) XNIO NIO Implementation Version 3.0.10.GA-redhat-1

    13:05:23,774 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.

    13:05:23,774 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.

    13:05:23,774 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 35) JBAS016300: Activating JacORB Subsystem

    13:05:23,774 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 45) JBAS011800: Activating Naming Subsystem

    13:05:23,774 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem

    13:05:23,790 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension

    13:05:23,790 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 41) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

    13:05:23,790 INFO  [org.jboss.remoting] (MSC service thread 1-17) JBoss Remoting version (unknown)

    13:05:23,821 INFO  [org.jboss.as.security] (MSC service thread 1-9) JBAS013170: Current PicketBox version=4.0.19.SP8-redhat-1

    13:05:23,836 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-34) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)

    13:05:24,008 INFO  [org.jboss.as.naming] (MSC service thread 1-46) JBAS011802: Starting Naming Service

    13:05:24,008 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-20) JBAS015400: Bound mail session [java:/Mail]

    13:05:24,008 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-26) JBAS015400: Bound mail session [java:jboss/mail/Default]

    13:05:24,024 INFO  [org.jboss.jaxr] (MSC service thread 1-4) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

    13:05:24,273 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-17) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080

    13:05:24,273 INFO  [org.apache.coyote.ajp] (MSC service thread 1-29) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009

    13:05:24,273 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-17) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080

    13:05:24,273 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

    13:05:24,289 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=C:\JBoss\jboss-eap-6.3\standalone\data\messagingjournal,bindingsDirectory=C:\JBoss\jboss-eap-6.3\standalone\data\messagingbindings,largeMessagesDirectory=C:\JBoss\jboss-eap-6.3\standalone\data\messaginglargemessages,pagingDirectory=C:\JBoss\jboss-eap-6.3\standalone\data\messagingpaging)

    13:05:24,289 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock

    13:05:24,336 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal

    13:05:24,382 WARN  [jacorb.codeset] (MSC service thread 1-30) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

    13:05:24,617 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

    13:05:24,617 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

    13:05:24,617 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-28) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

    13:05:24,633 INFO  [org.jboss.as.jacorb] (MSC service thread 1-30) JBAS016330: CORBA ORB Service started

    13:05:24,649 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)

    13:05:24,742 INFO  [org.jboss.as.jacorb] (MSC service thread 1-11) JBAS016328: CORBA Naming Service started

    13:05:24,742 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)

    13:05:25,522 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 0.0.0.0:5445 for CORE protocol

    13:05:25,538 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 0.0.0.0:5455 for CORE protocol

    13:05:25,538 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

    13:05:25,538 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.3.20.Final (2.3.20, 123) [e856ba74-2af5-11e5-80e0-8743a9b723c2]

    13:05:25,569 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

    13:05:25,585 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 69) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpUtilQueue

    13:05:25,585 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 69) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpUtilQueue

    13:05:25,585 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 69) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpUtilQueue

    13:05:25,600 INFO  [org.hornetq.jms.server] (ServerService Thread Pool -- 68) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "CTSINNVLSDSG". If this new address is incorrect please manually configure the connector to use the proper one.

    13:05:25,600 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 68) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

    13:05:25,600 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 67) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.RuntimeStatusDetailQueue

    13:05:25,600 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/RuntimeStatusDetailQueue

    13:05:25,600 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/RuntimeStatusDetailQueue

    13:05:25,600 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221003: trying to deploy queue jms.topic.testTopic

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:/topic/test

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

    13:05:25,834 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpEventQueue

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpEventQueue

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpEventQueue

    13:05:25,834 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpServAutoActQueue

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpServAutoActQueue

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpServAutoActQueue

    13:05:25,834 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/wpConnectionFactory

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/jms/wpConnectionFactory

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.DLQ

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.com.netegrity.ims.msg.queue

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/com.netegrity.ims.msg.queue

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/com.netegrity.ims.msg.queue

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 59) HQ221003: trying to deploy queue jms.topic.iam.im.jms.topic.ServerCommandTopic

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/topic/ServerCommandTopic

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/topic/iam/im/jms/topic/ServerCommandTopic

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.iam_imAnalyticsNotificationQueue

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/iam/im/jms/queue/analytics/AnalyticsNotificationQueue

    13:05:25,850 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.testQueue

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/queue/test

    13:05:25,850 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

    13:05:25,865 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-48) JBAS010406: Registered connection factory java:/JmsXA

    13:05:25,912 INFO  [org.hornetq.ra] (MSC service thread 1-48) HornetQ resource adaptor started

    13:05:25,912 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-48) IJ020002: Deployed: file://RaActivatorhornetq-ra

    13:05:25,912 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-17) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/reportsnapshot]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-10) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/WPDS]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-11) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/idm]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-29) JBAS010400: Bound data source [java:/iam/im/jdbc/auditDbDataSource]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-42) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/objectstore]

    13:05:26,271 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-30) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/archive]

    13:05:26,489 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-44) JBAS015012: Started FileSystemDeploymentService for directory C:\JBoss\jboss-eap-6.3\standalone\deployments

    13:05:26,489 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-34) JBAS015876: Starting deployment of "castylesr5.1.1.ear" (runtime-name: "castylesr5.1.1.ear")

    13:05:26,489 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015876: Starting deployment of "iam_im.ear" (runtime-name: "iam_im.ear")

    13:05:26,505 INFO  [org.jboss.as.remoting] (MSC service thread 1-17) JBAS017100: Listening on 127.0.0.1:9999

    13:05:26,505 INFO  [org.jboss.as.remoting] (MSC service thread 1-24) JBAS017100: Listening on 0.0.0.0:4447

    13:05:26,567 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-42) JBAS015876: Starting deployment of "null" (runtime-name: "castylesr5.1.1.war")

    13:05:26,755 INFO  [org.jboss.ws.common.management] (MSC service thread 1-19) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3

    13:05:27,347 INFO  [org.jboss.web] (ServerService Thread Pool -- 57) JBAS018210: Register web context: /castylesr5.1.1

    13:05:45,256 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jaxb-xjc__V2.0.5.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,256 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry scala-library__V2.8.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry activation__V1.0.2.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry annotations.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-collections__V3.2.1.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-lang__V2.3.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-logging__V1.1.1.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-pool__V1.5.5.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,272 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jsafeFIPS__V4.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,288 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jsafeJCEFIPS__V4.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,288 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry log4j__V1.2.16.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/cacommons.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,303 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jaxb-api.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jaxb-impl__V2.0.5.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,303 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jsr173_1.0_api.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jaxb-impl__V2.0.5.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,303 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry jaxb1-impl.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jaxb-impl__V2.0.5.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,303 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-dbcp-1.4.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jiam.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,303 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-pool__V1.5.5.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jiam.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,319 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry cahsqldb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jiam.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,319 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry poi-3.8-20120326.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jide-grids.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,334 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry poi-ooxml-3.8-20120326.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jide-grids.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,334 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry lucene-core-3.5.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/jide-grids.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,459 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry commons-validator.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/struts.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/jmxri.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/jmxtools.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/log4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/mail.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/bsf.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/js.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,522 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015960: Class Path entry APP-INF/lib/activation.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/wpMonitor.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-29) JBAS015876: Starting deployment of "null" (runtime-name: "manage_redirect.war")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-33) JBAS015876: Starting deployment of "null" (runtime-name: "custom")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015876: Starting deployment of "null" (runtime-name: "iam_im_wpServer.jar")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-12) JBAS015876: Starting deployment of "null" (runtime-name: "redirect.war")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-36) JBAS015876: Starting deployment of "null" (runtime-name: "policyserver.rar")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "null" (runtime-name: "ca-nim-sm.war")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015876: Starting deployment of "null" (runtime-name: "workflow.rar")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015876: Starting deployment of "null" (runtime-name: "iam_im_identityminder_ejb.jar")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-30) JBAS015876: Starting deployment of "null" (runtime-name: "user_console.war")

    13:05:45,568 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015876: Starting deployment of "null" (runtime-name: "management_console.war")

    13:05:45,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_wpServer.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_wpServer.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,600 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_wpServer.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,615 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_wpServer.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,615 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_wpServer.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,615 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/workflow.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,615 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/workflow.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,631 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/workflow.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,631 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/workflow.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,631 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-9) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/workflow.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,646 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-43) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/policyserver.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,646 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-43) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/policyserver.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,646 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-43) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/policyserver.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,646 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-43) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/policyserver.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,662 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-43) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/policyserver.rar  does not point to a valid jar for a Class-Path reference.

    13:05:45,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_identityminder_ejb.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_identityminder_ejb.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_identityminder_ejb.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_identityminder_ejb.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,678 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/iam_im_identityminder_ejb.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:45,849 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry jaxb-api__V2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war/WEB-INF/lib/roledefgen.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,849 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry jaxb-impl__V2.0.5.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war/WEB-INF/lib/roledefgen.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,849 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry cacommons.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war/WEB-INF/lib/roledefgen.jar  does not point to a valid jar for a Class-Path reference.

    13:05:45,849 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry jiam.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war/WEB-INF/lib/roledefgen.jar  does not point to a valid jar for a Class-Path reference.

    13:05:49,531 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015850: /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/ca-nim-sm.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for top level deployments.

    13:05:50,779 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-48) JBAS015960: Class Path entry library/cryptojFIPS.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/user_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:50,779 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-48) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/user_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:50,779 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-48) JBAS015960: Class Path entry library/jsp-2.0.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/user_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:50,779 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-48) JBAS015960: Class Path entry identityminder_ejb.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/user_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:50,795 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-48) JBAS015960: Class Path entry wpServer.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/user_console.war  does not point to a valid jar for a Class-Path reference.

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,982 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$Text' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:50,997 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyReader'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,013 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$App' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General' for service type 'javax.ws.rs.ext.MessageBodyWriter'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromStringEnum' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeValueOf' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$TypeFromString' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$StringConstructor' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,029 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.StringReaderProviders$DateProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,044 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-35) JBAS015893: Encountered invalid class name 'com.sun.jersey.server.impl.model.parameter.multivalued.JAXBStringReaderProviders$RootElementProvider' for service type 'com.sun.jersey.spi.StringReaderProvider'

    13:05:51,621 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-46) JBAS018568: Deployment "deployment.iam_im.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.

    13:05:51,621 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-46) JBAS018568: Deployment "deployment.iam_im.ear" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.

    13:05:51,621 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-46) JBAS018567: Deployment "deployment.iam_im.ear" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.

    13:05:51,621 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-46) JBAS018567: Deployment "deployment.iam_im.ear" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.

    13:05:51,699 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-22) JBAS018568: Deployment "deployment.iam_im.ear.config" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.

    13:05:51,699 WARN  [org.jboss.as.dependency.unsupported] (MSC service thread 1-22) JBAS018568: Deployment "deployment.iam_im.ear.config" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.

    13:05:51,699 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-22) JBAS018567: Deployment "deployment.iam_im.ear.config" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.

    13:05:51,699 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-22) JBAS018567: Deployment "deployment.iam_im.ear.config" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.

    13:05:52,885 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named WorkFlowCallBackEJB in deployment unit subdeployment "iam_im_identityminder_ejb.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBackHome

      java:app/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBackHome

      java:module/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBackHome

      java:jboss/exported/iam_im/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBackHome

      java:global/iam_im/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBack

      java:app/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBack

      java:module/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBack

      java:jboss/exported/iam_im/iam_im_identityminder_ejb/WorkFlowCallBackEJB!com.netegrity.ejb.workflow.callbacks.WorkFlowCallBack

     

     

    13:05:53,509 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named UtilityPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvt

      java:app/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvt

      java:module/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvt

      java:jboss/exported/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvt

      java:global/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocal

      java:app/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocal

      java:module/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocal

      java:global/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocalHome

      java:app/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocalHome

      java:module/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtLocalHome

      java:global/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtHome

      java:app/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtHome

      java:module/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/UtilityPvt_EJB!com.workpoint.server.ejb.UtilityPvtHome

     

     

    13:05:53,525 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named GroupTypeUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocalHome

      java:app/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocalHome

      java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvt

      java:app/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvt

      java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvt

      java:global/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtHome

      java:app/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtHome

      java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocal

      java:app/iam_im_wpServer/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocal

      java:module/GroupTypeUpdatePvt_EJB!com.workpoint.server.ejb.GroupTypeUpdatePvtLocal

     

     

    13:05:53,540 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named PriorityUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvt

      java:app/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvt

      java:module/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvt

      java:global/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocalHome

      java:app/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocalHome

      java:module/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtHome

      java:app/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtHome

      java:module/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocal

      java:app/iam_im_wpServer/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocal

      java:module/PriorityUpdatePvt_EJB!com.workpoint.server.ejb.PriorityUpdatePvtLocal

     

     

    13:05:53,556 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named MailUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocalHome

      java:app/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocalHome

      java:module/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvt

      java:app/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvt

      java:module/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvt

      java:global/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtHome

      java:app/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtHome

      java:module/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocal

      java:app/iam_im_wpServer/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocal

      java:module/MailUpdatePvt_EJB!com.workpoint.server.ejb.MailUpdatePvtLocal

     

     

    13:05:53,571 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named TablePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtHome

      java:app/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtHome

      java:module/TablePvt_EJB!com.workpoint.server.ejb.TablePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtHome

      java:global/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocalHome

      java:app/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocalHome

      java:module/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocalHome

      java:global/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocal

      java:app/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocal

      java:module/TablePvt_EJB!com.workpoint.server.ejb.TablePvtLocal

      java:global/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvt

      java:app/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvt

      java:module/TablePvt_EJB!com.workpoint.server.ejb.TablePvt

      java:jboss/exported/iam_im/iam_im_wpServer/TablePvt_EJB!com.workpoint.server.ejb.TablePvt

     

     

    13:05:53,571 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named UniqueIDUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvt

      java:app/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvt

      java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvt

      java:global/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtHome

      java:app/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtHome

      java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocalHome

      java:app/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocalHome

      java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocal

      java:app/iam_im_wpServer/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocal

      java:module/UniqueIDUpdatePvt_EJB!com.workpoint.server.ejb.UniqueIDUpdatePvtLocal

     

     

    13:05:53,587 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named HolCalPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocalHome

      java:app/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocalHome

      java:module/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocalHome

      java:global/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocal

      java:app/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocal

      java:module/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtLocal

      java:global/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtHome

      java:app/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtHome

      java:module/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvtHome

      java:global/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvt

      java:app/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvt

      java:module/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvt

      java:jboss/exported/iam_im/iam_im_wpServer/HolCalPvt_EJB!com.workpoint.server.ejb.HolCalPvt

     

     

    13:05:53,603 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named MailPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvt

      java:app/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvt

      java:module/MailPvt_EJB!com.workpoint.server.ejb.MailPvt

      java:jboss/exported/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvt

      java:global/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocalHome

      java:app/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocalHome

      java:module/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocalHome

      java:global/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocal

      java:app/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocal

      java:module/MailPvt_EJB!com.workpoint.server.ejb.MailPvtLocal

      java:global/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtHome

      java:app/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtHome

      java:module/MailPvt_EJB!com.workpoint.server.ejb.MailPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/MailPvt_EJB!com.workpoint.server.ejb.MailPvtHome

     

     

    13:05:53,618 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named SchemaPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocal

      java:app/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocal

      java:module/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocal

      java:global/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtHome

      java:app/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtHome

      java:module/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtHome

      java:global/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocalHome

      java:app/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocalHome

      java:module/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvtLocalHome

      java:global/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvt

      java:app/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvt

      java:module/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvt

      java:jboss/exported/iam_im/iam_im_wpServer/SchemaPvt_EJB!com.workpoint.server.ejb.SchemaPvt

     

     

    13:05:53,634 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named CompletionCodeUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocal

      java:app/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocal

      java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtHome

      java:app/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtHome

      java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocalHome

      java:app/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocalHome

      java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvt

      java:app/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvt

      java:module/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/CompletionCodeUpdatePvt_EJB!com.workpoint.server.ejb.CompletionCodeUpdatePvt

     

     

    13:05:53,649 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ProfileUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocalHome

      java:app/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocalHome

      java:module/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvt

      java:app/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvt

      java:module/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvt

      java:global/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocal

      java:app/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocal

      java:module/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtHome

      java:app/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtHome

      java:module/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ProfileUpdatePvt_EJB!com.workpoint.server.ejb.ProfileUpdatePvtHome

     

     

    13:05:53,665 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ScriptPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocal

      java:app/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocal

      java:module/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocal

      java:global/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtHome

      java:app/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtHome

      java:module/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtHome

      java:global/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvt

      java:app/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvt

      java:module/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvt

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvt

      java:global/iam_im/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocalHome

      java:app/iam_im_wpServer/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocalHome

      java:module/ScriptPvt_EJB!com.workpoint.server.ejb.ScriptPvtLocalHome

     

     

    13:05:53,681 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named AlertPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvt

      java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvt

      java:module/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvt

      java:jboss/exported/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvt

      java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtHome

      java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtHome

      java:module/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtHome

      java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocalHome

      java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocalHome

      java:module/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocalHome

      java:global/iam_im/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocal

      java:app/iam_im_wpServer/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocal

      java:module/AlertPvt_EJB!com.workpoint.server.ejb.AlertPvtLocal

     

     

    13:05:53,696 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named HolCalUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtHome

      java:app/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtHome

      java:module/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocal

      java:app/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocal

      java:module/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvt

      java:app/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvt

      java:module/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvt

      java:global/iam_im/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocalHome

      java:app/iam_im_wpServer/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocalHome

      java:module/HolCalUpdatePvt_EJB!com.workpoint.server.ejb.HolCalUpdatePvtLocalHome

     

     

    13:05:53,712 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named CategoryUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtHome

      java:app/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtHome

      java:module/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvt

      java:app/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvt

      java:module/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvt

      java:global/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocal

      java:app/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocal

      java:module/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocalHome

      java:app/iam_im_wpServer/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocalHome

      java:module/CategoryUpdatePvt_EJB!com.workpoint.server.ejb.CategoryUpdatePvtLocalHome

     

     

    13:05:53,712 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ProcessUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvt

      java:app/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvt

      java:module/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvt

      java:global/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocalHome

      java:app/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocalHome

      java:module/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtHome

      java:app/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtHome

      java:module/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocal

      java:app/iam_im_wpServer/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocal

      java:module/ProcessUpdatePvt_EJB!com.workpoint.server.ejb.ProcessUpdatePvtLocal

     

     

    13:05:53,727 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named CategoryPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocal

      java:app/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocal

      java:module/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocal

      java:global/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvt

      java:app/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvt

      java:module/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvt

      java:jboss/exported/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvt

      java:global/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtHome

      java:app/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtHome

      java:module/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtHome

      java:global/iam_im/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocalHome

      java:app/iam_im_wpServer/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocalHome

      java:module/CategoryPvt_EJB!com.workpoint.server.ejb.CategoryPvtLocalHome

     

     

    13:05:53,743 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ScriptExecutePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocalHome

      java:app/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocalHome

      java:module/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocalHome

      java:global/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtHome

      java:app/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtHome

      java:module/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtHome

      java:global/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocal

      java:app/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocal

      java:module/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvtLocal

      java:global/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvt

      java:app/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvt

      java:module/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptExecutePvt_EJB!com.workpoint.server.ejb.ScriptExecutePvt

     

     

    13:05:53,743 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named AlertUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocalHome

      java:app/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocalHome

      java:module/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtHome

      java:app/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtHome

      java:module/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvt

      java:app/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvt

      java:module/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvt

      java:global/iam_im/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocal

      java:app/iam_im_wpServer/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocal

      java:module/AlertUpdatePvt_EJB!com.workpoint.server.ejb.AlertUpdatePvtLocal

     

     

    13:05:53,759 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named BusCalUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvt

      java:app/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvt

      java:module/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvt

      java:global/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocal

      java:app/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocal

      java:module/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtHome

      java:app/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtHome

      java:module/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocalHome

      java:app/iam_im_wpServer/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocalHome

      java:module/BusCalUpdatePvt_EJB!com.workpoint.server.ejb.BusCalUpdatePvtLocalHome

     

     

    13:05:53,759 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named TableUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocal

      java:app/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocal

      java:module/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtHome

      java:app/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtHome

      java:module/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvt

      java:app/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvt

      java:module/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvt

      java:global/iam_im/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocalHome

      java:app/iam_im_wpServer/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocalHome

      java:module/TableUpdatePvt_EJB!com.workpoint.server.ejb.TableUpdatePvtLocalHome

     

     

    13:05:53,774 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ScriptUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtHome

      java:app/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtHome

      java:module/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvt

      java:app/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvt

      java:module/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvt

      java:global/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocal

      java:app/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocal

      java:module/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocalHome

      java:app/iam_im_wpServer/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocalHome

      java:module/ScriptUpdatePvt_EJB!com.workpoint.server.ejb.ScriptUpdatePvtLocalHome

     

     

    13:05:53,790 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named BusCalPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvt

      java:app/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvt

      java:module/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvt

      java:jboss/exported/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvt

      java:global/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocal

      java:app/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocal

      java:module/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocal

      java:global/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtHome

      java:app/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtHome

      java:module/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtHome

      java:global/iam_im/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocalHome

      java:app/iam_im_wpServer/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocalHome

      java:module/BusCalPvt_EJB!com.workpoint.server.ejb.BusCalPvtLocalHome

     

     

    13:05:53,790 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ProfilePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtHome

      java:app/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtHome

      java:module/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtHome

      java:global/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvt

      java:app/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvt

      java:module/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvt

      java:global/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocal

      java:app/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocal

      java:module/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocal

      java:global/iam_im/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocalHome

      java:app/iam_im_wpServer/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocalHome

      java:module/ProfilePvt_EJB!com.workpoint.server.ejb.ProfilePvtLocalHome

     

     

    13:05:53,805 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ScriptExecAsyncPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocalHome

      java:app/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocalHome

      java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocalHome

      java:global/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvt

      java:app/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvt

      java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvt

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvt

      java:global/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocal

      java:app/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocal

      java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtLocal

      java:global/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtHome

      java:app/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtHome

      java:module/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ScriptExecAsyncPvt_EJB!com.workpoint.server.ejb.ScriptExecAsyncPvtHome

     

     

    13:05:53,805 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named RulesEnginePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtHome

      java:app/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtHome

      java:module/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtHome

      java:global/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvt

      java:app/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvt

      java:module/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvt

      java:jboss/exported/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvt

      java:global/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocalHome

      java:app/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocalHome

      java:module/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocalHome

      java:global/iam_im/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocal

      java:app/iam_im_wpServer/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocal

      java:module/RulesEnginePvt_EJB!com.workpoint.server.ejb.RulesEnginePvtLocal

     

     

    13:05:53,821 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named CompletionCodePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocalHome

      java:app/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocalHome

      java:module/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocalHome

      java:global/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvt

      java:app/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvt

      java:module/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvt

      java:jboss/exported/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvt

      java:global/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtHome

      java:app/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtHome

      java:module/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtHome

      java:global/iam_im/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocal

      java:app/iam_im_wpServer/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocal

      java:module/CompletionCodePvt_EJB!com.workpoint.server.ejb.CompletionCodePvtLocal

     

     

    13:05:53,821 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ServerConfigPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtHome

      java:app/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtHome

      java:module/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtHome

      java:global/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocal

      java:app/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocal

      java:module/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocal

      java:global/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocalHome

      java:app/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocalHome

      java:module/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvtLocalHome

      java:global/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvt

      java:app/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvt

      java:module/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvt

      java:jboss/exported/iam_im/iam_im_wpServer/ServerConfigPvt_EJB!com.workpoint.server.ejb.ServerConfigPvt

     

     

    13:05:53,837 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named JobPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocal

      java:app/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocal

      java:module/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocal

      java:global/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocalHome

      java:app/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocalHome

      java:module/JobPvt_EJB!com.workpoint.server.ejb.JobPvtLocalHome

      java:global/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtHome

      java:app/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtHome

      java:module/JobPvt_EJB!com.workpoint.server.ejb.JobPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvtHome

      java:global/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvt

      java:app/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvt

      java:module/JobPvt_EJB!com.workpoint.server.ejb.JobPvt

      java:jboss/exported/iam_im/iam_im_wpServer/JobPvt_EJB!com.workpoint.server.ejb.JobPvt

     

     

    13:05:53,837 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named PriorityPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtHome

      java:app/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtHome

      java:module/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtHome

      java:global/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocal

      java:app/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocal

      java:module/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocal

      java:global/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocalHome

      java:app/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocalHome

      java:module/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvtLocalHome

      java:global/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvt

      java:app/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvt

      java:module/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvt

      java:jboss/exported/iam_im/iam_im_wpServer/PriorityPvt_EJB!com.workpoint.server.ejb.PriorityPvt

     

     

    13:05:53,852 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ResourcePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtHome

      java:app/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtHome

      java:module/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtHome

      java:global/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvt

      java:app/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvt

      java:module/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvt

      java:jboss/exported/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvt

      java:global/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocalHome

      java:app/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocalHome

      java:module/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocalHome

      java:global/iam_im/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocal

      java:app/iam_im_wpServer/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocal

      java:module/ResourcePvt_EJB!com.workpoint.server.ejb.ResourcePvtLocal

     

     

    13:05:53,868 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named DataSourcePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtHome

      java:app/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtHome

      java:module/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtHome

      java:global/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocal

      java:app/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocal

      java:module/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocal

      java:global/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocalHome

      java:app/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocalHome

      java:module/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvtLocalHome

      java:global/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvt

      java:app/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvt

      java:module/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvt

      java:jboss/exported/iam_im/iam_im_wpServer/DataSourcePvt_EJB!com.workpoint.server.ejb.DataSourcePvt

     

     

    13:05:53,868 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named SchemaUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvt

      java:app/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvt

      java:module/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvt

      java:global/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocal

      java:app/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocal

      java:module/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtHome

      java:app/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtHome

      java:module/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocalHome

      java:app/iam_im_wpServer/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocalHome

      java:module/SchemaUpdatePvt_EJB!com.workpoint.server.ejb.SchemaUpdatePvtLocalHome

     

     

    13:05:53,883 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named WorkItemPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocal

      java:app/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocal

      java:module/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocal

      java:global/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvt

      java:app/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvt

      java:module/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvt

      java:jboss/exported/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvt

      java:global/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocalHome

      java:app/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocalHome

      java:module/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtLocalHome

      java:global/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtHome

      java:app/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtHome

      java:module/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/WorkItemPvt_EJB!com.workpoint.server.ejb.WorkItemPvtHome

     

     

    13:05:53,883 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named JobUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvt

      java:app/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvt

      java:module/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvt

      java:global/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtHome

      java:app/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtHome

      java:module/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtHome

      java:global/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocalHome

      java:app/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocalHome

      java:module/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocal

      java:app/iam_im_wpServer/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocal

      java:module/JobUpdatePvt_EJB!com.workpoint.server.ejb.JobUpdatePvtLocal

     

     

    13:05:53,899 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named WorkItemUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocalHome

      java:app/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocalHome

      java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvt

      java:app/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvt

      java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvt

      java:global/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocal

      java:app/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocal

      java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtHome

      java:app/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtHome

      java:module/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/WorkItemUpdatePvt_EJB!com.workpoint.server.ejb.WorkItemUpdatePvtHome

     

     

    13:05:53,899 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named GroupTypePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtHome

      java:app/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtHome

      java:module/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtHome

      java:global/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocalHome

      java:app/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocalHome

      java:module/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocalHome

      java:global/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocal

      java:app/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocal

      java:module/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvtLocal

      java:global/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvt

      java:app/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvt

      java:module/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvt

      java:jboss/exported/iam_im/iam_im_wpServer/GroupTypePvt_EJB!com.workpoint.server.ejb.GroupTypePvt

     

     

    13:05:53,915 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named MonitorPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvt

      java:app/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvt

      java:module/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvt

      java:jboss/exported/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvt

      java:global/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtHome

      java:app/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtHome

      java:module/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtHome

      java:global/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocal

      java:app/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocal

      java:module/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocal

      java:global/iam_im/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocalHome

      java:app/iam_im_wpServer/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocalHome

      java:module/MonitorPvt_EJB!com.workpoint.server.ejb.MonitorPvtLocalHome

     

     

    13:05:53,915 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named UniqueIDPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocalHome

      java:app/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocalHome

      java:module/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocalHome

      java:global/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtHome

      java:app/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtHome

      java:module/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtHome

      java:global/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvt

      java:app/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvt

      java:module/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvt

      java:jboss/exported/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvt

      java:global/iam_im/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocal

      java:app/iam_im_wpServer/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocal

      java:module/UniqueIDPvt_EJB!com.workpoint.server.ejb.UniqueIDPvtLocal

     

     

    13:05:53,930 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named FormPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocalHome

      java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocalHome

      java:module/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocalHome

      java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocal

      java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocal

      java:module/FormPvt_EJB!com.workpoint.server.ejb.FormPvtLocal

      java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtHome

      java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtHome

      java:module/FormPvt_EJB!com.workpoint.server.ejb.FormPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvtHome

      java:global/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvt

      java:app/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvt

      java:module/FormPvt_EJB!com.workpoint.server.ejb.FormPvt

      java:jboss/exported/iam_im/iam_im_wpServer/FormPvt_EJB!com.workpoint.server.ejb.FormPvt

     

     

    13:05:53,946 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named FormUpdatePvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvt

      java:app/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvt

      java:module/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvt

      java:jboss/exported/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvt

      java:global/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocalHome

      java:app/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocalHome

      java:module/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocalHome

      java:global/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocal

      java:app/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocal

      java:module/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtLocal

      java:global/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtHome

      java:app/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtHome

      java:module/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/FormUpdatePvt_EJB!com.workpoint.server.ejb.FormUpdatePvtHome

     

     

    13:05:53,946 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-29) JNDI bindings for session bean named ProcessPvt_EJB in deployment unit subdeployment "iam_im_wpServer.jar" of deployment "iam_im.ear" are as follows:

     

     

      java:global/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtHome

      java:app/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtHome

      java:module/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtHome

      java:jboss/exported/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtHome

      java:global/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvt

      java:app/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvt

      java:module/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvt

      java:jboss/exported/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvt

      java:global/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocal

      java:app/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocal

      java:module/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocal

      java:global/iam_im/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocalHome

      java:app/iam_im_wpServer/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocalHome

      java:module/ProcessPvt_EJB!com.workpoint.server.ejb.ProcessPvtLocalHome

     

     

    13:05:53,977 WARN  [org.jboss.weld.deployer] (MSC service thread 1-30) JBAS016012: Deployment deployment "iam_im.ear" contains CDI annotations but beans.xml was not found.

    13:05:55,880 WARN  [ims.tmt.CreateDatabaseSchema] (MSC service thread 1-31) ****** Schema for: Workpoint is up to date.

    13:05:59,999 WARN  [ims.default] (ServerService Thread Pool -- 81) CA IAM Framework Server

    13:05:59,999 WARN  [ims.default] (ServerService Thread Pool -- 81) Copyright 2000 - 2013 CA. All Rights Reserved

    13:06:00,014 WARN  [ims.default] (ServerService Thread Pool -- 81) ################################################

    13:06:00,014 WARN  [ims.default] (ServerService Thread Pool -- 81) # IAM Framework 200.1.04.0.425

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) ################################################

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) ################################################

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) # CA Identity Manager 12.6.05.0.386

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) ################################################

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) ---- CA IAM FW Startup Sequence Initiated. ----

    13:06:00,030 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 1 : Attempting to start ServiceLocator.

    13:06:00,482 WARN  [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 81) ****** Schema for: Task Persistence is up to date.

    13:06:00,498 WARN  [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 81) ****** Schema for: Archive is up to date.

    13:06:00,638 WARN  [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 81) ****** Schema for: Auditing is up to date.

    13:06:00,685 WARN  [ims.tmt.CreateDatabaseSchema] (ServerService Thread Pool -- 81) ****** Schema for: Report Snapshot is up to date.

    13:06:00,685 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 2 : Attempting to start PolicyServerService

    13:06:00,685 WARN  [ims.default] (ServerService Thread Pool -- 81) Unlimited Strength Java Crypto Extensions enabled: FALSE

    13:06:00,732 WARN  [ims.default] (ServerService Thread Pool -- 81) Policy Server connection enabled: false

    13:06:00,732 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 3 : Attempting to start ServerCommandService

    13:06:00,779 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 4 : Attempting to start EnvironmentService

    13:06:00,779 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 5 : Attempting to start SecretKeyStore

    13:06:03,914 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 6 : Attempting to start CacheManagerService

    13:06:03,930 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 7 : Attempting to load global plugins.

    13:06:03,930 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 8 : Attempting to start AdaptersConfigService

    13:06:03,930 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 9 : Attempting to start EmailProviderService

    13:06:03,946 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 10 : Attempting to start AuditProviderService

    13:06:03,961 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 11 : Attempting to start RuntimeStatusDetailService

    13:06:03,961 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 12 : Attempting to start PasswordService

    13:06:03,961 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 13 : Attempting to start LogicalAttributeService

    13:06:03,977 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 14 : Attempting to start BLTHService

    13:06:03,977 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 15 : Attempting to start ParticipantResolverService

    13:06:03,977 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 16 : Attempting to start NotificationRuleService

    13:06:03,977 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 17 : Attempting to start EventAdapterService

    13:06:03,977 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 18 : Attempting to start TaskService

    13:06:03,992 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 19 : Attempting to start WorkflowCallbackService

    13:06:03,992 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 20 : Attempting to start WorkflowService

    13:06:03,992 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 21 : Attempting to start TaskStatusNotifyService

    13:06:03,992 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 22 : Attempting to start EventService

    13:06:04,024 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 23 : Attempting to start AdminService

    13:06:04,039 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 24 : Attempting to start GeneralMonitorAdmin

    13:06:04,039 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 25 : Attempting to start GlobalInitializer plug-ins

    13:06:04,039 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 26 : Attempting to start SchedulerService

    13:06:04,351 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 27 : Attempting to start NIMSMIntegrationService

    13:06:04,351 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 28 : Attempting to start environments

    13:06:04,367 WARN  [ims.default] (ServerService Thread Pool -- 81) ** FIPS mode enabled : false

    13:06:04,382 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 29 : Attempting to recover unprocessed events and runtime status details

    13:06:04,382 WARN  [ims.default] (ServerService Thread Pool -- 81) * Startup Step 30 : Attempting to start ApplicationContextInitializer plug-ins

    13:06:04,383 WARN  [ims.default] (ServerService Thread Pool -- 81) ---- CA IAM FW Startup Sequence Complete. ----

    13:06:04,584 WARN  [org.apache.myfaces.shared_impl.util.LocaleUtils] (ServerService Thread Pool -- 81) Locale name in faces-config.xml null or empty, setting locale to default locale : en_US



  • 4.  Re: Unable to launch IDM Management Console

    Broadcom Employee
    Posted Jul 16, 2015 03:57 AM

    you have a lot of message like this:

     

    13:05:45,834 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-17) JBAS015960: Class Path entry library/dom4j.jar in /C:/JBoss/jboss-eap-6.3/standalone/deployments/iam_im.ear/management_console.war  does not point to a valid jar for a Class-Path reference.

     

    Did you copy this jboss install from another server?

     

    You may try deleting your:

    C:\JBoss\jboss-eap-6.3\standalone\tmp

    C:\JBoss\jboss-eap-6.3\standalone\data

    C:\JBoss\jboss-eap-6.3\standalone\work

     

    directories and restarting jboss



  • 5.  Re: Unable to launch IDM Management Console

    Posted Jul 16, 2015 05:17 AM

    Hi Bill,

     

    I downloaded directly from the JBoss. Tried with above mentioned steps. Still facing the same error "Internet Explorer cannopt display this page".

     

    Please find the below JBoss logs.

     

    14:37:45,891 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1

    14:37:46,140 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

    14:37:46,265 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting

    14:37:46,265 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Configured system properties:

      awt.toolkit = sun.awt.windows.WToolkit

      file.encoding = Cp1252

      file.encoding.pkg = sun.io

      file.separator = \

      java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

      java.awt.printerjob = sun.awt.windows.WPrinterJob

      java.class.path = C:\jboss-eap-6.3.0\jboss-eap-6.3\jboss-modules.jar

      java.class.version = 51.0

      java.endorsed.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\endorsed

      java.ext.dirs = C:\Program Files\Java\jdk1.7.0\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

      java.home = C:\Program Files\Java\jdk1.7.0\jre

      java.io.tmpdir = C:\Users\******\AppData\Local\Temp\2\

      java.library.path = C:\Program Files\Java\jdk1.7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Java\jdk1.7.0;C:\Program Files\HP\NCU;C:\svn;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Windows Imaging\;D:\ESecurity_vss\svn\bin;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\PROGRA~1\CA\SHARED~1\CAM\bin;o;C:\Program Files\CA\Directory\dxserver\bin;.

      java.net.preferIPv4Stack = true

      java.runtime.name = Java(TM) SE Runtime Environment

      java.runtime.version = 1.7.0-b147

      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

      java.vm.info = mixed mode

      java.vm.name = Java HotSpot(TM) Client 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 = 21.0-b17

      javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

      javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

      javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

      javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

      javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

      javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

      javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

      javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

      javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

      javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

      jboss.bind.address = 0.0.0.0

      jboss.home.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3

      jboss.host.name = ctsinnvlsdsg

      jboss.modules.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\modules

      jboss.modules.policy-permissions = true

      jboss.modules.system.pkgs = org.jboss.byteman

      jboss.node.name = ctsinnvlsdsg

      jboss.qualified.host.name = ctsinnvlsdsg

      jboss.server.base.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone

      jboss.server.config.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\configuration

      jboss.server.data.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data

      jboss.server.deploy.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data\content

      jboss.server.log.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\log

      jboss.server.name = ctsinnvlsdsg

      jboss.server.persist.config = true

      jboss.server.temp.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\tmp

      line.separator =

     

     

      logging.configuration = file:C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone/configuration/logging.properties

      module.path = C:\jboss-eap-6.3.0\jboss-eap-6.3\modules

      nete.j2ee.vendor = jboss

      org.jboss.boot.log.file = C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\log\server.log

      org.jboss.resolver.warning = true

      org.xml.sax.driver = __redirected.__XMLReaderFactory

      os.arch = x86

      os.name = Windows Server 2008

      os.version = 6.0

      path.separator = ;

      program.name = standalone.bat

      sun.arch.data.model = 32

      sun.boot.class.path = C:\Program Files\Java\jdk1.7.0\jre\lib\resources.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\rt.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\jce.jar;C:\Program Files\Java\jdk1.7.0\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.7.0\jre\classes

      sun.boot.library.path = C:\Program Files\Java\jdk1.7.0\jre\bin

      sun.cpu.endian = little

      sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

      sun.desktop = windows

      sun.io.unicode.encoding = UnicodeLittle

      sun.java.command = C:\jboss-eap-6.3.0\jboss-eap-6.3\jboss-modules.jar -mp C:\jboss-eap-6.3.0\jboss-eap-6.3\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\jboss-eap-6.3.0\jboss-eap-6.3 -c standalone-full.xml -b 0.0.0.0 -Dnete.j2ee.vendor=jboss

      sun.java.launcher = SUN_STANDARD

      sun.jnu.encoding = Cp1252

      sun.management.compiler = HotSpot Client Compiler

      sun.os.patch.level = Service Pack 2

      user.country = US

      user.dir = C:\jboss-eap-6.3.0\jboss-eap-6.3\bin

      user.home = C:\Users\XXXXX

      user.language = en

      user.name = XXXXX

      user.script =

      user.timezone = Asia/Calcutta

      user.variant =

    14:37:46,265 DEBUG [org.jboss.as.config] (MSC service thread 1-6) VM Arguments: -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.policy-permissions=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dorg.jboss.boot.log.file=C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\log\server.log -Dlogging.configuration=file:C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone/configuration/logging.properties

    14:37:47,841 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_im.ear in deployment directory. To trigger deployment create a file called iam_im.ear.dodeploy

    14:37:47,872 INFO  [org.xnio] (MSC service thread 1-16) XNIO Version 3.0.10.GA-redhat-1

    14:37:47,888 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

    14:37:47,888 INFO  [org.xnio.nio] (MSC service thread 1-16) XNIO NIO Implementation Version 3.0.10.GA-redhat-1

    14:37:47,934 INFO  [org.jboss.remoting] (MSC service thread 1-16) JBoss Remoting version (unknown)

    14:37:47,950 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.

    14:37:47,966 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 34) JBAS010280: Activating Infinispan subsystem.

    14:37:47,966 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 35) JBAS016300: Activating JacORB Subsystem

    14:37:47,966 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 50) JBAS013171: Activating Security Subsystem

    14:37:47,966 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 45) JBAS011800: Activating Naming Subsystem

    14:37:47,966 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension

    14:37:47,966 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 41) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

    14:37:47,981 INFO  [org.jboss.as.security] (MSC service thread 1-24) JBAS013170: Current PicketBox version=4.0.19.SP8-redhat-1

    14:37:47,981 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-38) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)

    14:37:48,122 INFO  [org.jboss.as.naming] (MSC service thread 1-45) JBAS011802: Starting Naming Service

    14:37:48,122 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-26) JBAS015400: Bound mail session [java:jboss/mail/Default]

    14:37:48,122 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-9) JBAS015400: Bound mail session [java:/Mail]

    14:37:48,137 INFO  [org.jboss.jaxr] (MSC service thread 1-40) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory

    14:37:48,153 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

    14:37:48,356 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 11.1)

    14:37:48,371 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)

    14:37:48,371 INFO  [org.apache.coyote.ajp] (MSC service thread 1-19) JBWEB003046: Starting Coyote AJP/1.3 on ajp-/0.0.0.0:8009

    14:37:48,371 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-47) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/0.0.0.0:8080

    14:37:48,371 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-47) JBWEB003000: Coyote HTTP/1.1 starting on: http-/0.0.0.0:8080

    14:37:48,637 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=C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data\messagingjournal,bindingsDirectory=C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data\messagingbindings,largeMessagesDirectory=C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data\messaginglargemessages,pagingDirectory=C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\data\messagingpaging)

    14:37:48,652 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock

    14:37:48,668 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-27) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

    14:37:48,699 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal

    14:37:48,699 WARN  [jacorb.codeset] (MSC service thread 1-10) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

    14:37:48,730 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-31) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss-eap-6.3.0\jboss-eap-6.3\standalone\deployments

    14:37:48,730 INFO  [org.jboss.as.remoting] (MSC service thread 1-37) JBAS017100: Listening on 0.0.0.0:4447

    14:37:48,730 INFO  [org.jboss.as.remoting] (MSC service thread 1-38) JBAS017100: Listening on 127.0.0.1:9999

    14:37:48,746 INFO  [org.jboss.as.jacorb] (MSC service thread 1-10) JBAS016330: CORBA ORB Service started

    14:37:48,761 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3

    14:37:48,762 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock

    14:37:48,794 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock

    14:37:49,059 INFO  [org.jboss.as.jacorb] (MSC service thread 1-3) JBAS016328: CORBA Naming Service started

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-19) JBAS010400: Bound data source [java:/iam/im/jdbc/auditDbDataSource]

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-21) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/reportsnapshot]

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-32) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/WPDS]

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/archive]

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-36) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/idm]

    14:37:49,620 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-22) JBAS010400: Bound data source [java:/iam/im/jdbc/jdbc/objectstore]

    14:37:49,652 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 0.0.0.0:5445 for CORE protocol

    14:37:49,652 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 0.0.0.0:5455 for CORE protocol

    14:37:49,652 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live

    14:37:49,667 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.3.20.Final (2.3.20, 123) [21104413-2b9a-11e5-af09-353102e0998d]

    14:37:49,667 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpEventQueue

    14:37:49,808 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-31) JBAS010406: Registered connection factory java:/JmsXA

    14:37:49,823 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpEventQueue

    14:37:49,823 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpEventQueue

    14:37:49,823 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.topic.testTopic

    14:37:49,870 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:/topic/test

    14:37:49,870 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 65) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/topic/test

    14:37:49,870 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 68) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpServAutoActQueue

    14:37:49,870 INFO  [org.hornetq.ra] (MSC service thread 1-31) HornetQ resource adaptor started

    14:37:49,886 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-31) IJ020002: Deployed: file://RaActivatorhornetq-ra

    14:37:49,886 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-42) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

    14:37:49,886 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 68) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpServAutoActQueue

    14:37:49,886 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 68) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpServAutoActQueue

    14:37:49,886 INFO  [org.hornetq.jms.server] (ServerService Thread Pool -- 66) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "CTSINNVLSDSG". If this new address is incorrect please manually configure the connector to use the proper one.

    14:37:49,901 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:/wpConnectionFactory

    14:37:49,901 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory

    14:37:49,901 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name java:/jms/wpConnectionFactory

    14:37:49,901 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 67) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.com.netegrity.ims.msg.queue

    14:37:49,917 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/com.netegrity.ims.msg.queue

    14:37:49,917 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/com.netegrity.ims.msg.queue

    14:37:49,917 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.DLQ

    14:37:49,932 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 64) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ

    14:37:49,932 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 69) HQ221003: trying to deploy queue jms.queue.iam_imAnalyticsNotificationQueue

    14:37:49,948 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 69) JBAS011601: Bound messaging object to jndi name java:/iam/im/jms/queue/analytics/AnalyticsNotificationQueue

    14:37:49,948 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 63) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.wpUtilQueue

    14:37:49,979 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/wpUtilQueue

    14:37:49,979 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 63) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/wpUtilQueue

    14:37:49,979 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221003: trying to deploy queue jms.queue.testQueue

    14:37:49,995 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:/queue/test

    14:37:49,995 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 62) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/test

    14:37:49,995 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 60) HQ221003: trying to deploy queue jms.topic.iam.im.jms.topic.ServerCommandTopic

    14:37:50,010 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/topic/ServerCommandTopic

    14:37:50,010 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/topic/iam/im/jms/topic/ServerCommandTopic

    14:37:50,010 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

    14:37:50,026 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue

    14:37:50,026 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

    14:37:50,026 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory

    14:37:50,026 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.iam.im.jms.queue.RuntimeStatusDetailQueue

    14:37:50,057 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/queue/iam/im/jms/queue/RuntimeStatusDetailQueue

    14:37:50,073 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/im/jms/queue/RuntimeStatusDetailQueue

    14:37:50,213 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

    14:37:50,213 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

    14:37:50,213 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 4697ms - Started 247 of 284 services (78 services are lazy, passive or on-demand)

     

    Thanks,
    Murali



  • 6.  Re: Unable to launch IDM Management Console

    Broadcom Employee
    Posted Jul 16, 2015 05:37 AM

    Hi

    On my local IM 12.6 SP5 CR1 installation (using JBoss 6.3EAP) I get the same sort of

    "JBAS015960: Class Path entryxxx.jar in /E:/jboss-eap-6.3/standalone/deployments/iam_im.ear/library/***.jar  does not point to a valid jar for a Class-Path reference"

    would not worry about these as JBoss / IM starts just fine.

     

    I would start with updating your JDK. you are currently using

    java.version = 1.7.0

    According to the platform support matrix (SAP Portal Services) you should be using jdk1.7.0_71 as a minimum

     

    My advise would be to upgrade JDK, update JAVA_HOME in addition to Bill's advice re clearing the relevant folders.

     

    Regards

    Rinat



  • 7.  Re: Unable to launch IDM Management Console

    Posted Jul 16, 2015 06:36 AM

    Hi Rinat,

     

    Thank you.  Now am able to see the IM Page.

     

    Thanks,

    Murali



  • 8.  Re: Unable to launch IDM Management Console

    Broadcom Employee
    Posted Jul 16, 2015 06:39 AM

    Great news, can you share which step(s) fixed the problem?



  • 9.  Re: Unable to launch IDM Management Console

    Posted Jul 16, 2015 11:10 PM

    I have removed the temp directory and updated the java version to 1.7



  • 10.  Re: Unable to launch IDM Management Console

    Posted Jul 16, 2015 06:37 AM

    Hi Bill,

     

    Thank you for help.

     

    Now I am able to see the IM Page.

     

    Thanks,

    Murali