Zum Inhalt springen
Zurück zur Startseite

Kanzleisoftware | Kostenlos | Open Source

Kanzleisoftware | Kostenlos | Open Source

  • Startseite
  • Aktuelles
  • Funktionen
  • Download
  • Informationen
    • Screenshots
    • Online-Demo
    • Meinungen…
    • Medienecho
    • Installation
      • Installation Windows
      • Installation Linux
      • Installation macOS
    • Kurzanleitung
    • Dokumentation
    • Support
    • Lizenz
    • Entscheidungshilfe für Versand via beA
  • Community
    • Mitmachen!
    • Newsletter
    • Unterstützer
    • Forum
    • Wiki & Tickets
    • Vorlagen
  • Kaufen
    • cloudbasiert nutzen
    • KI-Funktionen integrieren
    • Services
    • j-lawyer.BOX Kanzleiserver
    • j-lawyer.BOX virtualisiert
    • Merchandising
  • Impressum
Startseite » Foren » Hilfe bei Problemen » Erstanmeldung schlägt fehl

Erstanmeldung schlägt fehl


Startseite › Foren › Hilfe bei Problemen › Erstanmeldung schlägt fehl

Verschlagwortet: Login, MySQL, Server, Windows

  • This topic has 7 Antworten, 2 Stimmen, and was last updated vor 1 years, 6 months by j-lawyer.org.
8 Beiträge anzeigen - 1 bis 8 (von insgesamt 8)
  • Autor
    Beiträge
  • 24. September 2023 um 15:26 #5578
    bob
    Participant

    Hi, ich habe gestern eine Installation von Server+Client auf einer Win10 Maschine durchgeführt und muss leider feststellen dass der Login nicht funktioniert.

    Ich habe mehrmals deinstalliert und wieder installiert. Auch MySQL hab ich jedes mal runter geschmissen. Dann hab ich mal die vorherige Version probiert, brachte auch nix.

    Hier mein server.log
    `
    2023-09-24 14:15:04,898 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Program Files\j-lawyer-server\wildfly\standalone\deployments
    2023-09-24 14:15:04,899 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
    2023-09-24 14:15:04,912 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/jlawyerdb]
    2023-09-24 14:15:04,913 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    2023-09-24 14:15:04,963 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
    2023-09-24 14:15:05,036 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.2.4.Final (Apache CXF 3.2.7)
    2023-09-24 14:15:05,101 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) 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-09-24 14:15:05,153 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221013: Using NIO Journal
    2023-09-24 14:15:05,203 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
    2023-09-24 14:15:05,203 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
    2023-09-24 14:15:05,204 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
    2023-09-24 14:15:05,204 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
    2023-09-24 14:15:05,230 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221034: Waiting indefinitely to obtain live lock
    2023-09-24 14:15:05,230 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221035: Live Server Obtained live lock
    2023-09-24 14:15:05,320 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2023-09-24 14:15:05,320 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    2023-09-24 14:15:05,320 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    2023-09-24 14:15:05,320 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2023-09-24 14:15:05,396 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221007: Server is now live
    2023-09-24 14:15:05,397 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 74) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.6.3.jbossorg-00014 [default, nodeID=fe95c002-5ad3-11ee-ac54-b06ebf2e3476]
    2023-09-24 14:15:05,450 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 75) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
    2023-09-24 14:15:05,452 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0007: Registered connection factory java:/JmsXA
    2023-09-24 14:15:05,453 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0011: Unbound JCA ConnectionFactory [java:/JmsXA]
    2023-09-24 14:15:05,455 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0119: Unbinding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2023-09-24 14:15:05,457 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-3AOTFP6“. If this new address is incorrect please manually configure the connector to use the proper one.
    2023-09-24 14:15:05,458 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 77) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    2023-09-24 14:15:05,494 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-6) AMQ151007: Resource adaptor started
    2023-09-24 14:15:05,495 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatoractivemq-ra
    2023-09-24 14:15:05,496 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
    2023-09-24 14:15:05,496 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2023-09-24 14:15:11,205 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-09-24 14:15:11,206 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-09-24 14:15:11,206 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-09-24 14:15:11,206 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-09-24 14:15:11,209 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,210 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-09-24 14:15:11,214 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-09-24 14:15:11,214 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-09-24 14:15:11,214 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-09-24 14:15:11,214 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-09-24 14:15:11,214 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-09-24 14:15:11,215 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,218 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-09-24 14:15:11,219 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-09-24 14:15:11,220 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-09-24 14:15:11,222 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-09-24 14:15:11,223 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-09-24 14:15:11,224 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-09-24 14:15:11,225 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-09-24 14:15:11,226 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-09-24 14:15:11,228 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-09-24 14:15:11,229 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-09-24 14:15:11,230 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-09-24 14:15:11,231 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-09-24 14:15:11,232 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-09-24 14:15:11,234 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-09-24 14:15:11,235 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-09-24 14:15:11,236 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-09-24 14:15:11,241 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-09-24 14:15:11,241 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-09-24 14:15:11,241 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-09-24 14:15:11,241 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-09-24 14:15:11,242 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-09-24 14:15:11,243 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-09-24 14:15:11,257 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
    2023-09-24 14:15:11,257 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
    2023-09-24 14:15:11,257 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
    2023-09-24 14:15:11,257 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
    2023-09-24 14:15:11,257 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
    2023-09-24 14:15:11,269 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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-09-24 14:15:11,269 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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-09-24 14:15:11,494 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2023-09-24 14:15:11,550 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2023-09-24 14:15:11,825 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 77) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2023-09-24 14:15:11,825 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 78) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2023-09-24 14:15:11,834 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
    2023-09-24 14:15:11,844 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 78) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2023-09-24 14:15:11,849 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 77) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2023-09-24 14:15:11,939 INFO [org.hibernate.Version] (ServerService Thread Pool — 78) HHH000412: Hibernate Core {5.3.9.Final}
    2023-09-24 14:15:11,941 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 78) HHH000206: hibernate.properties not found
    2023-09-24 14:15:12,072 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 6.0.15.Final
    2023-09-24 14:15:12,077 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 78) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    2023-09-24 14:15:12,365 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
    2023-09-24 14:15:12,373 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
    2023-09-24 14:15:12,410 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
    2023-09-24 14:15:12,418 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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-09-24 14:15:12,644 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan ‚Infinity Minus ONE +2‘ 9.4.8.Final
    2023-09-24 14:15:12,671 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
    2023-09-24 14:15:12,673 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-09-24 14:15:12,673 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-09-24 14:15:12,673 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-09-24 14:15:12,673 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-09-24 14:15:12,673 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-09-24 14:15:12,733 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-09-24 14:15:12,928 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
    2023-09-24 14:15:12,930 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-09-24 14:15:12,933 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-09-24 14:15:12,937 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-09-24 14:15:12,943 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-09-24 14:15:12,946 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-09-24 14:15:12,949 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-09-24 14:15:12,952 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-09-24 14:15:12,960 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-09-24 14:15:12,964 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-09-24 14:15:12,970 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-09-24 14:15:12,974 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-09-24 14:15:12,979 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-09-24 14:15:12,982 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-09-24 14:15:12,990 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-09-24 14:15:13,034 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 77) WFLYCLINF0002: Started client-mappings cache from ejb container
    2023-09-24 14:15:13,038 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-09-24 14:15:13,048 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-09-24 14:15:13,052 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-09-24 14:15:13,057 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-09-24 14:15:13,088 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-09-24 14:15:13,096 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-09-24 14:15:13,100 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.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
    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

    2023-09-24 14:15:13,105 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-09-24 14:15:13,108 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-09-24 14:15:13,112 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-09-24 14:15:13,115 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-09-24 14:15:13,119 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-09-24 14:15:13,124 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-09-24 14:15:13,128 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-09-24 14:15:13,132 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-09-24 14:15:13,135 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-09-24 14:15:13,139 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-09-24 14:15:13,142 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-09-24 14:15:13,146 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-09-24 14:15:13,150 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-09-24 14:15:13,155 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-09-24 14:15:13,159 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-09-24 14:15:13,163 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-09-24 14:15:13,166 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-09-24 14:15:13,170 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-09-24 14:15:13,173 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-09-24 14:15:13,177 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-09-24 14:15:13,182 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-09-24 14:15:13,185 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-09-24 14:15:13,189 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-09-24 14:15:13,193 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-09-24 14:15:13,196 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-09-24 14:15:13,200 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-09-24 14:15:13,204 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-09-24 14:15:13,208 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-09-24 14:15:13,211 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.CustomerRelationsServiceRemote
    java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceRemote
    java:global/j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    java:app/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    java:module/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/CustomerRelationsService!com.jdimension.jlawyer.services.CustomerRelationsServiceLocal

    2023-09-24 14:15:13,217 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-09-24 14:15:13,220 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.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
    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

    2023-09-24 14:15:13,225 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.SecurityServiceRemote
    java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
    java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceRemote
    java:global/j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    java:app/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    java:module/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal
    ejb:j-lawyer-server/j-lawyer-server-ejb/SecurityService!com.jdimension.jlawyer.services.SecurityServiceLocal

    2023-09-24 14:15:13,230 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-09-24 14:15:13,234 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-09-24 14:15:13,238 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-09-24 14:15:13,242 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-09-24 14:15:13,246 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-09-24 14:15:13,250 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-09-24 14:15:13,255 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-09-24 14:15:13,260 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-09-24 14:15:13,264 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-09-24 14:15:13,268 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-09-24 14:15:13,271 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-09-24 14:15:13,274 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-09-24 14:15:13,278 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-09-24 14:15:13,281 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-09-24 14:15:13,285 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-09-24 14:15:13,290 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-09-24 14:15:13,293 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-09-24 14:15:13,297 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-09-24 14:15:13,337 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.1.0 (Final)
    2023-09-24 14:15:13,481 WARN [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (writeFile)
    2023-09-24 14:15:13,481 WARN [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readTextFile)
    2023-09-24 14:15:13,481 WARN [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (copyFile)
    2023-09-24 14:15:13,481 WARN [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (createFile)
    2023-09-24 14:15:13,492 WARN [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0131: EJB com.jdimension.jlawyer.services.SystemManagement should not have a final or static method (readFile)
    2023-09-24 14:15:13,703 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 77) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2023-09-24 14:15:14,056 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 78) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2023-09-24 14:15:14,069 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2023-09-24 14:15:15,951 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool — 77) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
    at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
    at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
    at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
    at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:68)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:904)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:935)
    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: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:835)
    at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:455)
    at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
    at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:207)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
    … 38 more
    Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:105)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:151)
    at com.mysql.cj.exceptions.ExceptionFactory.createCommunicationsException(ExceptionFactory.java:167)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:91)
    at com.mysql.cj.NativeSession.connect(NativeSession.java:152)
    at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:955)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
    … 42 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at com.mysql.cj.protocol.StandardSocketFactory.connect(StandardSocketFactory.java:155)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:65)
    … 45 more

    2023-09-24 14:15:15,982 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 77) HHH000342: Could not obtain connection to query metadata : javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jlawyerdb
    2023-09-24 14:15:15,985 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 77) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.jboss.as.jpa.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: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:904)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:935)
    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.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
    at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
    at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    … 21 more

    2023-09-24 14:15:16,079 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool — 78) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
    at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
    at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
    at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
    at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcEnvironmentInitiator.java:180)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:68)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:904)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:935)
    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: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:835)
    at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:455)
    at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
    at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:207)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
    … 38 more
    Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:105)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:151)
    at com.mysql.cj.exceptions.ExceptionFactory.createCommunicationsException(ExceptionFactory.java:167)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:91)
    at com.mysql.cj.NativeSession.connect(NativeSession.java:152)
    at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:955)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
    … 42 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at com.mysql.cj.protocol.StandardSocketFactory.connect(StandardSocketFactory.java:155)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:65)
    … 45 more

    2023-09-24 14:15:16,094 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 78) HHH000342: Could not obtain connection to query metadata : javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jlawyerdb
    2023-09-24 14:15:16,095 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 78) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.jboss.as.jpa.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: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    at org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:904)
    at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:935)
    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.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
    at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
    at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
    at org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    … 21 more

    2023-09-24 14:15:16,117 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {„WFLYCTL0080: Failed services“ => {
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“,
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“
    }}
    2023-09-24 14:15:16,131 INFO [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2023-09-24 14:15:16,151 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“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    WFLYCTL0448: 354 additional services are down due to their dependencies being missing or failed
    2023-09-24 14:15:16,181 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2023-09-24 14:15:16,185 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://0.0.0.0:9990/management
    2023-09-24 14:15:16,185 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://0.0.0.0:9990
    2023-09-24 14:15:16,189 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 14860ms – Started 2737 of 3302 services (370 services failed or missing dependencies, 366 services are lazy, passive or on-demand)
    2023-09-24 14:15:40,999 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default task-1) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
    at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
    at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
    at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
    at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:180)
    at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:265)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:406)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:323)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:415)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:376)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:353)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.verify(JaasCallbackHandler.java:205)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.access$200(JaasCallbackHandler.java:81)
    at org.jboss.as.domain.management.security.JaasCallbackHandler$SecurityRealmImpl$RealmIdentityImpl.verifyEvidence(JaasCallbackHandler.java:356)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1978)
    at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:759)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:992)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:902)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:839)
    at org.wildfly.security.sasl.util.TrustManagerSaslServerFactory.lambda$createSaslServer$0(TrustManagerSaslServerFactory.java:96)
    at org.wildfly.security.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:117)
    at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58)
    at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106)
    at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:59)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
    at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486)
    at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
    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)
    Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:835)
    at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:455)
    at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
    at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:207)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
    … 53 more
    Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:105)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:151)
    at com.mysql.cj.exceptions.ExceptionFactory.createCommunicationsException(ExceptionFactory.java:167)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:91)
    at com.mysql.cj.NativeSession.connect(NativeSession.java:152)
    at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:955)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
    … 57 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at com.mysql.cj.protocol.StandardSocketFactory.connect(StandardSocketFactory.java:155)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:65)
    … 60 more

    2023-09-24 14:21:40,050 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default task-1) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
    at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
    at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
    at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
    at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:180)
    at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:265)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:406)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:323)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:415)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:376)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:353)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.verify(JaasCallbackHandler.java:205)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.access$200(JaasCallbackHandler.java:81)
    at org.jboss.as.domain.management.security.JaasCallbackHandler$SecurityRealmImpl$RealmIdentityImpl.verifyEvidence(JaasCallbackHandler.java:356)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1978)
    at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:759)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:992)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:902)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:839)
    at org.wildfly.security.sasl.util.TrustManagerSaslServerFactory.lambda$createSaslServer$0(TrustManagerSaslServerFactory.java:96)
    at org.wildfly.security.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:117)
    at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58)
    at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106)
    at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:59)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
    at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486)
    at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
    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)
    Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:835)
    at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:455)
    at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
    at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:207)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
    … 53 more
    Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:105)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:151)
    at com.mysql.cj.exceptions.ExceptionFactory.createCommunicationsException(ExceptionFactory.java:167)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:91)
    at com.mysql.cj.NativeSession.connect(NativeSession.java:152)
    at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:955)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
    … 57 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at com.mysql.cj.protocol.StandardSocketFactory.connect(StandardSocketFactory.java:155)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:65)
    … 60 more

    2023-09-24 14:21:46,288 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (default task-1) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: IJ031084: Unable to create connection
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1325)
    at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.getConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:499)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:632)
    at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:604)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:624)
    at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
    at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
    at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
    at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
    at org.jboss.security.auth.spi.DatabaseServerLoginModule.getUsersPassword(DatabaseServerLoginModule.java:180)
    at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:265)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
    at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
    at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
    at javax.security.auth.login.LoginContext.login(LoginContext.java:587)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:406)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.proceedWithJaasLogin(JBossCachedAuthenticationManager.java:345)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:323)
    at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:415)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:376)
    at org.jboss.as.security.service.SimpleSecurityManager.authenticate(SimpleSecurityManager.java:353)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.verify(JaasCallbackHandler.java:205)
    at org.jboss.as.domain.management.security.JaasCallbackHandler.access$200(JaasCallbackHandler.java:81)
    at org.jboss.as.domain.management.security.JaasCallbackHandler$SecurityRealmImpl$RealmIdentityImpl.verifyEvidence(JaasCallbackHandler.java:356)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1978)
    at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:759)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:992)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:902)
    at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:839)
    at org.wildfly.security.sasl.util.TrustManagerSaslServerFactory.lambda$createSaslServer$0(TrustManagerSaslServerFactory.java:96)
    at org.wildfly.security.sasl.plain.PlainSaslServer.evaluateResponse(PlainSaslServer.java:117)
    at org.wildfly.security.sasl.util.AuthenticationCompleteCallbackSaslServerFactory$1.evaluateResponse(AuthenticationCompleteCallbackSaslServerFactory.java:58)
    at org.wildfly.security.sasl.util.AuthenticationTimeoutSaslServerFactory$DelegatingTimeoutSaslServer.evaluateResponse(AuthenticationTimeoutSaslServerFactory.java:106)
    at org.wildfly.security.sasl.util.SecurityIdentitySaslServerFactory$1.evaluateResponse(SecurityIdentitySaslServerFactory.java:59)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
    at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
    at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486)
    at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
    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)
    Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)
    at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:835)
    at com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:455)
    at com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:240)
    at com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:207)
    at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
    … 53 more
    Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

    The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:105)
    at com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:151)
    at com.mysql.cj.exceptions.ExceptionFactory.createCommunicationsException(ExceptionFactory.java:167)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:91)
    at com.mysql.cj.NativeSession.connect(NativeSession.java:152)
    at com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:955)
    at com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:825)
    … 57 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:607)
    at com.mysql.cj.protocol.StandardSocketFactory.connect(StandardSocketFactory.java:155)
    at com.mysql.cj.protocol.a.NativeSocketConnection.connect(NativeSocketConnection.java:65)
    … 60 more

    `

    24. September 2023 um 15:28 #5581
    j-lawyer.org
    Keymaster

    Zumindest bei diesem letzten Startversuch ist der Datenbankdienst nicht erreichbar gewesen:

    > The driver has not received any packets from the server.

    Läuft der MySQL – Dienst?

    6. Oktober 2023 um 22:11 #5627
    bob
    Participant

    Sorry, ich hatte nicht die Zeit zu antworten.

    Ich habe es vorhin mal nachgeprüft und der Dienst lief nicht.
    Tatsächlich sieht es danach aus als würde MySQL garnicht vom Installer installiert und konfiguriert werden.
    Nur der mysql-installer-community wird installiert.
    Verstehe ich die Installationsanleitung falsch und man muss sich den MySQL server selbst installieren und einrichten oder funktioniert der jlawyer-installer nicht richtig?
    Jedenfalls wird MySQL nicht in den installierten Programmen aufgeführt und es gibt weder in C:\Programme noch in C:\Programme (x86) ein Verzeichnis von MySQL (nur dem installer).

    6. Oktober 2023 um 22:13 #5628
    j-lawyer.org
    Keymaster

    Bitte mal unter „Dienste“ schauen, ob dort ein Dienst „MySQL57“ installiert ist.

    7. Oktober 2023 um 13:00 #5629
    bob
    Participant

    Aso sorry, da hab ich mich unklar ausgedrückt:

    Es ist kein MySQL Dienst installiert.

    7. Oktober 2023 um 19:56 #5630
    j-lawyer.org
    Keymaster

    Wurde bereits versucht, den j-lawyer.org Server ein weiteres Mal zu installieren?

    Ggf. die Installation mal per Rechtsklick und „als Administrator ausführen“ starten.

    7. Oktober 2023 um 20:57 #5631
    bob
    Participant

    Jop, hatte es bereits mehrmals versucht mit neu installieren (auch als admin). Leider immer das gleiche Ergebnis.

    Auch gerade eben habe ich den jlawyer-server deinstalliert und erneut als administrator installiert. Leider weiterhin ohne erfolg (Login funktioniert nicht. MySQL scheint nicht installiert zu sein und es gibt auch keinen MySQL Dienst).

    Ich bin echt ratlos. Das ist eine frische Win10 Installation.

    • Diese Antwort wurde vor vor 1 years, 7 months von bob bearbeitet.
    15. Oktober 2023 um 20:50 #5661
    j-lawyer.org
    Keymaster

    Sorry, die Nachricht hat mich im Urlaub erreicht und war dann etwas vom Radar verschwunden. Ich kann hier gern mittels Supportauftrag / Fernwartung helfen, bei Interesse.

    Viele Grüße
    Jens / j-lawyer.org

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

Log in / Register


Soziale Links

j-lawyer.CLOUD

✓Hosting in Deutschland ✓Support ✓einfach und sicher

Kostenlos testen

Unterstützen

Sponsor werden
Direkt unterstützen
Amazon-Wunschliste aufrufen
Merchandising-Artikel kaufen

Newsletter

Wir benutzen MailChimp als Newsletterplattform. Durch das Absenden dieses Formulars stimmen Sie der Verarbeitung Ihrer Daten entsprechend der Terms of Service und Privacy Policy zu.

Aktuelles

  • j-lawyer.org 3.2 veröffentlicht 24. April 2025
  • Vorankündigung: j-lawyer.org 3.2 13. April 2025
  • neues Falldatenblatt für notarielle Kaufverträge 8. Februar 2025
  • Anwender(-innen)treffen in Leipzig 6. Februar 2025
  • Drebis wird eingestellt 23. Januar 2025

Forum durchsuchen

Forum

  • j-lawyer-server-Dienst startet nicht
    vor 5 days, 21 hours
  • Problem Installation Update auf Version
    vor 6 days, 1 hours
  • E-Rechnung – Fehlende Identifikation des Ausstellers
    vor 5 days, 16 hours
  • Notification Badge zurücksetzen?
    vor 1 weeks, 4 days
  • Anmelde- oder Verbindungsparameter falsch
    vor 2 weeks, 1 days

Anmelden

Anmelden
Registrieren Passwort vergessen

Neues

  • j-lawyer.org 3.2 veröffentlicht
  • Vorankündigung: j-lawyer.org 3.2
  • neues Falldatenblatt für notarielle Kaufverträge
  • Anwender(-innen)treffen in Leipzig
  • Drebis wird eingestellt
  • Fehlerkorrektur E-Mail-Integration
  • „Assistent Ingo“ – KI-Funktionen in j-lawyer.org integriert
  • j-lawyer.org 3.1 veröffentlicht
  • Vorabinformation: j-lawyer.org 3.1
  • j-lawyer.org 3.0 veröffentlicht
  • Brown Bag Session am 01.11.: j-lawyer.org 3.0
  • Vorschau: j-lawyer.org 2.7
  • Vorschau: elektronische Rechnungen
  • j-lawyer.org 2.6.1 veröffentlicht
  • E-POST: Korrektur bzgl. Einschreiben notwendig
  • Brown Bag Session am 15.03.: j-lawyer.org 2.6
  • j-lawyer.org 2.6 veröffentlicht
  • Bedarfserfassung WebAkte-Integration
  • Thunderbird-Add-On: Interview mit Maximilian Steinert
  • Vorschau: j-lawyer.org 2.6

Tags

1.8.1 1.9 1.9.1 1.10 1.11 2.0 2.3 2.6 Anwaltspostfach beA Berechnung BRAK Buchhaltung Client Community Datensicherung Dokumente Download Drebis E-Mail Installation Installer j-lawyer.BOX j-lawyer.org Kalender Leipzig LibreOffice Linux Meeting Nextcloud Open Source PDF Plugin Projekt Rechnungen Release RVG Schnittstelle Server Synchronisation Test Update Veröffentlichung Vorlagen Windows

Navigation

  • Community
    • Aktuelles
    • Forum
    • Mitmachen!
    • Newsletter
    • Unterstützer
    • Vorlagen
    • Wiki & Tickets
  • Download
  • Funktionen
  • Kaufen
    • j-lawyer.BOX Kanzleiserver
    • j-lawyer.BOX virtualisiert
    • Merchandising
    • Services
      • E-POST BUSINESS freischalten
  • Startseite
  • Downloads für Windows, Linux und Mac
  • Informationen
    • Entscheidungshilfe für Versand via beA
    • Medienecho
    • Meinungen…
    • Online-Demo
    • Screenshots
    • Installation
      • Installation Linux
      • Installation macOS
      • Installation Windows
        • Firewallkonfiguration für Server
    • Kurzanleitung
    • Dokumentation
    • Support
    • Lizenz
  • Impressum
    • Datenschutz

Suche

Newsletter

Wir benutzen MailChimp als Newsletterplattform. Durch das Absenden dieses Formulars stimmen Sie der Verarbeitung Ihrer Daten entsprechend der Terms of Service und Privacy Policy zu.

Unterstützer

j-lawyer.org nutzt den Multi-Platform Java Installer Builder der ej-technologies GmbH
install4j

 

Trademarks

MySQL®, Java®, JBoss®, LibreOffice®, OpenOffice.org® and Linux® are registered trademarks of their respective owners. The owner of j-lawyer.org uses these products without modification and has otherwise no business relation with the companies owning these trademarks.

· © 2025 j-lawyer.org ·

Diese Website benutzt ausschließlich technisch notwendige Cookies, jedoch keine von Drittanbietern. Bitte stimme der Nutzung der ausschließlich funktionalen Cookies zu.Ich stimme zu