Fehler: Anmeldedaten oder Verbindungsparameter Falsch


Startseite Foren Installation Fehler: Anmeldedaten oder Verbindungsparameter Falsch

Verschlagwortet: 

6 Beiträge anzeigen - 1 bis 6 (von insgesamt 6)
  • Autor
    Beiträge
  • #5818
    JH
    Teilnehmer

    Seit einem Updaten auf Version 2.5 war es nichtmehr möglich sich anzumelden. Die Version 2.3 lief seit März 2023 stabil.Im November wurden in einem Aufwasch erst Version 2.4 und dann 2.5 installiert. Seitdem funktioniert nichts mehr. Auch eine Neuinstallation nach vollständiger Entfernung von MySQL hat nichts gebracht. Der Server-Dienst scheint zu laufen und die Windows Defender Firewall ist wie beschrieben eingerichtet.

    Ich bin seit zwei Tagen auf der Suche nach dem Fehler und stehe kurz davor nach Alternativen zu j-lawyer zu suchen.
    Es wäre wirklich schön wenn jemand das Problem kennen würde und womöglich sogar eine Losung dafür hätte.

    Die Datei Server.log hat den folgenden Inhalt:

    2023-12-28 21:30:41,373 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Program Files\j-lawyer-server\wildfly\standalone\deployments
    2023-12-28 21:30:41,373 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
    2023-12-28 21:30:42,904 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\journal,bindingsDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\largemessages,pagingDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\paging)
    2023-12-28 21:30:43,935 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221013: Using NIO Journal
    2023-12-28 21:30:43,951 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
    2023-12-28 21:30:46,037 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
    2023-12-28 21:30:46,037 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
    2023-12-28 21:30:46,037 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
    2023-12-28 21:30:46,037 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
    2023-12-28 21:30:46,881 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221034: Waiting indefinitely to obtain live lock
    2023-12-28 21:30:46,881 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221035: Live Server Obtained live lock
    2023-12-28 21:30:49,022 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.7)
    2023-12-28 21:30:49,881 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2023-12-28 21:30:49,881 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    2023-12-28 21:30:49,881 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2023-12-28 21:30:49,881 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
    2023-12-28 21:30:52,474 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221007: Server is now live
    2023-12-28 21:30:52,474 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 75) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.6.3.jbossorg-00014 [default, nodeID=0aefc943-a5be-11ee-add2-ac220b89f2c1]
    2023-12-28 21:30:52,553 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 75) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
    2023-12-28 21:30:52,709 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 77) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „DESKTOP-83CNEBQ“. If this new address is incorrect please manually configure the connector to use the proper one.
    2023-12-28 21:30:52,709 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 77) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    2023-12-28 21:30:53,381 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA
    2023-12-28 21:30:53,381 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
    2023-12-28 21:30:53,396 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2023-12-28 21:30:53,990 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-4) AMQ151007: Resource adaptor started
    2023-12-28 21:30:53,990 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatoractivemq-ra
    2023-12-28 21:30:54,006 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
    2023-12-28 21:30:54,006 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2023-12-28 21:32:12,884 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,886 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,887 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,888 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,900 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,900 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/json-simple-2.3.0.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,901 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/log4j-over-slf4j-1.7.30.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,901 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/slf4j-api-1.7.30.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,902 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jboss-jaxrs-api_2.1_spec-1.0.2.Final.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,902 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/log4j-api-2.17.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,903 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/log4j-core-2.17.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,903 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/log4j-slf4j-impl-2.17.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,913 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,913 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,913 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,914 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,915 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,918 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/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.
    2023-12-28 21:32:12,923 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/FastInfoset.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/gmbal-api-only.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/ha-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/javax.mail_1.4.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jaxws-rt.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,924 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jaxws-tools.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,925 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/management-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,926 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/mimepull.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,927 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/policy.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/saaj-impl.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,930 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/stax-ex.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,932 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/stax2-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,933 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/streambuffer.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,934 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/woodstox-core-asl.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,936 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jaxws-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,937 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jsr181-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,939 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/javax.annotation.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,941 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/saaj-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,943 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/activation.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,944 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/jaxb-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,946 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/hamcrest-core-1.3.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,947 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry lib/org-netbeans-modules-java-j2seproject-copylibstask.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,954 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,954 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,954 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,955 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,956 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:12,957 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:13,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
    2023-12-28 21:32:13,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
    2023-12-28 21:32:13,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
    2023-12-28 21:32:13,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
    2023-12-28 21:32:13,007 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
    2023-12-28 21:32:13,022 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry lib/jollyday-0.4.7.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:13,022 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry lib/tika-app-1.5.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
    2023-12-28 21:32:38,924 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2023-12-28 21:32:38,924 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2023-12-28 21:32:45,103 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 81) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2023-12-28 21:32:45,103 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2023-12-28 21:32:45,200 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
    2023-12-28 21:32:45,582 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 81) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2023-12-28 21:32:45,582 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 82) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2023-12-28 21:32:48,493 INFO [org.hibernate.Version] (ServerService Thread Pool — 82) HHH000412: Hibernate Core {5.3.9.Final}
    2023-12-28 21:32:48,498 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 82) HHH000206: hibernate.properties not found
    2023-12-28 21:32:54,116 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 6.0.15.Final
    2023-12-28 21:32:57,969 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
    2023-12-28 21:32:58,074 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
    2023-12-28 21:32:58,221 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) 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

    2023-12-28 21:32:58,296 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
    2023-12-28 21:32:58,536 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 81) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    2023-12-28 21:32:58,750 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
    2023-12-28 21:32:58,753 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

    2023-12-28 21:32:58,753 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

    2023-12-28 21:32:58,753 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

    2023-12-28 21:32:58,754 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

    2023-12-28 21:32:58,754 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

    2023-12-28 21:32:58,754 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

    2023-12-28 21:32:58,757 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

    2023-12-28 21:32:58,763 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

    2023-12-28 21:32:58,770 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

    2023-12-28 21:32:58,777 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

    2023-12-28 21:32:58,783 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

    2023-12-28 21:32:58,789 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

    2023-12-28 21:32:58,793 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

    2023-12-28 21:32:58,797 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

    2023-12-28 21:32:58,801 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

    2023-12-28 21:32:58,807 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

    2023-12-28 21:32:58,811 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
    2023-12-28 21:32:58,813 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

    2023-12-28 21:32:58,818 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,819 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

    2023-12-28 21:32:58,826 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,838 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,844 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:58,851 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,855 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,859 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,867 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,876 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:58,885 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,890 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,895 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,901 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,905 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,910 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,914 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,921 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,927 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

    java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
    java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
    java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceRemote
    java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    java:app/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    java:module/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/ArchiveFileService!com.jdimension.jlawyer.services.ArchiveFileServiceLocal

    2023-12-28 21:32:58,935 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,938 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,944 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,952 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,959 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,965 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,972 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,978 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,984 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,993 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:58,997 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,004 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,010 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,017 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,021 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,025 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:59,031 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,039 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,046 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,052 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,057 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,062 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,068 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,074 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,079 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,083 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,090 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,097 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) WFLYEJB0473: JNDI bindings for session bean named ‚CustomerRelationsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

    java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote

    2023-12-28 21:32:59,104 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,109 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,118 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,124 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,129 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,134 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,140 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,144 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,149 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,156 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:59,161 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,167 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:59,173 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,177 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,181 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,187 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,191 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:59,197 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,202 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,209 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,216 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,220 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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.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
    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

    2023-12-28 21:32:59,225 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,229 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:32:59,234 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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

    2023-12-28 21:33:00,018 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.1.0 (Final)
    2023-12-28 21:33:00,443 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readFile)
    2023-12-28 21:33:00,443 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (writeFile)
    2023-12-28 21:33:00,444 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (createFile)
    2023-12-28 21:33:00,444 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (copyFile)
    2023-12-28 21:33:00,444 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readTextFile)
    2023-12-28 21:33:04,451 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2023-12-28 21:33:04,817 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan ‚Infinity Minus ONE +2‘ 9.4.8.Final
    2023-12-28 21:33:09,146 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2023-12-28 21:33:09,146 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 81) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2023-12-28 21:33:17,438 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 81) HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
    2023-12-28 21:33:17,438 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 82) HHH000400: Using dialect: org.hibernate.dialect.MySQL57Dialect
    2023-12-28 21:33:18,567 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 82) Envers integration enabled? : true
    2023-12-28 21:33:18,567 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 81) Envers integration enabled? : true
    2023-12-28 21:33:20,118 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 83) WFLYCLINF0002: Started client-mappings cache from ejb container
    2023-12-28 21:33:26,695 INFO [stdout] (ServerService Thread Pool — 82) Starting j-lawyer.org database migrations…

    2023-12-28 21:33:26,711 INFO [org.flywaydb.core.internal.license.VersionPrinter] (ServerService Thread Pool — 82) Flyway Community Edition 5.2.1 by Boxfuse
    2023-12-28 21:33:26,718 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 82) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.7)
    2023-12-28 21:33:27,995 INFO [org.flywaydb.core.internal.command.DbValidate] (ServerService Thread Pool — 82) Successfully validated 153 migrations (execution time 00:00.469s)
    2023-12-28 21:33:28,033 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 82) Current version of schema jlawyerdb: 1.13.0.1
    2023-12-28 21:33:28,034 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 82) Migrating schema jlawyerdb to version 1.13.0.2 – AddFieldsToContacts
    2023-12-28 21:33:28,359 WARN [org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor] (ServerService Thread Pool — 82) DB: Duplicate column name ‚district‘ (SQL State: 42S21 – Error Code: 1060)
    2023-12-28 21:33:28,363 ERROR [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 82) Migration of schema jlawyerdb to version 1.13.0.2 – AddFieldsToContacts failed! Please restore backups and roll back database and code!
    2023-12-28 21:33:29,114 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 82) exception caught: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException:
    Migration V1_13_0_2__AddFieldsToContacts.sql failed
    —————————————————
    SQL State : 42S21
    Error Code : 1060
    Message : Duplicate column name ‚district‘
    Location : db/migration/V1_13_0_2__AddFieldsToContacts.sql (C:\Program Files\j-lawyer-server\wildfly\bin\content\j-lawyer-server.ear\j-lawyer-server-entities.jar\db\migration\V1_13_0_2__AddFieldsToContacts.sql)
    Line : 1
    Statement : alter table contacts add district VARCHAR(250) BINARY

    at org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:370)
    at org.flywaydb.core.internal.command.DbMigrate.access$200(DbMigrate.java:54)
    at org.flywaydb.core.internal.command.DbMigrate$3.call(DbMigrate.java:284)
    at org.flywaydb.core.internal.jdbc.TransactionTemplate.execute(TransactionTemplate.java:74)
    at org.flywaydb.core.internal.command.DbMigrate.applyMigrations(DbMigrate.java:281)
    at org.flywaydb.core.internal.command.DbMigrate.migrateGroup(DbMigrate.java:246)
    at org.flywaydb.core.internal.command.DbMigrate.access$100(DbMigrate.java:54)
    at org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:164)
    at org.flywaydb.core.internal.command.DbMigrate$2.call(DbMigrate.java:161)
    at org.flywaydb.core.internal.database.mysql.MySQLNamedLockTemplate.execute(MySQLNamedLockTemplate.java:60)
    at org.flywaydb.core.internal.database.mysql.MySQLConnection.lock(MySQLConnection.java:81)
    at org.flywaydb.core.internal.schemahistory.JdbcTableSchemaHistory.lock(JdbcTableSchemaHistory.java:155)
    at org.flywaydb.core.internal.command.DbMigrate.migrateAll(DbMigrate.java:161)
    at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:139)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:1380)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: org.flywaydb.core.internal.sqlscript.FlywaySqlScriptException:
    Migration V1_13_0_2__AddFieldsToContacts.sql failed
    —————————————————
    SQL State : 42S21
    Error Code : 1060
    Message : Duplicate column name ‚district‘
    Location : db/migration/V1_13_0_2__AddFieldsToContacts.sql (C:\Program Files\j-lawyer-server\wildfly\bin\content\j-lawyer-server.ear\j-lawyer-server-entities.jar\db\migration\V1_13_0_2__AddFieldsToContacts.sql)
    Line : 1
    Statement : alter table contacts add district VARCHAR(250) BINARY

    at org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.handleException(DefaultSqlScriptExecutor.java:249)
    at org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.executeStatement(DefaultSqlScriptExecutor.java:202)
    at org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.execute(DefaultSqlScriptExecutor.java:125)
    at org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:77)
    at org.flywaydb.core.internal.command.DbMigrate.doMigrateGroup(DbMigrate.java:367)
    … 32 more
    Caused by: java.sql.SQLSyntaxErrorException: Duplicate column name ‚district‘
    at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:120)
    at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122)
    at com.mysql.cj.jdbc.StatementImpl.executeInternal(StatementImpl.java:782)
    at com.mysql.cj.jdbc.StatementImpl.execute(StatementImpl.java:666)
    at org.jboss.jca.adapters.jdbc.WrappedStatement.execute(WrappedStatement.java:198)
    at org.flywaydb.core.internal.jdbc.JdbcTemplate.executeStatement(JdbcTemplate.java:235)
    at org.flywaydb.core.internal.sqlscript.StandardSqlStatement.execute(StandardSqlStatement.java:42)
    at org.flywaydb.core.internal.sqlscript.DefaultSqlScriptExecutor.executeStatement(DefaultSqlScriptExecutor.java:189)
    … 35 more

    2023-12-28 21:33:29,139 INFO [stdout] (ServerService Thread Pool — 81) Starting j-lawyer.org database migrations…

    2023-12-28 21:33:29,144 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 81) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.7)
    2023-12-28 21:33:29,236 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 81) exception caught: org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 1.13.0.2 (AddFieldsToContacts)
    at org.flywaydb.core.Flyway.doValidate(Flyway.java:1467)
    at org.flywaydb.core.Flyway.access$100(Flyway.java:82)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:1349)
    at org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at org.jboss.threads.JBossThread.run(JBossThread.java:485)

    2023-12-28 21:33:36,311 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 82) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@6a35f1d8
    2023-12-28 21:33:36,311 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 81) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@274614c3
    2023-12-28 21:33:36,313 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at 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.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at 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.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    2023-12-28 21:33:36,313 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 81) 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.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
    at 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.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at 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.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
    at org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    2023-12-28 21:33:36,339 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]“
    }}
    2023-12-28 21:33:36,346 INFO [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2023-12-28 21:33:36,350 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-ejb.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-entities.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
    2023-12-28 21:33:38,914 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2023-12-28 21:33:38,924 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
    2023-12-28 21:33:38,925 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
    2023-12-28 21:33:38,925 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 416121ms – Started 3035 of 3650 services (420 services failed or missing dependencies, 366 services are lazy, passive or on-demand)

    #5821
    j-lawyer.org
    Administrator

    Guten Abend.

    Ich meine dass hier nicht das gesamte Bild dargestellt wird – die Datenbank ist der Meinung, sie sei auf einem Versionsstand 1.13, nicht 2.3 oder später:

    > 2023-12-28 21:33:28,033 INFO [org.flywaydb.core.internal.command.DbMigrate] (ServerService Thread Pool — 82) Current version of schema jlawyerdb: 1.13.0.1

    Und wenn das Updateproblem im November auftrat – warum dann so späte Meldung? Man kann ein Update für 55 EUR durchführen lassen – das wäre in jedem Fall kostengünstiger als eine tagelange Fehlersuche.

    Ich kann auch nicht deuten, auf was die Information „Ich bin seit zwei Tagen auf der Suche nach dem Fehler und stehe kurz davor nach Alternativen zu j-lawyer zu suchen.“ abzielt – wir bieten hier eine kostenfreie Software und einen ziemlich guten Support – kostenfrei über das Forum oder zu wirklich angenehmen Preisen per Fernwartung. Das oben hört sich schon ein wenig nach Drohung an – unklar warum.

    Ich kann hier ohne die genaue Historie (wurde mehrfach aktualisiert, wurde ggf. eine Neuinstallation über eine bestehende Installation durchgeführt, wurde ein Rücksicherung aus Backup ausgeführt, …) aus der Ferne nicht helfen. Es wäre eine Fernwartung notwendig. Bei Interesse einfach an die Mailadresse im Impressum wenden.

    VG
    Jens / j-lawyer.org

    #5822
    JH
    Teilnehmer

    Guten Abend und vielen Dank für die schnelle Reaktion,

    ich habe versucht das Problem so gut wie es geht darzustellen. Im März 2023 hatte ich nach einer Software gesucht mit der ich regelmäßig auf mein beA Postfach zugreifen kann um eingehende NAchrichten herunterzuladen. Bei dieser Suche bin ich schließlich auf j-lawyer gestoßen. Die erste installation wurde im März 2023 mit den Dateien j-lawyer-server_windows-x64_2_3_0_22.exe und j-lawyer-client_windows-x64_2_3_0_1.exe vorgenommen. Ich hatte mir dann extra ein BeA Softwarezertifikat bestellt und j-lawyer als Client für das BeA und e-Mails verwendet. Sicherungen habe ich aber weiter über die Seite bea-brak.de gemacht.

    Da ich in meinem Hauptjob angestellt bin und meine eigenen Kanzlei nur nebenbei betreibe war das kein Problem.

    Als ich im November die Software wieder nutzen wollte. Stelte ich fest, dass zwischenzeitlich zwei Updates herausgekommen waren. Über die bestehende Installation habe ich erst die Versionen j-lawyer-client_windows-x64_2_4_0_2 und j-lawyer-server_windows-x64_2_4_0_13 gespielt und dann die Versionen j-lawyer-client_windows-x64_2_5_0_0 und j-lawyer-server_windows-x64_2_5_0_4.

    Als dann ein Anmelden nicht mehr möglich war habe ich dies erstmal nur zur Kenntnis genommen und meine beA Nachrichten manuell abgerufen. Meist bin ich eher gestaltend oder beratend Tätig, über die Feiertage habe ich aber doch einige klassische Fälle angenommen für die man eine Anwaltssoftware nutzen könnte. Deswegen habe ich mich vor zwei Tagen hingesetzt und versucht j-lawyer wieder zum laufen zu bekommen. Leider erfolglos.

    Das Scheitern war ziemlich frustrierend. Normalerweise bekommen ich solche Probleme in den Griff. Ich habe mir noch nie durch ein Update ein fuktionierendes System zerschossen und konnte mir bisher auch nicht vorstellen, Hilfe zu brauchen.

    Dass die Möglichkeit besteht diese zu bekommen ist jedenfalls ein Lichtblick.

    #5823
    j-lawyer.org
    Administrator

    Die Sequenz
    – Installation
    – Update 1
    – Update 2

    führt nicht zum obigen Fehler. Sie schrieben im ersten Post u.a. „Auch eine Neuinstallation nach vollständiger Entfernung von MySQL hat nichts gebracht.“, also ist es in etwa so?

    – Installation
    – Update 1
    – Update 2
    – Deinstallation
    – Neuinstallation
    – Rücksicherung aus Datensicherung

    ?

    Bereits bei fehlschlagendem Login nach Update wäre ein Eintrag im Forum das Mittel der Wahl gewesen, die danach folgenden Aktionen waren sehr wahrscheinlich eher kontraproduktiv und ich hoffe dass eine vollständige Datensicherung vorliegt.

    Grundsätzlich gibt es zwei Optionen:

    (1) Wenn das System sowieso nur als beA-Viewer genutzt wurde und keine Daten (Akten, Adressen, Dokumente) erstellt wurden, dann einmal deinstallieren und neu installieren.

    (1) Es liegt eine vollständige und funktionierende Datensicherung vor, die zweifelsfrei zur Rücksicherung geeignet ist: dann könnten Sie eine vollständige Deinstallation durchführen, neu installieren und das Backup einspielen mittels der ebenfalls in der Installation verfügbaren Anwendung „Backupmanager“.

    (3) Sofern es nur geringste Zweifel an der Wiederherstellbarkeit aus Backup gibt: nichts unternehmen, eine Fernwartung anfragen.

    Hinweise zur vollständigen Deinstallation:
    – j-lawyer Server deinstallieren. Die Deinstallation lässt alle nutzerspezifischen Einstellungsdateien auf Festplatte zurück, bspw. um auch nach Deinstallation noch das Datenbankpasswort rekonstruieren zu können. Vor einer Neuinstallation daher C:\Programme\j-lawyer-server löschen
    – MySQL deinstallieren. Auch MySQL löscht nicht die auf dem System vorhandenen Datenbanken und Zugänge/Nutzer. Daher (in der Regel) C:\ProgramData\MySQL löschen – wenn sichergestellt ist, dass keine anderen Anwendungen MySQL verwenden.

    #5824
    j-lawyer.org
    Administrator

    Zu Dokuzwecken: Das Problem wurde per Fernwartung behoben. Wahrscheinlichste Ursache ist ein Timeout beim Updaten der Datenbank. Für diesen Vorgang gibt es ein Limit von 5min. Während der Fernwartung war die Festplatte (eine mechanische Platte / HDD) auf dem Gerät zu 100% ausgelastet.

    VG
    Jens / j-lawyer.org

    #5825
    JH
    Teilnehmer

    Jetzt funktioniert wieder alles.
    Vielen Dank für die schnelle und kompetente Hilfe!

    VG und einen guten Rutsch!

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