Startseite › Foren › Hilfe bei Problemen › WildFly Application Server hasn’t started within the timeout allowed
- Dieses Thema hat 1 Antwort sowie 2 Stimmen und wurde zuletzt vor vor 4 Monaten, 2 Wochen von
j-lawyer.org aktualisiert.
-
AutorBeiträge
-
20. April 2024 um 20:25 #6130
ras
TeilnehmerIch habe Probleme bei einer Neuinstallation von j-lawyer auf einem blanken Server. Ich habe es mehrfach versucht, ich habe den Ubuntu-Server komplett neu aufgesetzt, leider das gleiche Problem.
1. Neuinstallation des j-lawyer-servers auf einem frischen Ubuntu-Server.
2. Anleitung hier befolgt: https://www.j-lawyer.org/?page_id=93#install-server
3. root@ubuntu-4gb-nbg1-1:/usr/local/j-lawyer-server# sudo service j-lawyer-server status gibt folgendes aus:—
● j-lawyer-server.service – LSB: WildFly Application Server
Loaded: loaded (/etc/init.d/j-lawyer-server; generated)
Active: active (running) since Sat 2024-04-20 00:45:47 UTC; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 12935 ExecStart=/etc/init.d/j-lawyer-server start (code=exited, status=0/SUCCESS)
Tasks: 114 (limit: 18677)
Memory: 1.6G
CPU: 45.428s
CGroup: /system.slice/j-lawyer-server.service
├─12949 /bin/sh /usr/local/j-lawyer-server/wildfly/bin/standalone.sh -c standalone.xml -b 0.0.0.0
└─13071 java „-D[Standalone]“ -server -Xms256m -Xmx2048m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true –add-exports=java.desktop/sun.awt=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED –add-expor>Apr 20 00:45:16 ubuntu-4gb-nbg1-1 systemd[1]: Starting LSB: WildFly Application Server…
Apr 20 00:45:16 ubuntu-4gb-nbg1-1 j-lawyer-server[12935]: * Starting j-lawyer.org WildFly Application Server j-lawyer-server
Apr 20 00:45:47 ubuntu-4gb-nbg1-1 j-lawyer-server[12935]: …done.
Apr 20 00:45:47 ubuntu-4gb-nbg1-1 j-lawyer-server[12935]: * j-lawyer.org WildFly Application Server hasn’t started within the timeout allowed
Apr 20 00:45:47 ubuntu-4gb-nbg1-1 j-lawyer-server[12935]: * please review file „/var/log/j-lawyer-server/console.log“ to see the status of the service
Apr 20 00:45:47 ubuntu-4gb-nbg1-1 systemd[1]: Started LSB: WildFly Application Server.
—4. Logs unter /var/log/j-lawyer-server/console.log enthalten:
—root@ubuntu-4gb-nbg1-1:/usr/local/j-lawyer-server# cat /var/log/j-lawyer-server/console.log
=========================================================================JBoss Bootstrap Environment
JBOSS_HOME: /usr/local/j-lawyer-server/wildfly
JAVA: java
JAVA_OPTS: -server -Xms256m -Xmx2048m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true –add-exports=java.desktop/sun.awt=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.url.ldap=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.url.ldaps=ALL-UNNAMED –add-opens=java.base/java.lang=ALL-UNNAMED –add-opens=java.base/java.lang.invoke=ALL-UNNAMED –add-opens=java.base/java.lang.reflect=ALL-UNNAMED –add-opens=java.base/java.io=ALL-UNNAMED –add-opens=java.base/java.security=ALL-UNNAMED –add-opens=java.base/java.util=ALL-UNNAMED –add-opens=java.base/java.util.concurrent=ALL-UNNAMED –add-opens=java.management/javax.management=ALL-UNNAMED –add-opens=java.naming/javax.naming=ALL-UNNAMED -Djava.security.manager=allow
=========================================================================
00:45:16,953 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.2.Final
00:45:17,300 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.13.Final
00:45:17,305 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
00:45:17,371 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) starting
00:45:18,160 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads – 1) WFLYDS0015: Re-attempting failed deployment j-lawyer-server.ear
00:45:18,627 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
00:45:18,640 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.8.7.Final
00:45:18,646 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.8.7.Final
00:45:18,664 INFO [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool — 53) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
00:45:18,669 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 57) WFLYRS0016: RESTEasy version 4.7.7.Final
00:45:18,670 INFO [org.wildfly.extension.health] (ServerService Thread Pool — 54) WFLYHEALTH0001: Activating Base Health Subsystem
00:45:18,671 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 55) WFLYCLINF0001: Activating Infinispan subsystem.
00:45:18,674 INFO [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool — 66) WFLYCONF0001: Activating MicroProfile Config Subsystem
00:45:18,676 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 56) WFLYIO001: Worker ‚default‘ has auto-configured to 16 IO threads with 128 max task threads based on your 8 available processors
00:45:18,678 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 62) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
00:45:18,685 WARN [org.jboss.as.txn] (ServerService Thread Pool — 76) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
00:45:18,687 INFO [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool — 67) WFLYJWT0001: Activating MicroProfile JWT Subsystem
00:45:18,691 INFO [org.jboss.as.naming] (ServerService Thread Pool — 69) WFLYNAM0001: Activating Naming Subsystem
00:45:18,697 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 68) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
00:45:18,700 INFO [org.wildfly.extension.metrics] (ServerService Thread Pool — 65) WFLYMETRICS0001: Activating Base Metrics Subsystem
00:45:18,702 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.5.3.Final)
00:45:18,710 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 78) WFLYWS0002: Activating WebServices Extension
00:45:18,715 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
00:45:18,719 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
00:45:18,736 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
00:45:18,737 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
00:45:18,739 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
00:45:18,739 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = mysql
00:45:18,743 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.2.19.Final starting
00:45:18,748 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.25.Final
00:45:18,795 WARN [org.wildfly.extension.elytron] (MSC service thread 1-7) WFLYELY00023: KeyStore file ‚/usr/local/j-lawyer-server/wildfly/standalone/configuration/application.keystore‘ does not exist. Used blank.
00:45:18,818 WARN [org.wildfly.extension.elytron] (MSC service thread 1-7) WFLYELY01084: KeyStore /usr/local/j-lawyer-server/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
00:45:18,843 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 77) WFLYUT0014: Creating file handler for path ‚/usr/local/j-lawyer-server/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
00:45:18,845 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
00:45:18,845 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
00:45:18,846 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) Queuing requests.
00:45:18,847 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
00:45:18,847 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
00:45:18,910 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
00:45:18,972 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
00:45:18,984 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
00:45:19,004 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
00:45:19,004 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jlawyerdb]
00:45:19,132 INFO [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
00:45:19,136 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory /usr/local/j-lawyer-server/wildfly/standalone/deployments
00:45:19,140 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
00:45:19,168 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.5.0.Final (Apache CXF 3.4.10)
00:45:19,176 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/usr/local/j-lawyer-server/wildfly/standalone/data/activemq/journal,bindingsDirectory=/usr/local/j-lawyer-server/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/usr/local/j-lawyer-server/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/usr/local/j-lawyer-server/wildfly/standalone/data/activemq/paging)
00:45:19,197 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221012: Using AIO Journal
00:45:19,251 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
00:45:19,251 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
00:45:19,252 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
00:45:19,252 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
00:45:19,292 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221034: Waiting indefinitely to obtain live lock
00:45:19,292 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221035: Live Server Obtained live lock
00:45:19,556 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
00:45:19,562 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
00:45:19,562 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.searchIndexProcessorQueue on address jms.queue.searchIndexProcessorQueue
00:45:19,562 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.outgoingMailProcessorQueue on address jms.queue.outgoingMailProcessorQueue
00:45:19,579 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
00:45:19,579 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
00:45:19,579 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
00:45:19,579 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
00:45:19,662 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221007: Server is now live
00:45:19,662 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [default, nodeID=dab191e0-8e1d-11ee-8f82-b0a4607a48b5]
00:45:19,674 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
00:45:19,676 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 84) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „ubuntu-4gb-nbg1-1“. If this new address is incorrect please manually configure the connector to use the proper one.
00:45:19,676 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
00:45:19,716 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA
00:45:19,747 INFO [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-1) AMQ151007: Resource adaptor started
00:45:19,748 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra
00:45:19,748 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
00:45:19,748 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
00:45:25,987 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
00:45:25,987 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
00:45:25,987 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
00:45:25,987 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
00:45:25,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/json-simple-2.3.0.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/log4j-over-slf4j-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/slf4j-api-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/log4j-api-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jboss-jaxrs-api_2.1_spec-2.0.2.Final.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/log4j-core-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/log4j-slf4j-impl-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/asm-all-repackaged-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/cglib-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/guava-14.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/hk2-api-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/hk2-locator-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/hk2-utils-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,992 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/javax.annotation-api-1.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/javax.inject-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/javax.servlet-api-3.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jaxb-api-2.2.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-entity-filtering-2.5.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-media-moxy-2.5.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.osgi.core-4.2.0.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/osgi-resource-locator-1.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-client.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,993 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-common.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-container-servlet.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-container-servlet-core.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jersey-server.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.core-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.asm-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.antlr-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.jpa-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.jpa.jpql-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:25,994 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.moxy-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
00:45:26,008 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,008 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,008 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,008 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,008 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,009 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/j-lawyer-server.ear/lib/jaxb-core-2.3.0.1.jar does not point to a valid jar for a Class-Path reference.
00:45:26,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/FastInfoset.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/gmbal-api-only.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/ha-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/javax.mail_1.4.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,010 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jaxws-rt.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,011 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jaxws-tools.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,011 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/management-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/mimepull.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/policy.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/saaj-impl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/stax-ex.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,013 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/stax2-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/streambuffer.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/woodstox-core-asl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jaxws-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jsr181-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/javax.annotation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/saaj-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/activation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/jaxb-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/hamcrest-core-1.3.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,014 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry lib/org-netbeans-modules-java-j2seproject-copylibstask.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,020 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
00:45:26,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
00:45:26,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
00:45:26,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
00:45:26,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
00:45:26,032 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
00:45:26,034 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jollyday-0.4.7.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
00:45:26,034 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/tika-app-1.5.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
00:45:26,170 WARN [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/searchIndexProcessorQueue‘ for Jakarta Enterprise Beans ‚SearchIndexProcessor‘ will be ignored.
00:45:26,171 WARN [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/outgoingMailProcessorQueue‘ for Jakarta Enterprise Beans ‚OutgoingMailProcessor‘ will be ignored.
00:45:26,202 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
00:45:26,217 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
00:45:26,615 INFO [org.jipijapa] (MSC service thread 1-6) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
00:45:26,681 INFO [org.jipijapa] (MSC service thread 1-6) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
00:45:26,700 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
00:45:26,840 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 6.0.23.Final
00:45:26,865 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 81) ISPN000128: Infinispan version: Infinispan ‚Triskaidekaphobia‘ 13.0.10.Final
00:45:26,948 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 81) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller‘
00:45:26,986 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
00:45:26,992 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
00:45:27,017 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
00:45:27,020 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚PersistenceLifecycleBean‘ in deployment unit ’subdeployment „j-lawyer-server-entities.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:app/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:module/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean
java:app/j-lawyer-server-entities/PersistenceLifecycleBean
java:module/PersistenceLifecycleBean00:45:27,047 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-3) WFLYTRAC0001: Tracer initialized: NoopTracer
00:45:27,056 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
00:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:app/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:module/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5
java:app/j-lawyer-io/ContactsEndpointV5
java:module/ContactsEndpointV500:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚TemplatesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:app/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:module/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6
java:app/j-lawyer-io/TemplatesEndpointV6
java:module/TemplatesEndpointV600:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:app/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:module/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4
java:app/j-lawyer-io/CalendarEndpointV4
java:module/CalendarEndpointV400:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:app/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:module/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2
java:app/j-lawyer-io/ContactsEndpointV2
java:module/ContactsEndpointV200:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:app/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:module/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1
java:app/j-lawyer-io/ContactsEndpointV1
java:module/ContactsEndpointV100:45:27,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚ConfigurationEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:app/j-lawyer-io/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:module/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7
java:app/j-lawyer-io/ConfigurationEndpointV7
java:module/ConfigurationEndpointV700:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚DataBucketEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:app/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:module/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6
java:app/j-lawyer-io/DataBucketEndpointV6
java:module/DataBucketEndpointV600:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:app/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:module/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1
java:app/j-lawyer-io/SecurityEndpointV1
java:module/SecurityEndpointV100:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:app/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:module/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6
java:app/j-lawyer-io/CasesEndpointV6
java:module/CasesEndpointV600:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:app/j-lawyer-io/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:module/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV7
java:app/j-lawyer-io/CasesEndpointV7
java:module/CasesEndpointV700:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚FormsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:app/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:module/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1
java:app/j-lawyer-io/FormsEndpointV1
java:module/FormsEndpointV100:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:app/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:module/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6
java:app/j-lawyer-io/SecurityEndpointV6
java:module/SecurityEndpointV600:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:app/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:module/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2
java:app/j-lawyer-io/CasesEndpointV2
java:module/CasesEndpointV200:45:27,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV3‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:app/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:module/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3
java:app/j-lawyer-io/CasesEndpointV3
java:module/CasesEndpointV300:45:27,061 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:app/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:module/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4
java:app/j-lawyer-io/CasesEndpointV4
java:module/CasesEndpointV400:45:27,061 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚MessagingEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:app/j-lawyer-io/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:module/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/MessagingEndpointV7
java:app/j-lawyer-io/MessagingEndpointV7
java:module/MessagingEndpointV700:45:27,061 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:app/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:module/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5
java:app/j-lawyer-io/CasesEndpointV5
java:module/CasesEndpointV500:45:27,061 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚AdministrationEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:app/j-lawyer-io/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:module/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/AdministrationEndpointV7
java:app/j-lawyer-io/AdministrationEndpointV7
java:module/AdministrationEndpointV700:45:27,061 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:app/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:module/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1
java:app/j-lawyer-io/CasesEndpointV1
java:module/CasesEndpointV100:45:27,088 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller‘
00:45:27,215 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
00:45:27,220 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:module/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade
java:app/j-lawyer-server-ejb/DocumentFolderFacade
java:module/DocumentFolderFacade00:45:27,221 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚BankDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:module/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade
java:app/j-lawyer-server-ejb/BankDataBeanFacade
java:module/BankDataBeanFacade00:45:27,223 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:module/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:module/ArchiveFileFormsBeanFacade00:45:27,226 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚SystemManagement‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:app/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:module/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal
java:app/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal
java:module/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal00:45:27,227 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ContactSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:app/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:module/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService
java:app/j-lawyer-server-ejb/ContactSyncService
java:module/ContactSyncService00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚MappingEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:app/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:module/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade
java:app/j-lawyer-server-ejb/MappingEntryFacade
java:module/MappingEntryFacade00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeArtefactBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:module/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:module/FormTypeArtefactBeanFacade00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ContainerLifecycleBean‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:app/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:module/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:app/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:module/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ContainerLifecycleBean!com.jdimension.jlawyer.services.ContainerLifecycleBeanRemote00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚FormsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceRemote00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileHistoryBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:module/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:module/ArchiveFileHistoryBeanFacade00:45:27,228 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ScheduledTasksService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:app/j-lawyer-server-ejb/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:module/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ScheduledTasksService
java:app/j-lawyer-server-ejb/ScheduledTasksService
java:module/ScheduledTasksService00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚SearchService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CityDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:module/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade
java:app/j-lawyer-server-ejb/CityDataBeanFacade
java:module/CityDataBeanFacade00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileAddressesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:module/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:module/ArchiveFileAddressesBeanFacade00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:app/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:module/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade
java:app/j-lawyer-server-ejb/MailboxAccessFacade
java:module/MailboxAccessFacade00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetPositionTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:module/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionTemplateFacade
java:app/j-lawyer-server-ejb/TimesheetPositionTemplateFacade
java:module/TimesheetPositionTemplateFacade00:45:27,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:app/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:module/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade
java:app/j-lawyer-server-ejb/MailboxSetupFacade
java:module/MailboxSetupFacade00:45:27,230 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal00:45:27,231 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AddressTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:module/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade
java:module/AddressTagsBeanFacade00:45:27,231 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePositionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:module/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade
java:app/j-lawyer-server-ejb/InvoicePositionFacade
java:module/InvoicePositionFacade00:45:27,231 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:app/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:module/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade
java:app/j-lawyer-server-ejb/CalendarAccessFacade
java:module/CalendarAccessFacade00:45:27,231 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚GroupMembershipFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:app/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:module/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade
java:app/j-lawyer-server-ejb/GroupMembershipFacade
java:module/GroupMembershipFacade00:45:27,231 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AddressBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:module/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade
java:app/j-lawyer-server-ejb/AddressBeanFacade
java:module/AddressBeanFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetPositionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:module/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionFacade
java:app/j-lawyer-server-ejb/TimesheetPositionFacade
java:module/TimesheetPositionFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:app/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:module/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade
java:app/j-lawyer-server-ejb/CampaignFacade
java:module/CampaignFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:module/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:module/DocumentTagsBeanFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚FaxQueueBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:module/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade
java:module/FaxQueueBeanFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileReviewsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:module/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:module/ArchiveFileReviewsBeanFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:module/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade
java:app/j-lawyer-server-ejb/InvoicePoolFacade
java:module/InvoicePoolFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚GroupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:app/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:module/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade
java:app/j-lawyer-server-ejb/GroupFacade
java:module/GroupFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ReportService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:app/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:module/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService
java:app/j-lawyer-server-ejb/ReportService
java:module/ReportService00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CaseSyncSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:module/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:module/CaseSyncSettingsFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚DrebisService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InstantMessageFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:app/j-lawyer-server-ejb/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:module/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageFacade
java:app/j-lawyer-server-ejb/InstantMessageFacade
java:module/InstantMessageFacade00:45:27,232 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceTypeFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:module/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade
java:app/j-lawyer-server-ejb/InvoiceTypeFacade
java:module/InvoiceTypeFacade00:45:27,233 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CaseAccountEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:app/j-lawyer-server-ejb/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:module/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseAccountEntryFacade
java:app/j-lawyer-server-ejb/CaseAccountEntryFacade
java:module/CaseAccountEntryFacade00:45:27,235 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileGroupsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:module/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:module/ArchiveFileGroupsBeanFacade00:45:27,235 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:module/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:module/ArchiveFileTagsBeanFacade00:45:27,236 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePositionTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:module/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionTemplateFacade
java:app/j-lawyer-server-ejb/InvoicePositionTemplateFacade
java:module/InvoicePositionTemplateFacade00:45:27,236 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:module/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:module/CaseFolderSettingsFacade00:45:27,236 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:app/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:module/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade
java:app/j-lawyer-server-ejb/CalendarSetupFacade
java:module/CalendarSetupFacade00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormEntriesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:module/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:module/ArchiveFileFormEntriesBeanFacade00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:module/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:module/InvoicePoolAccessFacade00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:module/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetFacade
java:app/j-lawyer-server-ejb/TimesheetFacade
java:module/TimesheetFacade00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:app/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:module/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService
java:app/j-lawyer-server-ejb/CalendarSyncService
java:module/CalendarSyncService00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CustomerRelationsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚MappingTableFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:app/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:module/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade
java:app/j-lawyer-server-ejb/MappingTableFacade
java:module/MappingTableFacade00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AddressService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:app/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:module/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal
java:app/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal
java:module/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal00:45:27,238 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignAddressesFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:app/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:module/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade
java:app/j-lawyer-server-ejb/CampaignAddressesFacade
java:module/CampaignAddressesFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InstantMessageMentionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:app/j-lawyer-server-ejb/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:module/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageMentionFacade
java:app/j-lawyer-server-ejb/InstantMessageMentionFacade
java:module/InstantMessageMentionFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileDocumentsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:module/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:module/ArchiveFileDocumentsBeanFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AppOptionGroupBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:module/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:module/AppOptionGroupBeanFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:module/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:module/DocumentFolderTemplateFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ServerSettingsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:module/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:module/ServerSettingsBeanFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚SingletonService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:app/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:module/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal
java:app/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal
java:module/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚VoipService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚EpostQueueBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:app/j-lawyer-server-ejb/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:module/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/EpostQueueBeanFacade
java:app/j-lawyer-server-ejb/EpostQueueBeanFacade
java:module/EpostQueueBeanFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:app/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:module/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetService
java:app/j-lawyer-server-ejb/TimesheetService
java:module/TimesheetService00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚PartyTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:module/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade
java:module/PartyTypeBeanFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:module/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade
java:app/j-lawyer-server-ejb/InvoiceFacade
java:module/InvoiceFacade00:45:27,239 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚MessagingService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:module/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade
java:app/j-lawyer-server-ejb/FormTypeBeanFacade
java:module/FormTypeBeanFacade00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AppUserBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:module/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade
java:app/j-lawyer-server-ejb/AppUserBeanFacade
java:module/AppUserBeanFacade00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:module/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade
java:app/j-lawyer-server-ejb/CaseFolderFacade
java:module/CaseFolderFacade00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:module/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:module/ArchiveFileBeanFacade00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚DataBucketLoader‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:app/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:module/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:app/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:module/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/DataBucketLoader!com.jdimension.jlawyer.services.DataBucketLoaderRemote00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚CustomHooksService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:app/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:module/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService
java:app/j-lawyer-server-ejb/CustomHooksService
java:module/CustomHooksService00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationHookFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:app/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:module/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade
java:app/j-lawyer-server-ejb/IntegrationHookFacade
java:module/IntegrationHookFacade00:45:27,240 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) WFLYEJB0473: JNDI bindings for session bean named ‚AppRoleBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:
java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:module/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade
java:app/j-lawyer-server-ejb/AppRoleBeanFacade
java:module/AppRoleBeanFacade00:45:27,251 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
00:45:27,253 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 81) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
00:45:27,256 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:45:27,257 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
00:45:27,265 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 83) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
00:45:27,265 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 81) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
00:45:27,266 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 82) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
00:45:27,268 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 83) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
00:45:27,280 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-4) WFLYTRAC0001: Tracer initialized: NoopTracer
00:45:27,318 INFO [org.hibernate.Version] (ServerService Thread Pool — 82) HHH000412: Hibernate Core {5.3.28.Final}
00:45:27,318 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 82) HHH000206: hibernate.properties not found
00:45:27,356 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-1) No shutdown hook registered: Please call close() manually on application shutdown.
00:45:27,356 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-1) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@4df28385, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=ubuntu-4gb-nbg1-1, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
00:45:27,372 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-8) No shutdown hook registered: Please call close() manually on application shutdown.
00:45:27,373 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-7) No shutdown hook registered: Please call close() manually on application shutdown.
00:45:27,373 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-server-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@33980dbe, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=ubuntu-4gb-nbg1-1, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
00:45:27,373 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-7) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-server-war.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@661970b0, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=ubuntu-4gb-nbg1-1, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
00:45:27,398 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 3.1.9 (Final)
00:45:27,449 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 82) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
00:45:27,483 INFO [org.jipijapa] (MSC service thread 1-4) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
00:45:27,643 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
00:45:27,784 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool — 82) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:364)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:371)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1328)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:505)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:640)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:605)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151)
at org.jboss.as.connector@26.1.3.Final//org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:68)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.sql.SQLException: Access denied for user ‚root’@’localhost‘
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:446)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:239)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:188)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:335)
… 39 more00:45:27,785 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 82) HHH000342: Could not obtain connection to query metadata : javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jlawyerdb
00:45:27,786 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
… 10 more
Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
… 22 more00:45:27,898 INFO [org.jipijapa] (MSC service thread 1-6) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
00:45:28,031 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
00:45:28,033 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool — 82) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:364)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:371)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1328)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:505)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:640)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:605)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
at org.jboss.ironjacamar.impl@1.5.3.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151)
at org.jboss.as.connector@26.1.3.Final//org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:68)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: java.sql.SQLException: Access denied for user ‚root’@’localhost‘
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:446)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:239)
at com.mysql.driver8@8.0.33//com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:188)
at org.jboss.ironjacamar.jdbcadapters@1.5.3.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:335)
… 39 more00:45:28,034 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 82) HHH000342: Could not obtain connection to query metadata : javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jlawyerdb
00:45:28,034 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
… 10 more
Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
… 22 more00:45:28,043 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
00:45:28,049 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean ‚OutgoingMailProcessor‘ with ‚activemq-ra.rar‘ resource adapter
00:45:28,063 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {„WFLYCTL0080: Failed services“ => {
„jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“,
„jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“
}}
00:45:28,157 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
00:45:28,161 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
WFLYCTL0448: 419 additional services are down due to their dependencies being missing or failed
00:45:28,191 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
00:45:28,194 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 11498ms – Started 3258 of 3885 services (440 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
00:45:28,196 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
00:45:28,196 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
—5. Der j-lawyer-server ist nicht erreichbar, insb auch nicht j-lawyer-io/swagger (weswegen ich ein neues System aufgesetzt habe)
6. Gleiches Problem beim Starten via Docker (Schritte hier: https://www.j-lawyer.org/?p=3581)
Hat es etwas damit zu tun, dass bei 2.5->2.6 sehr viele DB-Änderungen stattgefunden haben? Hat das ggfs. Auswirkungen auf Neuinstallationen? Es kommt ja der Fehler „00:59:45,712 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 83) exception caught: org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 1.13.0.17 (AddRootFolders)“
20. April 2024 um 20:26 #6132j-lawyer.org
Administrator> Access denied for user ‚root’@’localhost‘
Aktuell hat entweder der Server kein korrektes Datenbankpasswort, oder die Datenbank ist nicht korrekt konfiguriert um TCP-Verbindungen zu erlauben.
-
AutorBeiträge
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.