Fehler bei Neuinstallation 2.5

Startseite › Foren › Hilfe bei Problemen › Fehler bei Neuinstallation 2.5

Verschlagwortet: ,

3 Beiträge anzeigen - 1 bis 3 (von insgesamt 3)
  • Autor
    Beiträge
  • 9. März 2024 um 20:34 #5986
    Veraendert
    Participant

    Ich habe jetzt schon komplett neu installiert (und sogar von Debian auf Ubuntu gewechselt) und komme trotzdem nicht weiter, weil es sql-Fehler gibt. Was, bitte, übersehe ich?

    Datenbank ist vorhanden:
    MariaDB [(none)]> SHOW DATABASES;
    +——————–+
    | Database |
    +——————–+
    | information_schema |
    | jlawyerdb |
    | mysql |
    | performance_schema |
    | sys |
    +——————–+
    5 rows in set (0,003 sec)

    MariaDB müsste die richtige Version sein:
    Server version: 10.6.16-MariaDB-0ubuntu0.22.04.1 Ubuntu 22.04

    Java auch:
    georg@jlawyer:~$ java –version
    openjdk 11.0.22 2024-01-16
    OpenJDK Runtime Environment (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1)
    OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1, mixed mode, sharing)

    Und trotzdem gibt es Fehler:

    =========================================================================

    JBoss Bootstrap Environment

    JBOSS_HOME: /usr/local/j-lawyer-server/wildfly

    JAVA: java

    JAVA_OPTS: -server -Xms256m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dlog4j2.formatMsgNoLookups=true –add-exports=java.base/sun.nio.ch=ALL-UNNAMED –add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED –add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED –add-modules=java.se

    =========================================================================

    [0m09:49:06,330 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
    [0m[0m09:49:06,728 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
    [0m[0m09:49:06,734 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
    [0m[0m09:49:06,858 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
    [0m[0m09:49:07,598 INFO [org.wildfly.security] (ServerService Thread Pool — 26) ELY00001: WildFly Elytron version 1.8.0.Final
    [0m[0m09:49:08,021 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/core-service=management/management-interface=http-interface‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
    [0m[33m09:49:08,066 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 22) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
    [0m[0m09:49:08,077 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool — 11) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/subsystem=undertow/server=default-server/https-listener=https‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
    [0m[0m09:49:09,854 INFO [org.jboss.as.repository] (ServerService Thread Pool — 10) WFLYDR0001: Content added at location /usr/local/j-lawyer-server/wildfly/standalone/data/content/8d/e6f73a8502b87aea13e9afdece30e33cf3d4db/content
    [0m[0m09:49:09,892 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
    [0m[0m09:49:09,904 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.6.5.Final
    [0m[0m09:49:09,909 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.6.5.Final
    [0m[33m09:49:09,918 WARN [org.jboss.as.logging] (Controller Boot Thread) WFLYLOG0012: Replacing handler ‚FILE‘ during add operation. Either the handler type or the module name differs from the initial configuration.
    [0m[0m09:49:09,960 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool — 60) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
    [0m[0m09:49:09,967 INFO [org.jboss.as.security] (ServerService Thread Pool — 68) WFLYSEC0002: Activating Security Subsystem
    [0m[0m09:49:09,971 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
    [0m[0m09:49:09,974 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 2.0.19.Final starting
    [0m[0m09:49:09,976 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool — 59) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
    [0m[0m09:49:09,986 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 51) WFLYRS0016: RESTEasy version 3.6.3.Final
    [0m[0m09:49:09,993 INFO [org.jboss.as.naming] (ServerService Thread Pool — 62) WFLYNAM0001: Activating Naming Subsystem
    [0m[0m09:49:09,993 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
    [0m[0m09:49:09,996 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
    [0m[33m09:49:09,998 WARN [org.jboss.as.txn] (ServerService Thread Pool — 70) 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.
    [0m[0m09:49:10,027 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 49) WFLYCLINF0001: Activating Infinispan subsystem.
    [0m[0m09:49:10,006 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
    [0m[0m09:49:10,039 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.12.Final)
    [0m[0m09:49:10,058 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 50) WFLYIO001: Worker ‚default‘ has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
    [0m[0m09:49:10,061 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 72) WFLYWS0002: Activating WebServices Extension
    [0m[0m09:49:10,079 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
    [0m[0m09:49:10,118 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.8.Final
    [0m[0m09:49:10,127 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
    [0m[0m09:49:10,130 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
    [0m[0m09:49:10,166 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
    [0m[0m09:49:10,166 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
    [0m[0m09:49:10,184 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
    [0m[0m09:49:10,185 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
    [0m[0m09:49:10,185 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = mysql
    [0m[0m09:49:10,191 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
    [0m[0m09:49:10,187 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
    [0m[0m09:49:10,299 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 71) 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: ‚[]‘]
    [0m[0m09:49:10,328 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
    [0m[0m09:49:10,329 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
    [0m[0m09:49:10,436 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
    [0m[0m09:49:10,511 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete
    [0m[0m09:49:10,565 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    [0m[0m09:49:10,566 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/jlawyerdb]
    [0m[0m09:49:10,666 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
    [0m[33m09:49:10,727 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: 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
    [0m[0m09:49:10,741 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /usr/local/j-lawyer-server/wildfly/standalone/deployments
    [0m[0m09:49:10,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
    [0m[0m09:49:10,758 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) 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)
    [0m[0m09:49:10,815 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221012: Using AIO Journal
    [0m[0m09:49:10,848 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
    [0m[0m09:49:10,908 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
    [0m[0m09:49:10,912 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
    [0m[0m09:49:10,913 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
    [0m[0m09:49:10,914 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
    [0m[0m09:49:10,943 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.7)
    [0m[0m09:49:10,975 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221034: Waiting indefinitely to obtain live lock
    [0m[0m09:49:10,976 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221035: Live Server Obtained live lock
    [0m[0m09:49:11,261 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    [0m[0m09:49:11,262 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    [0m[0m09:49:11,262 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    [0m[0m09:49:11,262 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
    [0m[0m09:49:11,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221007: Server is now live
    [0m[0m09:49:11,338 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.6.3.jbossorg-00014 [default, nodeID=47914851-ddfa-11ee-8cf3-64006a2b30db]
    [0m[33m09:49:11,344 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 74) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „jlawyer“. If this new address is incorrect please manually configure the connector to use the proper one.
    [0m[0m09:49:11,364 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 74) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    [0m[0m09:49:11,399 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0007: Registered connection factory java:/JmsXA
    [0m[0m09:49:11,401 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
    [0m[0m09:49:11,402 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    [0m[0m09:49:11,524 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 78) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
    [0m[0m09:49:11,570 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-6) AMQ151007: Resource adaptor started
    [0m[0m09:49:11,570 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatoractivemq-ra
    [0m[0m09:49:11,572 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
    [0m[0m09:49:11,572 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    [0m[33m09:49:16,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jboss-jaxrs-api_2.1_spec-1.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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,923 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,923 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,925 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[33m09:49:16,935 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
    [0m[0m09:49:16,947 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
    [0m[0m09:49:16,947 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
    [0m[0m09:49:16,947 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
    [0m[0m09:49:16,947 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
    [0m[0m09:49:16,947 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
    [0m[33m09:49:16,964 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    [0m[33m09:49:16,965 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    [0m[0m09:49:17,174 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    [0m[0m09:49:17,189 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    [0m[0m09:49:17,513 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 75) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    [0m[0m09:49:17,524 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
    [0m[0m09:49:17,526 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 77) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    [0m[0m09:49:17,533 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 77) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    [0m[0m09:49:17,534 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 75) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    [0m[0m09:49:17,637 INFO [org.hibernate.Version] (ServerService Thread Pool — 75) HHH000412: Hibernate Core {5.3.9.Final}
    [0m[0m09:49:17,638 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 75) HHH000206: hibernate.properties not found
    [0m[0m09:49:17,727 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-7) HV000001: Hibernate Validator 6.0.15.Final
    [0m[0m09:49:17,791 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 75) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    [0m[0m09:49:17,908 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
    [0m[0m09:49:17,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
    [0m[0m09:49:17,958 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
    [0m[0m09:49:17,961 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-7) 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
    ejb:j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
    java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean
    java:app/j-lawyer-server-entities/PersistenceLifecycleBean
    java:module/PersistenceLifecycleBean

    [0m[0m09:49:18,127 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
    [0m[0m09:49:18,129 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
    java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6
    java:app/j-lawyer-io/TemplatesEndpointV6
    java:module/TemplatesEndpointV6

    [0m[0m09:49:18,129 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
    java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5
    java:app/j-lawyer-io/ContactsEndpointV5
    java:module/ContactsEndpointV5

    [0m[0m09:49:18,129 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
    java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4
    java:app/j-lawyer-io/CalendarEndpointV4
    java:module/CalendarEndpointV4

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
    java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2
    java:app/j-lawyer-io/ContactsEndpointV2
    java:module/ContactsEndpointV2

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
    java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1
    java:app/j-lawyer-io/ContactsEndpointV1
    java:module/ContactsEndpointV1

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
    java:global/j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7
    java:app/j-lawyer-io/ConfigurationEndpointV7
    java:module/ConfigurationEndpointV7

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
    java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6
    java:app/j-lawyer-io/DataBucketEndpointV6
    java:module/DataBucketEndpointV6

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
    java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1
    java:app/j-lawyer-io/SecurityEndpointV1
    java:module/SecurityEndpointV1

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6
    java:app/j-lawyer-io/CasesEndpointV6
    java:module/CasesEndpointV6

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV7
    java:app/j-lawyer-io/CasesEndpointV7
    java:module/CasesEndpointV7

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
    java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1
    java:app/j-lawyer-io/FormsEndpointV1
    java:module/FormsEndpointV1

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
    java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6
    java:app/j-lawyer-io/SecurityEndpointV6
    java:module/SecurityEndpointV6

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2
    java:app/j-lawyer-io/CasesEndpointV2
    java:module/CasesEndpointV2

    [0m[0m09:49:18,130 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3
    java:app/j-lawyer-io/CasesEndpointV3
    java:module/CasesEndpointV3

    [0m[0m09:49:18,131 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
    java:global/j-lawyer-server/j-lawyer-io/MessagingEndpointV7
    java:app/j-lawyer-io/MessagingEndpointV7
    java:module/MessagingEndpointV7

    [0m[0m09:49:18,131 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4
    java:app/j-lawyer-io/CasesEndpointV4
    java:module/CasesEndpointV4

    [0m[0m09:49:18,131 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5
    java:app/j-lawyer-io/CasesEndpointV5
    java:module/CasesEndpointV5

    [0m[0m09:49:18,131 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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
    ejb:j-lawyer-server/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
    java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1
    java:app/j-lawyer-io/CasesEndpointV1
    java:module/CasesEndpointV1

    [0m[0m09:49:18,264 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan ‚Infinity Minus ONE +2‘ 9.4.8.Final
    [0m[0m09:49:18,369 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
    [0m[0m09:49:18,372 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/DocumentFolderFacade

    [0m[0m09:49:18,372 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/BankDataBeanFacade

    [0m[0m09:49:18,372 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileFormsBeanFacade

    [0m[0m09:49:18,373 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.SystemManagementLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/SystemManagement!com.jdimension.jlawyer.services.SystemManagementLocal

    [0m[0m09:49:18,373 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ContactSyncService

    [0m[0m09:49:18,373 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/MappingEntryFacade

    [0m[0m09:49:18,373 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/FormTypeArtefactBeanFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.CalendarServiceLocal
    java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
    java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceLocal
    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

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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.ContainerLifecycleBeanRemote

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.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.FormsServiceRemote
    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
    ejb:j-lawyer-server/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileHistoryBeanFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.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.SearchServiceRemote
    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
    ejb:j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CityDataBeanFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileAddressesBeanFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/MailboxAccessFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/TimesheetPositionTemplateFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/MailboxSetupFacade

    [0m[0m09:49:18,374 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.ArchiveFileServiceLocal
    java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    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

    [0m[0m09:49:18,375 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/AddressTagsBeanFacade

    [0m[0m09:49:18,375 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoicePositionFacade

    [0m[0m09:49:18,375 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CalendarAccessFacade

    [0m[0m09:49:18,375 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/GroupMembershipFacade

    [0m[0m09:49:18,382 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/AddressBeanFacade

    [0m[0m09:49:18,383 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/TimesheetPositionFacade

    [0m[0m09:49:18,384 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CampaignFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/DocumentTagsBeanFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.IntegrationServiceLocal
    java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
    java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceLocal
    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

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/FaxQueueBeanFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileReviewsBeanFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoicePoolFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/GroupFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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/ReportService

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CaseSyncSettingsFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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.DrebisServiceRemote

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InstantMessageFacade

    [0m[0m09:49:18,385 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoiceTypeFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileGroupsBeanFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileTagsBeanFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoicePositionTemplateFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CaseFolderSettingsFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CalendarSetupFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileFormEntriesBeanFacade

    [0m[0m09:49:18,386 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoicePoolAccessFacade

    [0m[0m09:49:18,390 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/TimesheetFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CalendarSyncService

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.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.CustomerRelationsServiceRemote
    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
    ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/MappingTableFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.AddressServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/AddressService!com.jdimension.jlawyer.services.AddressServiceLocal

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.SecurityServiceLocal
    java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    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

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CampaignAddressesFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InstantMessageMentionFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileDocumentsBeanFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/AppOptionGroupBeanFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/DocumentFolderTemplateFacade

    [0m[0m09:49:18,391 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ServerSettingsBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.SingletonServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/SingletonService!com.jdimension.jlawyer.services.SingletonServiceLocal

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.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.InvoiceServiceRemote
    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
    ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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.VoipServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/EpostQueueBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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/TimesheetService

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/PartyTypeBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/InvoiceFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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.MessagingServiceRemote

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/FormTypeBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/AppUserBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CaseFolderFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/ArchiveFileBeanFacade

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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.DataBucketLoaderRemote

    [0m[0m09:49:18,392 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/CustomHooksService

    [0m[0m09:49:18,393 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/IntegrationHookFacade

    [0m[0m09:49:18,393 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) 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
    ejb:j-lawyer-server/j-lawyer-server-ejb/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/AppRoleBeanFacade

    [0m[0m09:49:18,505 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.1.0 (Final)
    [0m[33m09:49:18,660 WARN [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (createFile)
    [0m[33m09:49:18,660 WARN [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readFile)
    [0m[33m09:49:18,660 WARN [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (copyFile)
    [0m[33m09:49:18,660 WARN [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readTextFile)
    [0m[33m09:49:18,660 WARN [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (writeFile)
    [0m[0m09:49:18,840 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 75) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    [0m[0m09:49:18,870 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 78) WFLYCLINF0002: Started client-mappings cache from ejb container
    [0mWARNING: An illegal reflective access operation has occurred
    WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/usr/local/j-lawyer-server/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
    WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
    WARNING: Use –illegal-access=warn to enable warnings of further illegal reflective access operations
    WARNING: All illegal access operations will be denied in a future release
    [0m09:49:19,128 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 75) HHH000400: Using dialect: org.hibernate.dialect.MySQL55Dialect
    [0m[0m09:49:19,174 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 75) Envers integration enabled? : true
    [0m[0m09:49:19,309 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 77) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    [0m[0m09:49:19,326 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 77) HHH000400: Using dialect: org.hibernate.dialect.MySQL55Dialect
    [0m[0m09:49:19,336 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 77) Envers integration enabled? : true
    [0m[0m09:49:19,345 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    [0m[0m09:49:19,774 INFO [stdout] (ServerService Thread Pool — 75) Starting j-lawyer.org database migrations…
    [0m[0m09:49:19,795 INFO [org.flywaydb.core.internal.license.VersionPrinter] (ServerService Thread Pool — 75) Flyway Community Edition 5.2.1 by Boxfuse
    [0m[0m09:49:19,802 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 75) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.5)
    [0m[0m09:49:20,084 INFO [org.flywaydb.core.internal.command.DbValidate] (ServerService Thread Pool — 75) Successfully validated 152 migrations (execution time 00:00.186s)
    [0m[0m09:49:20,097 INFO [org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory] (ServerService Thread Pool — 75) Creating Schema History table: jlawyerdb.flyway_schema_history
    [0m[33m09:49:20,141 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚flyway_schema_history_pk‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:20,221 INFO [org.flywaydb.core.internal.command.DbBaseline] (ServerService Thread Pool — 75) Successfully baselined schema with version: 1.9.1.0
    [0m[0m09:49:20,231 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Current version of schema jlawyerdb: 1.9.1.0
    [0m[0m09:49:20,233 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.0 – UpdateDbVersion
    [0m[0m09:49:20,266 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.1 – SampleMigration
    [0m[0m09:49:20,270 INFO [db.migration.V1_10_0_1__SampleMigration] (ServerService Thread Pool — 75) Running migration db.migration.V1_10_0_1__SampleMigration
    [0m[0m09:49:20,288 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.2 – AddIndex
    [0m[0m09:49:20,369 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.3 – RenameTables
    [0m[0m09:49:20,934 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.4 – RemoveOptionGroupRole
    [0m[0m09:49:20,967 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.5 – AddIndex
    [0m[0m09:49:21,045 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.6 – AddTableDocumentTags
    [0m[33m09:49:21,093 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_document_tags‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:21,341 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.7 – BeaProductionEndpoint
    [0m[0m09:49:21,354 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.8 – InitialDocmentTags
    [0m[0m09:49:21,377 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.9 – VersionUpdate
    [0m[0m09:49:21,391 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.10.0.10 – MacOsForeignKeyFix
    [0m[0m09:49:22,658 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.11.0.0 – AddDepartment
    [0m[0m09:49:22,721 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.11.0.1 – AddSmtpPort
    [0m[0m09:49:22,787 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.11.0.2 – SyncFix
    [0m[0m09:49:22,808 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.0 – AddTablePartyTypes
    [0m[33m09:49:22,844 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_party_types‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:23,184 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.1 – AddIndexDepartment
    [0m[0m09:49:23,266 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.2 – AddTableFormTypes
    [0m[33m09:49:23,311 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_form_types‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[33m09:49:23,346 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_form_types_artefacts‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[33m09:49:23,396 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_forms‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[33m09:49:23,442 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_forms_entries‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:23,461 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.3 – AddFormUsageType
    [0m[0m09:49:23,521 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.4 – AddTableSecurityGroups
    [0m[33m09:49:23,568 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_security_groups‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[33m09:49:23,610 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_group_memberships‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:23,629 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.5 – AddAbbrevPrimGroup
    [0m[0m09:49:23,831 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.6 – AddGroupToCase
    [0m[0m09:49:24,066 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.7 – AddTableCaseGroups
    [0m[33m09:49:24,117 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Name ‚pk_case_groups‘ ignored for PRIMARY key. (SQL State: 42000 – Error Code: 1280)
    [0m[0m09:49:24,137 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migrating schema jlawyerdb to version 1.12.0.8 – ModifyOwnerGroup
    [0m[33m09:49:24,178 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 75) DB: Cannot change column ‚owner_group‘: used in a foreign key constraint ‚jlawyerdb/fk_group‘ (SQL State: HY000 – Error Code: 1832)
    [0m[31m09:49:24,181 ERROR [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 75) Migration of schema jlawyerdb to version 1.12.0.8 – ModifyOwnerGroup failed! Please restore backups and roll back database and code!
    [0m[31m09:49:24,197 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 75) exception caught: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException:
    Migration V1_12_0_8__ModifyOwnerGroup.sql failed
    ————————————————
    SQL State : HY000
    Error Code : 1832
    Message : Cannot change column ‚owner_group‘: used in a foreign key constraint ‚jlawyerdb/fk_group‘
    Location : db/migration/V1_12_0_8__ModifyOwnerGroup.sql (/content/j-lawyer-server.ear/j-lawyer-server-entities.jar/db/migration/V1_12_0_8__ModifyOwnerGroup.sql)
    Line : 1
    Statement : alter table cases modify owner_group VARCHAR(50) BINARY

    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:370)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.access$200(DbMigrate.java:54)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate$3.call(DbMigrate.java:284)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.jdbc.TransactionTemplate.execute(TransactionTemplate.java:74)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.applyMigrations(DbMigrate.java:281)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:246)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.access$100(DbMigrate.java:54)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:164)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:161)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.database.mysql.MySQLNamedLockTemplate.execute(MySQLNamedLockTemplate.java:60)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.database.mysql.MySQLConnection.lock(MySQLConnection.java:81)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:155)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:161)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:139)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1380)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: org.flywaydb.core.internal.sqlscript.FlywaySqlScriptException:
    Migration V1_12_0_8__ModifyOwnerGroup.sql failed
    ————————————————
    SQL State : HY000
    Error Code : 1832
    Message : Cannot change column ‚owner_group‘: used in a foreign key constraint ‚jlawyerdb/fk_group‘
    Location : db/migration/V1_12_0_8__ModifyOwnerGroup.sql (/content/j-lawyer-server.ear/j-lawyer-server-entities.jar/db/migration/V1_12_0_8__ModifyOwnerGroup.sql)
    Line : 1
    Statement : alter table cases modify owner_group VARCHAR(50) BINARY

    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.handleException(DefaultSqlScriptExecutor.java:249)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.executeStatement(DefaultSqlScriptExecutor.java:202)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.execute(DefaultSqlScriptExecutor.java:125)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:77)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:367)
    … 32 more
    Caused by: java.sql.SQLException: Cannot change column ‚owner_group‘: used in a foreign key constraint ‚jlawyerdb/fk_group‘
    at com.mysql@8.0.13//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
    at com.mysql@8.0.13//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
    at com.mysql@8.0.13//com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
    at com.mysql@8.0.13//com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:782)
    at com.mysql@8.0.13//com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:666)
    at org.jboss.ironjacamar.jdbcadapters@1.4.12.Final//org.jboss.jca.adapters.jdbc.WrappedStatement.execute(WrappedStatement.java:198)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.jdbc.JdbcTemplate.executeStatement(JdbcTemplate.java:235)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.sqlscript.StandardSqlStatement.execute(StandardSqlStatement.java:42)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.executeStatement(DefaultSqlScriptExecutor.java:189)
    … 35 more

    [0m[0m09:49:24,203 INFO [stdout] (ServerService Thread Pool — 77) Starting j-lawyer.org database migrations…
    [0m[0m09:49:24,211 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 77) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.5)
    [0m[31m09:49:24,325 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 77) exception caught: org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 1.12.0.8 (ModifyOwnerGroup)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.doValidate(Flyway.java:1467)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.access$100(Flyway.java:82)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1349)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)

    [0m[0m09:49:25,010 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 77) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@7be2e1b2
    [0m[31m09:49:25,011 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 77) 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“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    … 9 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [calendar_setup]
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    [0m[0m09:49:25,013 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 75) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@79da80fd
    [0m[31m09:49:25,014 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 75) 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“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    … 9 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [calendar_setup]
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    [0m[31m09:49:25,023 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-entities.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [calendar_setup]“,
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [calendar_setup]“
    }}
    [0m[0m09:49:25,027 INFO [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    [0m[0m09:49:25,030 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“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    WFLYCTL0448: 404 additional services are down due to their dependencies being missing or failed
    [0m[0m09:49:25,068 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    [0m[0m09:49:25,070 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
    [0m[0m09:49:25,070 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
    [0m[31m09:49:25,070 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 19008ms – Started 3035 of 3650 services (420 services failed or missing dependencies, 366 services are lazy, passive or on-demand)
    [0m

    9. März 2024 um 20:37 #5990
    j-lawyer.org
    Keymaster

    Bitte wie folgt vorgehen:

    – SQL-Statement ausführen:

    use jlawyerdb;
    update flyway_schema_history set success=1 where version=’1.12.0.8′;
    quit;

    – Dienst stoppen: sudo service j-lawyer-server stop

    – Datei löschen: wildfly/standalone/deployments/j-lawyer-server ear.failed

    – Dienst starten: sudo service j-lawyer-server restart

    VG
    Jens / j-lawyer.org

    • Diese Antwort wurde vor vor 8 months, 2 weeks von j-lawyer.org bearbeitet.
    10. März 2024 um 18:44 #5992
    Veraendert
    Participant

    Danke, das war es schon.

  • Autor
    Beiträge
3 Beiträge anzeigen - 1 bis 3 (von insgesamt 3)
  • Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.