j-lawyer.org

Thorsten

Erstellte Forenantworten

15 Beiträge anzeigen - 1 bis 15 (von insgesamt 18)

1 2 →

Autor

Beiträge
5. März 2026 um 19:09 als Antwort auf: Arbeiten auf 3 Rechnern an verschiedenen Orten ohne Netzwerk #7433

Thorsten
Participant

Ja, jetzt nach ziemlich genau 4 Jahren mit der oben beschriebenen Lösung hat die LAN-Schnittstelle an meinem mobilen Miniserver den Geist aufgegeben. Reparieren geht nicht, substituieren durch USB-Ethernet-Adapter ist zu wurstelig und alles per WLAN ist mir zu unsicher. Eigentlich habe ich auch keine Lust mehr auf das Rumtragen eines Miniservers – habe außerdem nur noch zwei getrennte Arbeitsorte.

Für’s Erste habe ich im HomeOffice eine Standalone-Installation realisiert. Dabei fiel auf, daß J-Lawyer zwischenzeitlich von MySQL zu MariaDB gewechselt ist. Das Rückspielen meiner Sicherung in die Neuinstallation führte zu Kompatibilitätsproblemen. Die Sicherungsdatei mußte händisch angepaßt werden. Dazu gibt es ein eigenes Thema hier im Forum, wo ich meinen Lösungsweg beschrieben habe. Danach funktioniert alles.

Mein Problem mit den zwei Arbeitsplätzen habe ich jetzt aber wieder neu. Die offiziell angebotene Cloud basierte Lösung ist natürlich nicht schlecht, aber im Verhältnis zu meinem Arbeitsaufkommen zu kostspielig.

Meine bisherigen Versuche, Dateien direkt auf einer externen SSD unterzubringen sind gescheitert. Ich habe den Eindruck, daß J-Lawyer den vom System vergebenen Alias für das USB-Laufwerk nicht mag und da nicht zugreifen kann. Mal sehen, wie es weiter gehen kann….

Grüße,
T.

1. März 2026 um 19:44 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7428

Thorsten
Participant

Boah – bin ich gut 😉

Ich habe mich auf die Seite von Susan B. durchgegoogelt, die genau dieses Problem „Migrate from MySQL to MariaDB (Ubuntu)“ befaßt https://codewithsusan.com/notes/migrate-mysql-to-mariadb?r=ypc. Dort wird Schritt für Schritt im Video erklärt, wie der alte Datenbank-Dump modifiziert werden muß, damit er für die neue MariaDB kompatibel ist. Also, hier wird konkret erklärt, was zu tun ist.

Bei mir hat gereicht, daß ich im alten Backup-Dump alle Vorkommnisse von „utf8mb4_0900_ai_ci“ durch „utf8mb4_unicode_ci“ ersetzt habe. Danach habe ich die modifizierte Datei manuell gemäß J-Lawyer-Anleitung „Kapitel Administration/Daten aus Sicherung wiederherstellen (manuell)“ in den MariaDB-Server eingespielt – ohne eine einzige Fehlermeldung! (Vorher gab es unzählige Meldungen).

Nach Neustart des J-Law-Servers ging zunächst nichts. Ein Neustart des ganzen Rechners führte dann aber zu dem gewünschten Ergebnis. Ich habe wieder Zugang zu meinen Daten und soweit bis jetzt erkennbar, gibt es keine Fehler in der Darstellung oder sonstwelche Unregelmäßigkeiten.

Ich kann mir vorstellen, daß potentiell eine ganze Reihe von Nutzern aus älteren Zeiten von diesem Problem betroffen sind. Ein Hinweis in der Anleitung wäre hilfreich. Ich hatte an diesem Wochenende eine schöne Lernkurve.

28. Februar 2026 um 16:28 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7426
Thorsten
Participant
Zwischenergebnis: Server und Client neu installiert.
Damit der Backupmanager läuft habe ich das Serverdatenverzeichnis auf mich als Benutzer umgewidmet. Mein Backup wurde korrekt eingespielt. Danach den Client gestartet. Login mit meinen Anmeldedaten möglich, Client hat mich erkannt.

Beim Start kommen aber folgende Fehlermeldungen:
```
1. Sie benutzen einen Client in Version 3.4.0.4 mit einem Server in Version unknown. Dies kann im schlimmsten Fall zu Datenverlust führen. Trotzdem fortfahren? Ja/Nein

2. org.hibernate.exception.SQLGrammarException: could not extract ResuitSet. OK

3. Lade Eingabehilfe... 5 von 9
```
Danach friert der Start ein und es geht nicht weiter. Testweise habe ich dann das Server-Datenverzeichnis wieder auf den Benutzer „j-lawyer-server“ zurückgewidmet. Das Ergebnis beim Start bleibt aber exakt dasselbe. Start läuft nicht durch.
28. Februar 2026 um 14:58 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7425
Thorsten
Participant
Ja, habe mal den Dump geöffnet, dort steht als Version:
```
-- MySQL dump 10.13  Distrib 8.0.45, for Linux (x86_64)
--
-- Host: localhost    Database: jlawyerdb
-- ------------------------------------------------------
-- Server version	8.0.45-0ubuntu0.24.04.1
```
Meine Anwendungsverwaltung meint zu meiner installierten MariaDB:

Version: 1:10.11.14-OubuntuO.24.04.1

Für diesen Unterschied zwischen MySQL 8.0 und MariaDB 10.11 wird bei den Leuten von MariaDB ein ganzer Sack voll Inkompatibilitäten aufgezählt:
```
Incompatibilities

When moving from MySQL 8.0 to MariaDB 10.11, please take note of the following incompatibilities:

    For a list of function differences, see Function Differences Between MariaDB 10.11 and MySQL 8.0.

    For a list of system variable differences, see System Variable Differences Between MariaDB 10.11 and MySQL 8.0.

    For replication, see Replication Compatibility Between MariaDB and MySQL.

    MariaDB does not support MySQL's SET PERSIST - MDEV-16228

    MariaDB's GTID is not compatible with MySQL's. Note that MariaDB and MySQL also have different GTID system variables, so these need to be adjusted when migrating.

    The unix_socket authentication plugin is now default on Unix-like systems, which is a major change to authentication in MariaDB. See Authentication from MariaDB 10.4 for an overview of the changes.

    All mysql* binaries are now named mariadb* (the previous mysql named is retained as a symlink for compatibility purposes)

    Not all character sets and collations are supported across both MySQL and MariaDB. As of 10.11, MariaDB supports 40 character sets and 506 collations . As of 8.0.32, MySQL supports 41 character sets (gb18030 being the additional one - MDEV-7495) and 286 collations.

    MariaDB indicates collation pad status as part of the name (e.g. utf8mb3_unicode_nopad_ci), while MySQL indicates pad status by means of an extra column in SHOW COLLATION.

    To make CREATE TABLE ... SELECT work the same way in statement based and row based replication it's by default executed as CREATE OR REPLACE TABLE on the slave. One benefit of this is that if the slave dies in the middle of CREATE ... SELECT it will be able to continue.

        One can use the slave-ddl-exec-mode variable to specify how CREATE TABLE and DROP TABLE is replicated.

    Users created with MySQL's SHA256 password algorithm cannot be used in MariaDB 10.11 - MDEV-9804.

    MariaDB 10.11 does not support Lateral Derived Tables - MDEV-19078.

    MariaDB 10.11 does not support CIDR notation for user accounts - MDEV-25515.

    MariaDB stores JSON as true text, not in binary format as MySQL. MariaDB's JSON functions are much faster than MySQL's so there is no need to store in binary format, which would add complexity when manipulating JSON objects.

    For the same reason, MariaDB's JSON data type is an alias for LONGTEXT. If you want to replicate JSON columns from MySQL to MariaDB, you should store JSON objects in MySQL in a TEXT or LONGTEXT column or use statement-based replication. If you are using JSON columns and want to upgrade to MariaDB, use the mysql_json plugin to automatically convert MySQL JSON to TEXT, or alternatively you need to either convert them to TEXT or use mysqldump to copy these tables to MariaDB.

    In MySQL, JSON is compared according to json values. In MariaDB JSON strings are normal strings and compared as strings.

    MariaDB 10.11 does not support MySQL's JSON operators (-> and ->>) - MDEV-13594

    MariaDB 10.11 supports the standard by producing null and a warning for JSON_SEARCH when given invalid data, while MySQL produces an error.

    Roles

        MariaDB never allows authentication via roles, while MySQL permits this.

        MySQL permits activating multiple roles at the same time. MariaDB can achieve the same result by creating an intermediate aggregate role.

        In the INFORMATION_SCHEMA.ENABLED_ROLES table, MySQL reports just the direct list of enabled roles, while MariaDB reports the enabled role, plus the effective inherited roles.

        MySQL extends the INFORMATION_SCHEMA.APPLICABLE_ROLES table .

        MySQL includes the tables INFORMATION_SCHEMA.ROLE_TABLE_GRANTS, INFORMATION_SCHEMA.ROLE_ROUTINE_GRANTS, INFORMATION_SCHEMA.ROLE_COLUMN_GRANTS, and INFORMATION_SCHEMA ADMINISTRABLE_ROLE_AUTHORIZATIONS.

    MySQL has the performance schema enabled by default. For performance reasons MariaDB 10.11 has it disabled by default. You can enable it by starting mysqld with the option --performance-schema.

    In MariaDB 10.11, using FLUSH TABLES without any table list will only close tables not in use, and tables not locked by the FLUSH TABLES connection. If there are no locked tables, FLUSH TABLES will be instant and will not cause any waits, as it no longer waits for tables in use. When a table list is provided, the server will wait for the end of any transactions that are using the tables. In MySQL, FLUSH TABLES only waits for the statements to complete.

    MariaDB binaries (mysqld, myisamchk etc.) give a warning if one uses a unique prefix of an option (such as --big-table instead of --big-tables). MySQL binaries require the full option name.

    MariaDB 10.11 implements InnoDB encryption in a different way to MySQL 8.0.

    MySQL's implementation of aborting statements that exceed a certain time to execute can only kill SELECTs, while MariaDB's can kill any queries (excluding stored procedures).

    MariaDB 10.11 does not support MySQL's SELECT /*+ MAX_EXECUTION_TIME(n) */ ... - see Aborting Statements that Exceed a Certain Time to Execute.

    MySQL 8.0 does not support the Query Cache.

    MariaDB 10.11 does not support the MySQL Memcached plugin (which has been deprecated in MySQL 8.0). However, data stored using memcached can be retrieved because the data is stored as InnoDB tables. MariaDB is able to start successfully with an error message of not being able to find libmemcached.so library.

    In MySQL, X'HHHH', the standard SQL syntax for binary string literals, erroneously works in the same way as 0xHHHH, which could work as a number or string depending on the context. In MariaDB, this has been fixed to behave as a string in all contexts (and never as a number). See CAST and Hexadecimal Literals for more details and examples.

    In MariaDB 10.11, SHOW CREATE TABLE does not quote the DEFAULT value of an integer. MariaDB 10.2 and earlier, and MySQL, do. Since MariaDB can support defaults for BLOB and TEXT fields, while MySQL does not, SHOW CREATE TABLE will also append DEFAULT NULL where no default is explicitly provided to nullable BLOB or TEXT fields in MariaDB.

    As a result of implementing Table Value Constructors, the VALUES function has been renamed to VALUE().

    MariaDB's NOWAIT supports SELECT statements, LOCK TABLES and various DDL statements, while MySQL's NOWAIT only supports SELECT.

    MariaDB's NOWAIT cannot be added on views and stored procedures while MySQL's can - MDEV-25247

    MariaDB does not support RENAME table while it is write-locked - MDEV-30814

    MariaDB returns an ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction when unable to lock within the time, while MySQL returns ERROR 3572 (HY000): Statement aborted because lock(s) could not be acquired immediately and NOWAIT is set

    MariaDB does not support the optional init_vector argument for AES_ENCRYPT and AES_DECRYPT or the block_encryption_mode variable - MDEV-9069

    MariaDB does not support the --initialize option. Use mariadb-install-db instead. - MDEV-19010

    MariaDB 10.11 does not support the ngram and MeCab full-text parser plugins - MDEV-10267, MDEV-10268.

    MariaDB 10.11 does not support the MySQL X plugin.

    MariaDB 10.11 before MariaDB 10.11.5 does not support MySQL 8's “native” InnoDB partitioning handler - MDEV-29253

    MariaDB 10.11 does not support CREATE TABLESPACE for InnoDB.

    The MySQL 8.0 and MariaDB 10.11 INFORMATION_SCHEMA.COLUMNS table contain slightly different fields.

    MariaDB 10.11 client executables allow the connection protocol to be forced by specifying only connection properties on the command-line. See mariadb Command-line client

    The MySQL binary log includes the thread_id, while MariaDB's binary log does not - MDEV-7850

    The MariaDB syntax supporting Spatial Reference System IDs for spatial data type columns with REF_SYSTEM_ID is not supported by MySQL. MySQL 8 introduced CREATE SPATIAL REFERENCE SYSTEM, which is not supported by MariaDB - MDEV-29953

    MariaDB 10.11 does not support the RESTART statement - MDEV-30813

    Compressing the binary log in MariaDB uses a different compression algorithm, and different system variables to manage.

    MariaDB 10.11 does not support the SELECT FOR UPDATE and FOR SHARE locks - MDEV-17514

For protocol differences, see MariaDB protocol difference with MySQL.
```
Da kenne ich mich natürlich überhaupt nicht mit aus.

Mein Plan ist jetzt folgender:

1. Ich setze den J-Lawyer bei mir noch einmal komplett neu und sauber auf.
2. Spiele dann mein Backup zurück
3. Wenn es dann nicht klappt, installiere ich nochmal die alte MySQL-DB-Engine
4. Spiele das Backup zurück
5. Wenn es dann klappt, würde ich mich über Vorschläge freuen, wie ich meine Daten von MySQL auf MariaDB migrieren kann (sind Gott sei Dank nicht so viele).
6. Wenn es nicht klappt, liegt das Problem wohl woanders…

Eigentlich kann ich ja nicht der einzige Betroffene sein. Mal schauen…
27. Februar 2026 um 17:33 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7422

Thorsten
Participant

Also, das Backup ist gerade einmal 3 Tage alt und ich hatte meine Programm-Installation immer kurzfristig geupdated. Das klingt jetzt so, alsob bei einem Update des Servers die Datenbank nicht mit geupdated wird, also noch die initiale MySQL Datenbank von der Erstinstallation bestand. Allerdings habe ich das Serverbetriebssystem Ubuntu-Server 24.irgendwas auch regelmäßig zeitnah aktualisiert. Da werden ja auch die MySQL-Sache auf einen aktuellen Stand gebracht. Und bis Montag dieser Woche hat ja alles auch noch gut funktioniert.

Ja, und bei der Neuinstallation auf dem lokalen Rechner habe ich natürlich eine aktuelle MariaDB angelegt. Aber irgendwie wäre es schon gut, wenn man mit den Daten arbeiten könnte.

Mhmm…

27. Februar 2026 um 17:18 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7419
Thorsten
Participant
Ja, stimmt, wenn alle Programmdaten in einer DB liegen, dann kann sich das Programm nur mit Mühe selbst updaten, wenn es sich nicht selbst neu starten will.

Wenn nur der Server auf das Datenverzeichnis zugreift, macht er das dann als Benutzer „j-lawyer-server“ oder unter dem normal angemeldeten Benutzer? Oder anders: Sollen die Daten im Datenverzeichnis stets dem Nutzer „j-lawyer-server“ gehören und welche Zugriffsrechte sollen die haben? Dann kann man das ja schon mal zu Fuß richtigstellen.

Hier ist mal das Log vom Client und der vergeblichen Anmeldung:
```
clr@Tante-Frida:/media/clr/SSD-1GB/Daten/09-CONF/j-lawyer-client$ ./j-lawyer-Client
Migrating settings from /home/clr/.j-lawyer-client to /home/clr/j-lawyer-settings
new dir exists: true
old dir exists: true
test dir exists: true
16:47:58,671 INFO  [Main] Java: 17.0.17
16:48:11,640 INFO  [LoginDialog] login: initiated
16:48:11,641 INFO  [LoginDialog] login: saving last settings
16:48:11,641 INFO  [LoginDialog] login: initiating lookups
16:48:11,642 INFO  [LoginDialog] login: logging in...
16:48:11,663 INFO  [naming] WildFly Naming version 1.0.15.Final
16:48:11,702 INFO  [security] ELY00001: WildFly Elytron version 1.19.1.Final
16:48:11,728 INFO  [xnio] XNIO version 3.8.7.Final
16:48:11,733 INFO  [nio] XNIO NIO Implementation Version 3.8.7.Final
16:48:11,752 INFO  [threads] JBoss Threads version 2.4.0.Final
16:48:11,778 INFO  [remoting] JBoss Remoting version 5.0.25.Final
16:48:11,799 INFO  [client] JBoss EJB Client version 4.0.44.Final
16:48:12,127 ERROR [LoginDialog] Error connecting to server
org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:620) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:57) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:148) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:130) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:87) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.call(AuthenticationContextEJBClientInterceptor.java:59) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.handleInvocationResult(AuthenticationContextEJBClientInterceptor.java:52) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:212) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:1003) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:182) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:116) ~[jboss-client.jar:26.1.3.Final]
	at jdk.proxy2.$Proxy20.login(Unknown Source) ~[?:?]
	at com.jdimension.jlawyer.client.LoginDialog.loginPerformed(LoginDialog.java:2276) ~[j-lawyer-client.jar:?]
	at com.jdimension.jlawyer.client.LoginDialog.pwPasswordKeyPressed(LoginDialog.java:2578) ~[j-lawyer-client.jar:?]
	at com.jdimension.jlawyer.client.LoginDialog$7.keyPressed(LoginDialog.java:1333) ~[j-lawyer-client.jar:?]
	at java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258) ~[?:?]
	at java.awt.Component.processKeyEvent(Component.java:6584) ~[?:?]
	at javax.swing.JComponent.processKeyEvent(JComponent.java:2896) ~[?:?]
	at java.awt.Component.processEvent(Component.java:6403) ~[?:?]
	at java.awt.Container.processEvent(Container.java:2266) ~[?:?]
	at java.awt.Component.dispatchEventImpl(Component.java:5001) ~[?:?]
	at java.awt.Container.dispatchEventImpl(Container.java:2324) ~[?:?]
	at java.awt.Component.dispatchEvent(Component.java:4833) ~[?:?]
	at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1952) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:883) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1150) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1020) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:848) ~[?:?]
	at java.awt.Component.dispatchEventImpl(Component.java:4882) ~[?:?]
	at java.awt.Container.dispatchEventImpl(Container.java:2324) ~[?:?]
	at java.awt.Window.dispatchEventImpl(Window.java:2780) ~[?:?]
	at java.awt.Component.dispatchEvent(Component.java:4833) ~[?:?]
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:775) ~[?:?]
	at java.awt.EventQueue$4.run(EventQueue.java:720) ~[?:?]
	at java.awt.EventQueue$4.run(EventQueue.java:714) ~[?:?]
	at java.security.AccessController.doPrivileged(AccessController.java:399) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97) ~[?:?]
	at java.awt.EventQueue$5.run(EventQueue.java:747) ~[?:?]
	at java.awt.EventQueue$5.run(EventQueue.java:745) ~[?:?]
	at java.security.AccessController.doPrivileged(AccessController.java:399) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) ~[?:?]
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:744) ~[?:?]
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) ~[?:?]
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) ~[?:?]
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) ~[?:?]
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) ~[?:?]
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) ~[?:?]
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) ~[?:?]
	Suppressed: javax.ejb.NoSuchEJBException: No such EJB: j-lawyer-server/j-lawyer-server-ejb/SecurityService @ http-remoting://localhost:8080
		at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1193) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.ejb.protocol.remote.EJBClientChannel$MethodInvocation.handleResponse(EJBClientChannel.java:1107) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.util.InvocationTracker.signalResponse(InvocationTracker.java:167) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.ejb.protocol.remote.EJBClientChannel.processMessage(EJBClientChannel.java:199) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.ejb.protocol.remote.EJBClientChannel.access$100(EJBClientChannel.java:123) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.ejb.protocol.remote.EJBClientChannel$1$1.handleMessage(EJBClientChannel.java:758) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:432) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282) ~[jboss-client.jar:26.1.3.Final]
		at java.lang.Thread.run(Thread.java:840) ~[?:?]
16:48:24,326 INFO  [LoginDialog] login: initiated
16:48:24,327 INFO  [LoginDialog] login: saving last settings
16:48:24,327 INFO  [LoginDialog] login: initiating lookups
16:48:24,328 INFO  [LoginDialog] login: logging in...
16:48:24,340 ERROR [LoginDialog] Error connecting to server
org.jboss.ejb.client.RequestSendFailedException: EJBCLIENT000409: No more destinations are available
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:620) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.protocol.remote.RemotingEJBClientInterceptor.handleInvocationResult(RemotingEJBClientInterceptor.java:57) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.TransactionPostDiscoveryInterceptor.handleInvocationResult(TransactionPostDiscoveryInterceptor.java:148) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.DiscoveryEJBClientInterceptor.handleInvocationResult(DiscoveryEJBClientInterceptor.java:130) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.NamingEJBClientInterceptor.handleInvocationResult(NamingEJBClientInterceptor.java:87) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.call(AuthenticationContextEJBClientInterceptor.java:59) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.AuthenticationContextEJBClientInterceptor.handleInvocationResult(AuthenticationContextEJBClientInterceptor.java:52) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.TransactionInterceptor.handleInvocationResult(TransactionInterceptor.java:212) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:622) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:551) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:1003) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:182) ~[jboss-client.jar:26.1.3.Final]
	at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:116) ~[jboss-client.jar:26.1.3.Final]
	at jdk.proxy2.$Proxy20.login(Unknown Source) ~[?:?]
	at com.jdimension.jlawyer.client.LoginDialog.loginPerformed(LoginDialog.java:2276) ~[j-lawyer-client.jar:?]
	at com.jdimension.jlawyer.client.LoginDialog.pwPasswordKeyPressed(LoginDialog.java:2578) ~[j-lawyer-client.jar:?]
	at com.jdimension.jlawyer.client.LoginDialog$7.keyPressed(LoginDialog.java:1333) ~[j-lawyer-client.jar:?]
	at java.awt.AWTEventMulticaster.keyPressed(AWTEventMulticaster.java:258) ~[?:?]
	at java.awt.Component.processKeyEvent(Component.java:6584) ~[?:?]
	at javax.swing.JComponent.processKeyEvent(JComponent.java:2896) ~[?:?]
	at java.awt.Component.processEvent(Component.java:6403) ~[?:?]
	at java.awt.Container.processEvent(Container.java:2266) ~[?:?]
	at java.awt.Component.dispatchEventImpl(Component.java:5001) ~[?:?]
	at java.awt.Container.dispatchEventImpl(Container.java:2324) ~[?:?]
	at java.awt.Component.dispatchEvent(Component.java:4833) ~[?:?]
	at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1952) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:883) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1150) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:1020) ~[?:?]
	at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:848) ~[?:?]
	at java.awt.Component.dispatchEventImpl(Component.java:4882) ~[?:?]
	at java.awt.Container.dispatchEventImpl(Container.java:2324) ~[?:?]
	at java.awt.Window.dispatchEventImpl(Window.java:2780) ~[?:?]
	at java.awt.Component.dispatchEvent(Component.java:4833) ~[?:?]
	at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:775) ~[?:?]
	at java.awt.EventQueue$4.run(EventQueue.java:720) ~[?:?]
	at java.awt.EventQueue$4.run(EventQueue.java:714) ~[?:?]
	at java.security.AccessController.doPrivileged(AccessController.java:399) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:97) ~[?:?]
	at java.awt.EventQueue$5.run(EventQueue.java:747) ~[?:?]
	at java.awt.EventQueue$5.run(EventQueue.java:745) ~[?:?]
	at java.security.AccessController.doPrivileged(AccessController.java:399) ~[?:?]
	at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86) ~[?:?]
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:744) ~[?:?]
	at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) ~[?:?]
	at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) ~[?:?]
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) ~[?:?]
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) ~[?:?]
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) ~[?:?]
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:90) ~[?:?]
	Suppressed: org.jboss.ejb.client.RequestSendFailedException: Error in connecting to Destination @http-remoting://localhost:8080 : Please check if the client and server are configured to use the same protocol and ports. 
		at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleFailed(RemoteEJBReceiver.java:112) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleFailed(RemoteEJBReceiver.java:78) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:215) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.IoUtils$2.execute(IoUtils.java:71) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:693) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.AbstractIoFuture$NotifierState.doNotify(AbstractIoFuture.java:267) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.AbstractIoFuture$NotifierState.notifyFailed(AbstractIoFuture.java:253) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.AbstractIoFuture.setException(AbstractIoFuture.java:595) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.FutureResult.setException(FutureResult.java:85) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.EndpointImpl$3.lambda$handleDone$0(EndpointImpl.java:532) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) ~[jboss-client.jar:26.1.3.Final]
		at org.xnio.XnioWorker$WorkerThreadFactory$1$1.run(XnioWorker.java:1282) ~[jboss-client.jar:26.1.3.Final]
		at java.lang.Thread.run(Thread.java:840) ~[?:?]
	Caused by: org.wildfly.security.auth.AuthenticationException: JBREM000308: Authentication failed (no mechanisms left), tried: 
   PLAIN: org.wildfly.security.auth.AuthenticationException: JBREM000304: Server rejected authentication
		at org.jboss.remoting3.ConnectionPeerIdentityContext.doAuthenticate(ConnectionPeerIdentityContext.java:379) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.ConnectionPeerIdentityContext.authenticate(ConnectionPeerIdentityContext.java:183) ~[jboss-client.jar:26.1.3.Final]
		at org.jboss.remoting3.EndpointImpl$3.lambda$handleDone$0(EndpointImpl.java:529) ~[jboss-client.jar:26.1.3.Final]
```
———————————————————————————————

Und hier ist das Log vom Server:

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

JBoss Bootstrap Environment

JBOSS_HOME: /opt/j-lawyer-server/wildfly

JAVA: /opt/j-lawyer-server/jre/bin/java

JAVA_OPTS: -server -Xms256m -Xmx2048m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true –add-exports=java.desktop/sun.awt=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.url.ldap=ALL-UNNAMED –add-exports=java.naming/com.sun.jndi.url.ldaps=ALL-UNNAMED –add-opens=java.base/java.lang=ALL-UNNAMED –add-opens=java.base/java.lang.invoke=ALL-UNNAMED –add-opens=java.base/java.lang.reflect=ALL-UNNAMED –add-opens=java.base/java.io=ALL-UNNAMED –add-opens=java.base/java.security=ALL-UNNAMED –add-opens=java.base/java.util=ALL-UNNAMED –add-opens=java.base/java.util.concurrent=ALL-UNNAMED –add-opens=java.management/javax.management=ALL-UNNAMED –add-opens=java.naming/javax.naming=ALL-UNNAMED -Djava.security.manager=allow

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

[0m14:27:10,927 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.2.Final
[0m[0m14:27:11,371 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.13.Final
[0m[0m14:27:11,378 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
[0m[0m14:27:11,468 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) starting
[0m[0m14:27:12,495 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads – 1) WFLYDS0015: Re-attempting failed deployment j-lawyer-server.ear
[0m[0m14:27:13,725 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
[0m[0m14:27:13,741 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.8.7.Final
[0m[0m14:27:13,745 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.8.7.Final
[0m[0m14:27:13,767 INFO [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool — 53) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
[0m[0m14:27:13,766 INFO [org.wildfly.extension.health] (ServerService Thread Pool — 54) WFLYHEALTH0001: Activating Base Health Subsystem
[0m[0m14:27:13,768 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 55) WFLYCLINF0001: Activating Infinispan subsystem.
[0m[0m14:27:13,774 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 57) WFLYRS0016: RESTEasy version 4.7.7.Final
[0m[0m14:27:13,779 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 56) WFLYIO001: Worker ‚default‘ has auto-configured to 8 IO threads with 64 max task threads based on your 4 available processors
[0m[0m14:27:13,790 INFO [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool — 66) WFLYCONF0001: Activating MicroProfile Config Subsystem
[0m[0m14:27:13,796 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.5.3.Final)
[0m[0m14:27:13,796 INFO [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool — 67) WFLYJWT0001: Activating MicroProfile JWT Subsystem
[0m[33m14:27:13,796 WARN [org.jboss.as.txn] (ServerService Thread Pool — 76) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
[0m[0m14:27:13,799 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
[0m[0m14:27:13,802 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 68) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
[0m[0m14:27:13,809 INFO [org.jboss.as.naming] (ServerService Thread Pool — 69) WFLYNAM0001: Activating Naming Subsystem
[0m[0m14:27:13,803 INFO [org.wildfly.extension.metrics] (ServerService Thread Pool — 65) WFLYMETRICS0001: Activating Base Metrics Subsystem
[0m[0m14:27:13,810 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 62) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
[0m[0m14:27:13,820 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 78) WFLYWS0002: Activating WebServices Extension
[0m[0m14:27:13,822 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
[0m[0m14:27:13,825 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.25.Final
[0m[0m14:27:13,836 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0004: Deploying JDBC-compliant driver class org.mariadb.jdbc.Driver (version 3.4)
[0m[0m14:27:13,854 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = mariadb
[0m[33m14:27:13,873 WARN [org.wildfly.extension.elytron] (MSC service thread 1-1) WFLYELY00023: KeyStore file ‚/opt/j-lawyer-server/wildfly/standalone/configuration/application.keystore‘ does not exist. Used blank.
[0m[0m14:27:13,883 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 2.2.19.Final starting
[0m[0m14:27:13,894 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
[0m[0m14:27:13,908 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
[0m[33m14:27:13,915 WARN [org.wildfly.extension.elytron] (MSC service thread 1-8) WFLYELY01084: KeyStore /opt/j-lawyer-server/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
[0m[0m14:27:13,988 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
[0m[0m14:27:13,991 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
[0m[0m14:27:14,024 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 77) WFLYUT0014: Creating file handler for path ‚/opt/j-lawyer-server/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
[0m[0m14:27:14,026 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
[0m[0m14:27:14,029 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) Queuing requests.
[0m[0m14:27:14,030 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: Host default-host starting
[0m[0m14:27:14,081 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
[0m[0m14:27:14,141 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
[0m[0m14:27:14,212 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
[0m[0m14:27:14,216 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
[0m[0m14:27:14,216 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:/jlawyerdb]
[0m[0m14:27:14,367 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn’t located on this platform, it will fall back to using pure Java NIO. Your platform is Linux, install LibAIO to enable the AIO journal and achieve optimal performance.
[0m[0m14:27:14,371 INFO [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
[0m[0m14:27:14,372 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/j-lawyer-server/wildfly/standalone/deployments
[0m[0m14:27:14,381 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
[0m[0m14:27:14,442 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/journal,bindingsDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/opt/j-lawyer-server/wildfly/standalone/data/activemq/paging)
[0m[0m14:27:14,452 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.5.0.Final (Apache CXF 3.4.10)
[0m[0m14:27:14,481 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221013: Using NIO Journal
[0m[0m14:27:14,589 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
[0m[0m14:27:14,590 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
[0m[0m14:27:14,590 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
[0m[0m14:27:14,590 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
[0m[0m14:27:14,642 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221034: Waiting indefinitely to obtain live lock
[0m[0m14:27:14,643 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221035: Live Server Obtained live lock
[0m[0m14:27:14,995 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
[0m[0m14:27:15,006 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
[0m[0m14:27:15,006 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.searchIndexProcessorQueue on address jms.queue.searchIndexProcessorQueue
[0m[0m14:27:15,006 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.outgoingMailProcessorQueue on address jms.queue.outgoingMailProcessorQueue
[0m[0m14:27:15,118 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
[0m[0m14:27:15,124 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
[0m[0m14:27:15,125 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
[0m[0m14:27:15,125 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
[0m[0m14:27:15,284 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221007: Server is now live
[0m[0m14:27:15,285 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [default, nodeID=dab191e0-8e1d-11ee-8f82-b0a4607a48b5]
[0m[0m14:27:15,299 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 82) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
[0m[33m14:27:15,315 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 86) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „Tante-Frida“. If this new address is incorrect please manually configure the connector to use the proper one.
[0m[0m14:27:15,316 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 86) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
[0m[0m14:27:15,366 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0007: Registered connection factory java:/JmsXA
[0m[0m14:27:15,411 INFO [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-7) AMQ151007: Resource adaptor started
[0m[0m14:27:15,411 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatoractivemq-ra
[0m[0m14:27:15,412 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
[0m[0m14:27:15,412 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
[0m[33m14:27:23,311 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,311 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,311 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,311 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/json-simple-2.3.0.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/log4j-over-slf4j-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/slf4j-api-1.7.30.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/log4j-api-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jboss-jaxrs-api_2.1_spec-2.0.2.Final.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/log4j-core-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,317 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/log4j-slf4j-impl-2.17.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/asm-all-repackaged-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/cglib-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/guava-14.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/hk2-api-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/hk2-locator-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/hk2-utils-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/javax.annotation-api-1.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/javax.inject-2.2.0-b21.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/javax.servlet-api-3.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jaxb-api-2.2.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,318 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-entity-filtering-2.5.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-media-moxy-2.5.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.osgi.core-4.2.0.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/osgi-resource-locator-1.0.1.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-client.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-common.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-container-servlet.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-container-servlet-core.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/jersey-server.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.core-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.asm-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.antlr-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,319 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.jpa-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.jpa.jpql-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,320 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/org.eclipse.persistence.moxy-2.7.7.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,335 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,335 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,335 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,335 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,335 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,336 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/j-lawyer-server.ear/lib/jaxb-core-2.3.0.1.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,344 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,344 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
[0m[0m14:27:23,363 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
[0m[0m14:27:23,363 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
[0m[0m14:27:23,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
[0m[0m14:27:23,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
[0m[0m14:27:23,364 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
[0m[33m14:27:23,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jollyday-0.4.7.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,367 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/tika-app-1.5.jar in /content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
[0m[33m14:27:23,520 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/searchIndexProcessorQueue‘ for Jakarta Enterprise Beans ‚SearchIndexProcessor‘ will be ignored.
[0m[33m14:27:23,522 WARN [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/outgoingMailProcessorQueue‘ for Jakarta Enterprise Beans ‚OutgoingMailProcessor‘ will be ignored.
[0m[0m14:27:23,567 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
[0m[0m14:27:23,597 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
[0m[0m14:27:23,936 INFO [org.jipijapa] (MSC service thread 1-5) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
[0m[0m14:27:23,936 INFO [org.jipijapa] (MSC service thread 1-6) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
[0m[0m14:27:24,004 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
[0m[0m14:27:24,189 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 6.0.23.Final
[0m[0m14:27:24,291 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 81) ISPN000128: Infinispan version: Infinispan ‚Triskaidekaphobia‘ 13.0.10.Final
[0m[0m14:27:24,379 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
[0m[0m14:27:24,386 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
[0m[0m14:27:24,412 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
[0m[0m14:27:24,426 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-6) WFLYEJB0473: JNDI bindings for session bean named ‚PersistenceLifecycleBean‘ in deployment unit ’subdeployment „j-lawyer-server-entities.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:app/j-lawyer-server-entities/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:module/PersistenceLifecycleBean!org.jlawyer.persistence.PersistenceLifecycleBeanLocal
java:global/j-lawyer-server/j-lawyer-server-entities/PersistenceLifecycleBean
java:app/j-lawyer-server-entities/PersistenceLifecycleBean
java:module/PersistenceLifecycleBean

[0m[0m14:27:24,453 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 81) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller‘
[0m[0m14:27:24,485 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-6) WFLYTRAC0001: Tracer initialized: NoopTracer
[0m[0m14:27:24,561 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
[0m[0m14:27:24,567 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚TemplatesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:app/j-lawyer-io/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:module/TemplatesEndpointV6!org.jlawyer.io.rest.v6.TemplatesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/TemplatesEndpointV6
java:app/j-lawyer-io/TemplatesEndpointV6
java:module/TemplatesEndpointV6

[0m[0m14:27:24,567 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚DataBucketEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:app/j-lawyer-io/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:module/DataBucketEndpointV6!org.jlawyer.io.rest.v6.DataBucketEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/DataBucketEndpointV6
java:app/j-lawyer-io/DataBucketEndpointV6
java:module/DataBucketEndpointV6

[0m[0m14:27:24,567 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚WebHooksEndpointV7‘ 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/WebHooksEndpointV7!org.jlawyer.io.rest.v7.WebHooksEndpointLocalV7
java:app/j-lawyer-io/WebHooksEndpointV7!org.jlawyer.io.rest.v7.WebHooksEndpointLocalV7
java:module/WebHooksEndpointV7!org.jlawyer.io.rest.v7.WebHooksEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/WebHooksEndpointV7
java:app/j-lawyer-io/WebHooksEndpointV7
java:module/WebHooksEndpointV7

[0m[0m14:27:24,567 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:app/j-lawyer-io/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:module/SecurityEndpointV1!org.jlawyer.io.rest.v1.SecurityEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV1
java:app/j-lawyer-io/SecurityEndpointV1
java:module/SecurityEndpointV1

[0m[0m14:27:24,567 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:app/j-lawyer-io/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:module/CasesEndpointV6!org.jlawyer.io.rest.v6.CasesEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV6
java:app/j-lawyer-io/CasesEndpointV6
java:module/CasesEndpointV6

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:app/j-lawyer-io/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:module/CasesEndpointV7!org.jlawyer.io.rest.v7.CasesEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV7
java:app/j-lawyer-io/CasesEndpointV7
java:module/CasesEndpointV7

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚SecurityEndpointV6‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:app/j-lawyer-io/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:module/SecurityEndpointV6!org.jlawyer.io.rest.v6.SecurityEndpointLocalV6
java:global/j-lawyer-server/j-lawyer-io/SecurityEndpointV6
java:app/j-lawyer-io/SecurityEndpointV6
java:module/SecurityEndpointV6

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:app/j-lawyer-io/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:module/CasesEndpointV2!org.jlawyer.io.rest.v2.CasesEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV2
java:app/j-lawyer-io/CasesEndpointV2
java:module/CasesEndpointV2

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV3‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:app/j-lawyer-io/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:module/CasesEndpointV3!org.jlawyer.io.rest.v3.CasesEndpointLocalV3
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV3
java:app/j-lawyer-io/CasesEndpointV3
java:module/CasesEndpointV3

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚MessagingEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:app/j-lawyer-io/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:module/MessagingEndpointV7!org.jlawyer.io.rest.v7.MessagingEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/MessagingEndpointV7
java:app/j-lawyer-io/MessagingEndpointV7
java:module/MessagingEndpointV7

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:app/j-lawyer-io/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:module/CasesEndpointV4!org.jlawyer.io.rest.v4.CasesEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV4
java:app/j-lawyer-io/CasesEndpointV4
java:module/CasesEndpointV4

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:app/j-lawyer-io/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:module/CasesEndpointV5!org.jlawyer.io.rest.v5.CasesEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV5
java:app/j-lawyer-io/CasesEndpointV5
java:module/CasesEndpointV5

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚AdministrationEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:app/j-lawyer-io/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:module/AdministrationEndpointV7!org.jlawyer.io.rest.v7.AdministrationEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/AdministrationEndpointV7
java:app/j-lawyer-io/AdministrationEndpointV7
java:module/AdministrationEndpointV7

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CasesEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:app/j-lawyer-io/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:module/CasesEndpointV1!org.jlawyer.io.rest.v1.CasesEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/CasesEndpointV1
java:app/j-lawyer-io/CasesEndpointV1
java:module/CasesEndpointV1

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV5‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:app/j-lawyer-io/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:module/ContactsEndpointV5!org.jlawyer.io.rest.v5.ContactsEndpointLocalV5
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV5
java:app/j-lawyer-io/ContactsEndpointV5
java:module/ContactsEndpointV5

[0m[0m14:27:24,568 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarEndpointV4‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:app/j-lawyer-io/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:module/CalendarEndpointV4!org.jlawyer.io.rest.v4.CalendarEndpointLocalV4
java:global/j-lawyer-server/j-lawyer-io/CalendarEndpointV4
java:app/j-lawyer-io/CalendarEndpointV4
java:module/CalendarEndpointV4

[0m[0m14:27:24,569 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV2‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:app/j-lawyer-io/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:module/ContactsEndpointV2!org.jlawyer.io.rest.v2.ContactsEndpointLocalV2
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV2
java:app/j-lawyer-io/ContactsEndpointV2
java:module/ContactsEndpointV2

[0m[0m14:27:24,569 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚ContactsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:app/j-lawyer-io/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:module/ContactsEndpointV1!org.jlawyer.io.rest.v1.ContactsEndpointLocalV1
java:global/j-lawyer-server/j-lawyer-io/ContactsEndpointV1
java:app/j-lawyer-io/ContactsEndpointV1
java:module/ContactsEndpointV1

[0m[0m14:27:24,569 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚ConfigurationEndpointV7‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:app/j-lawyer-io/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:module/ConfigurationEndpointV7!org.jlawyer.io.rest.v7.ConfigurationEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/ConfigurationEndpointV7
java:app/j-lawyer-io/ConfigurationEndpointV7
java:module/ConfigurationEndpointV7

[0m[0m14:27:24,569 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicesEndpointV7‘ 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/InvoicesEndpointV7!org.jlawyer.io.rest.v7.InvoicesEndpointLocalV7
java:app/j-lawyer-io/InvoicesEndpointV7!org.jlawyer.io.rest.v7.InvoicesEndpointLocalV7
java:module/InvoicesEndpointV7!org.jlawyer.io.rest.v7.InvoicesEndpointLocalV7
java:global/j-lawyer-server/j-lawyer-io/InvoicesEndpointV7
java:app/j-lawyer-io/InvoicesEndpointV7
java:module/InvoicesEndpointV7

[0m[0m14:27:24,569 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named ‚FormsEndpointV1‘ in deployment unit ’subdeployment „j-lawyer-io.war“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:app/j-lawyer-io/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:module/FormsEndpointV1!org.jlawyer.io.rest.v1.FormsEndpointV1Local
java:global/j-lawyer-server/j-lawyer-io/FormsEndpointV1
java:app/j-lawyer-io/FormsEndpointV1
java:module/FormsEndpointV1

[0m[0m14:27:24,678 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 83) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller‘
[0m[0m14:27:24,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
[0m[0m14:27:24,782 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:module/DocumentFolderFacade!com.jdimension.jlawyer.persistence.DocumentFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderFacade
java:app/j-lawyer-server-ejb/DocumentFolderFacade
java:module/DocumentFolderFacade

[0m[0m14:27:24,782 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚BankStatementsCSVConfigFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/BankStatementsCSVConfigFacade!com.jdimension.jlawyer.persistence.BankStatementsCSVConfigFacadeLocal
java:app/j-lawyer-server-ejb/BankStatementsCSVConfigFacade!com.jdimension.jlawyer.persistence.BankStatementsCSVConfigFacadeLocal
java:module/BankStatementsCSVConfigFacade!com.jdimension.jlawyer.persistence.BankStatementsCSVConfigFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/BankStatementsCSVConfigFacade
java:app/j-lawyer-server-ejb/BankStatementsCSVConfigFacade
java:module/BankStatementsCSVConfigFacade

[0m[0m14:27:24,782 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚BankDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:module/BankDataBeanFacade!com.jdimension.jlawyer.persistence.BankDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/BankDataBeanFacade
java:app/j-lawyer-server-ejb/BankDataBeanFacade
java:module/BankDataBeanFacade

[0m[0m14:27:24,782 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:module/ArchiveFileFormsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormsBeanFacade
java:module/ArchiveFileFormsBeanFacade

[0m[0m14:27:24,782 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚PaymentFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/PaymentFacade!com.jdimension.jlawyer.persistence.PaymentFacadeLocal
java:app/j-lawyer-server-ejb/PaymentFacade!com.jdimension.jlawyer.persistence.PaymentFacadeLocal
java:module/PaymentFacade!com.jdimension.jlawyer.persistence.PaymentFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/PaymentFacade
java:app/j-lawyer-server-ejb/PaymentFacade
java:module/PaymentFacade

[0m[0m14:27:24,791 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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
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

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ContactSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:app/j-lawyer-server-ejb/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:module/ContactSyncService!com.jdimension.jlawyer.services.ContactSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ContactSyncService
java:app/j-lawyer-server-ejb/ContactSyncService
java:module/ContactSyncService

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚MappingEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:app/j-lawyer-server-ejb/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:module/MappingEntryFacade!com.jdimension.jlawyer.persistence.MappingEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingEntryFacade
java:app/j-lawyer-server-ejb/MappingEntryFacade
java:module/MappingEntryFacade

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeArtefactBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:module/FormTypeArtefactBeanFacade!com.jdimension.jlawyer.persistence.FormTypeArtefactBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:app/j-lawyer-server-ejb/FormTypeArtefactBeanFacade
java:module/FormTypeArtefactBeanFacade

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:app/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:module/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/CalendarService!com.jdimension.jlawyer.services.CalendarServiceRemote

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ClaimLedgerEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerEntryFacade!com.jdimension.jlawyer.persistence.ClaimLedgerEntryFacadeLocal
java:app/j-lawyer-server-ejb/ClaimLedgerEntryFacade!com.jdimension.jlawyer.persistence.ClaimLedgerEntryFacadeLocal
java:module/ClaimLedgerEntryFacade!com.jdimension.jlawyer.persistence.ClaimLedgerEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerEntryFacade
java:app/j-lawyer-server-ejb/ClaimLedgerEntryFacade
java:module/ClaimLedgerEntryFacade

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileHistoryBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:module/ArchiveFileHistoryBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileHistoryBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileHistoryBeanFacade
java:module/ArchiveFileHistoryBeanFacade

[0m[0m14:27:24,792 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ScheduledTasksService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:app/j-lawyer-server-ejb/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:module/ScheduledTasksService!com.jdimension.jlawyer.services.ScheduledTasksServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ScheduledTasksService
java:app/j-lawyer-server-ejb/ScheduledTasksService
java:module/ScheduledTasksService

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ClaimComponentFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimComponentFacade!com.jdimension.jlawyer.persistence.ClaimComponentFacadeLocal
java:app/j-lawyer-server-ejb/ClaimComponentFacade!com.jdimension.jlawyer.persistence.ClaimComponentFacadeLocal
java:module/ClaimComponentFacade!com.jdimension.jlawyer.persistence.ClaimComponentFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimComponentFacade
java:app/j-lawyer-server-ejb/ClaimComponentFacade
java:module/ClaimComponentFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚SearchService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:app/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:module/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/SearchService!com.jdimension.jlawyer.services.SearchServiceRemote

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentTagRuleConditionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagRuleConditionFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleConditionFacadeLocal
java:app/j-lawyer-server-ejb/DocumentTagRuleConditionFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleConditionFacadeLocal
java:module/DocumentTagRuleConditionFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleConditionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagRuleConditionFacade
java:app/j-lawyer-server-ejb/DocumentTagRuleConditionFacade
java:module/DocumentTagRuleConditionFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentTagRuleFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagRuleFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleFacadeLocal
java:app/j-lawyer-server-ejb/DocumentTagRuleFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleFacadeLocal
java:module/DocumentTagRuleFacade!com.jdimension.jlawyer.persistence.DocumentTagRuleFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagRuleFacade
java:app/j-lawyer-server-ejb/DocumentTagRuleFacade
java:module/DocumentTagRuleFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CityDataBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:app/j-lawyer-server-ejb/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:module/CityDataBeanFacade!com.jdimension.jlawyer.persistence.CityDataBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CityDataBeanFacade
java:app/j-lawyer-server-ejb/CityDataBeanFacade
java:module/CityDataBeanFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileAddressesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:module/ArchiveFileAddressesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileAddressesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileAddressesBeanFacade
java:module/ArchiveFileAddressesBeanFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:app/j-lawyer-server-ejb/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:module/MailboxAccessFacade!com.jdimension.jlawyer.persistence.MailboxAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxAccessFacade
java:app/j-lawyer-server-ejb/MailboxAccessFacade
java:module/MailboxAccessFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetPositionTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:module/TimesheetPositionTemplateFacade!com.jdimension.jlawyer.persistence.TimesheetPositionTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionTemplateFacade
java:app/j-lawyer-server-ejb/TimesheetPositionTemplateFacade
java:module/TimesheetPositionTemplateFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InterestRuleFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InterestRuleFacade!com.jdimension.jlawyer.persistence.InterestRuleFacadeLocal
java:app/j-lawyer-server-ejb/InterestRuleFacade!com.jdimension.jlawyer.persistence.InterestRuleFacadeLocal
java:module/InterestRuleFacade!com.jdimension.jlawyer.persistence.InterestRuleFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InterestRuleFacade
java:app/j-lawyer-server-ejb/InterestRuleFacade
java:module/InterestRuleFacade

[0m[0m14:27:24,793 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚MailboxSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:app/j-lawyer-server-ejb/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:module/MailboxSetupFacade!com.jdimension.jlawyer.persistence.MailboxSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MailboxSetupFacade
java:app/j-lawyer-server-ejb/MailboxSetupFacade
java:module/MailboxSetupFacade

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AddressTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:module/AddressTagsBeanFacade!com.jdimension.jlawyer.persistence.AddressTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressTagsBeanFacade
java:app/j-lawyer-server-ejb/AddressTagsBeanFacade
java:module/AddressTagsBeanFacade

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePositionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:module/InvoicePositionFacade!com.jdimension.jlawyer.persistence.InvoicePositionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionFacade
java:app/j-lawyer-server-ejb/InvoicePositionFacade
java:module/InvoicePositionFacade

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:app/j-lawyer-server-ejb/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:module/CalendarAccessFacade!com.jdimension.jlawyer.persistence.CalendarAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarAccessFacade
java:app/j-lawyer-server-ejb/CalendarAccessFacade
java:module/CalendarAccessFacade

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚GroupMembershipFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:app/j-lawyer-server-ejb/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:module/GroupMembershipFacade!com.jdimension.jlawyer.persistence.GroupMembershipFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupMembershipFacade
java:app/j-lawyer-server-ejb/GroupMembershipFacade
java:module/GroupMembershipFacade

[0m[0m14:27:24,794 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AddressBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:app/j-lawyer-server-ejb/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:module/AddressBeanFacade!com.jdimension.jlawyer.persistence.AddressBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AddressBeanFacade
java:app/j-lawyer-server-ejb/AddressBeanFacade
java:module/AddressBeanFacade

[0m[0m14:27:24,797 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetPositionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:module/TimesheetPositionFacade!com.jdimension.jlawyer.persistence.TimesheetPositionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetPositionFacade
java:app/j-lawyer-server-ejb/TimesheetPositionFacade
java:module/TimesheetPositionFacade

[0m[0m14:27:24,797 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:app/j-lawyer-server-ejb/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:module/CampaignFacade!com.jdimension.jlawyer.persistence.CampaignFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignFacade
java:app/j-lawyer-server-ejb/CampaignFacade
java:module/CampaignFacade

[0m[0m14:27:24,797 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:module/DocumentTagsBeanFacade!com.jdimension.jlawyer.persistence.DocumentTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:app/j-lawyer-server-ejb/DocumentTagsBeanFacade
java:module/DocumentTagsBeanFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:app/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:module/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/IntegrationService!com.jdimension.jlawyer.services.IntegrationServiceRemote

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚FaxQueueBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:module/FaxQueueBeanFacade!com.jdimension.jlawyer.persistence.FaxQueueBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FaxQueueBeanFacade
java:app/j-lawyer-server-ejb/FaxQueueBeanFacade
java:module/FaxQueueBeanFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileReviewsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:module/ArchiveFileReviewsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileReviewsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileReviewsBeanFacade
java:module/ArchiveFileReviewsBeanFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:module/InvoicePoolFacade!com.jdimension.jlawyer.persistence.InvoicePoolFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolFacade
java:app/j-lawyer-server-ejb/InvoicePoolFacade
java:module/InvoicePoolFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚GroupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:app/j-lawyer-server-ejb/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:module/GroupFacade!com.jdimension.jlawyer.persistence.GroupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/GroupFacade
java:app/j-lawyer-server-ejb/GroupFacade
java:module/GroupFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ReportService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:app/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:module/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ReportService!com.jdimension.jlawyer.services.ReportServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/ReportService
java:app/j-lawyer-server-ejb/ReportService
java:module/ReportService

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CaseSyncSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:module/CaseSyncSettingsFacade!com.jdimension.jlawyer.persistence.CaseSyncSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:app/j-lawyer-server-ejb/CaseSyncSettingsFacade
java:module/CaseSyncSettingsFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InstantMessageFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:app/j-lawyer-server-ejb/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:module/InstantMessageFacade!com.jdimension.jlawyer.persistence.InstantMessageFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageFacade
java:app/j-lawyer-server-ejb/InstantMessageFacade
java:module/InstantMessageFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceTypeFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:module/InvoiceTypeFacade!com.jdimension.jlawyer.persistence.InvoiceTypeFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceTypeFacade
java:app/j-lawyer-server-ejb/InvoiceTypeFacade
java:module/InvoiceTypeFacade

[0m[0m14:27:24,798 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CaseAccountEntryFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:app/j-lawyer-server-ejb/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:module/CaseAccountEntryFacade!com.jdimension.jlawyer.persistence.CaseAccountEntryFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseAccountEntryFacade
java:app/j-lawyer-server-ejb/CaseAccountEntryFacade
java:module/CaseAccountEntryFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileGroupsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:module/ArchiveFileGroupsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileGroupsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileGroupsBeanFacade
java:module/ArchiveFileGroupsBeanFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AssistantPromptFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantPromptFacade!com.jdimension.jlawyer.persistence.AssistantPromptFacadeLocal
java:app/j-lawyer-server-ejb/AssistantPromptFacade!com.jdimension.jlawyer.persistence.AssistantPromptFacadeLocal
java:module/AssistantPromptFacade!com.jdimension.jlawyer.persistence.AssistantPromptFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantPromptFacade
java:app/j-lawyer-server-ejb/AssistantPromptFacade
java:module/AssistantPromptFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileTagsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:module/ArchiveFileTagsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileTagsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileTagsBeanFacade
java:module/ArchiveFileTagsBeanFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationHookLogFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookLogFacade!com.jdimension.jlawyer.persistence.IntegrationHookLogFacadeLocal
java:app/j-lawyer-server-ejb/IntegrationHookLogFacade!com.jdimension.jlawyer.persistence.IntegrationHookLogFacadeLocal
java:module/IntegrationHookLogFacade!com.jdimension.jlawyer.persistence.IntegrationHookLogFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookLogFacade
java:app/j-lawyer-server-ejb/IntegrationHookLogFacade
java:module/IntegrationHookLogFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚EmailService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceLocal
java:app/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceLocal
java:module/EmailService!com.jdimension.jlawyer.services.EmailServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceRemote
java:app/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceRemote
java:module/EmailService!com.jdimension.jlawyer.services.EmailServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/EmailService!com.jdimension.jlawyer.services.EmailServiceRemote

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePositionTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:module/InvoicePositionTemplateFacade!com.jdimension.jlawyer.persistence.InvoicePositionTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePositionTemplateFacade
java:app/j-lawyer-server-ejb/InvoicePositionTemplateFacade
java:module/InvoicePositionTemplateFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderSettingsFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:module/CaseFolderSettingsFacade!com.jdimension.jlawyer.persistence.CaseFolderSettingsFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:app/j-lawyer-server-ejb/CaseFolderSettingsFacade
java:module/CaseFolderSettingsFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarEntryTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarEntryTemplateFacade!com.jdimension.jlawyer.persistence.CalendarEntryTemplateFacadeLocal
java:app/j-lawyer-server-ejb/CalendarEntryTemplateFacade!com.jdimension.jlawyer.persistence.CalendarEntryTemplateFacadeLocal
java:module/CalendarEntryTemplateFacade!com.jdimension.jlawyer.persistence.CalendarEntryTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarEntryTemplateFacade
java:app/j-lawyer-server-ejb/CalendarEntryTemplateFacade
java:module/CalendarEntryTemplateFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSetupFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:app/j-lawyer-server-ejb/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:module/CalendarSetupFacade!com.jdimension.jlawyer.persistence.CalendarSetupFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSetupFacade
java:app/j-lawyer-server-ejb/CalendarSetupFacade
java:module/CalendarSetupFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileFormEntriesBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:module/ArchiveFileFormEntriesBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileFormEntriesBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileFormEntriesBeanFacade
java:module/ArchiveFileFormEntriesBeanFacade

[0m[0m14:27:24,799 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoicePoolAccessFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:module/InvoicePoolAccessFacade!com.jdimension.jlawyer.persistence.InvoicePoolAccessFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:app/j-lawyer-server-ejb/InvoicePoolAccessFacade
java:module/InvoicePoolAccessFacade

[0m[0m14:27:24,800 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:module/TimesheetFacade!com.jdimension.jlawyer.persistence.TimesheetFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetFacade
java:app/j-lawyer-server-ejb/TimesheetFacade
java:module/TimesheetFacade

[0m[0m14:27:24,800 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CalendarSyncService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:app/j-lawyer-server-ejb/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:module/CalendarSyncService!com.jdimension.jlawyer.services.CalendarSyncServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CalendarSyncService
java:app/j-lawyer-server-ejb/CalendarSyncService
java:module/CalendarSyncService

[0m[0m14:27:24,800 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚BaseInterestFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/BaseInterestFacade!com.jdimension.jlawyer.persistence.BaseInterestFacadeLocal
java:app/j-lawyer-server-ejb/BaseInterestFacade!com.jdimension.jlawyer.persistence.BaseInterestFacadeLocal
java:module/BaseInterestFacade!com.jdimension.jlawyer.persistence.BaseInterestFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/BaseInterestFacade
java:app/j-lawyer-server-ejb/BaseInterestFacade
java:module/BaseInterestFacade

[0m[0m14:27:24,800 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CustomerRelationsService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

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

[0m[0m14:27:24,800 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TransactionLogFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TransactionLogFacade!com.jdimension.jlawyer.persistence.TransactionLogFacadeLocal
java:app/j-lawyer-server-ejb/TransactionLogFacade!com.jdimension.jlawyer.persistence.TransactionLogFacadeLocal
java:module/TransactionLogFacade!com.jdimension.jlawyer.persistence.TransactionLogFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TransactionLogFacade
java:app/j-lawyer-server-ejb/TransactionLogFacade
java:module/TransactionLogFacade

[0m[0m14:27:24,803 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚MappingTableFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:app/j-lawyer-server-ejb/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:module/MappingTableFacade!com.jdimension.jlawyer.persistence.MappingTableFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/MappingTableFacade
java:app/j-lawyer-server-ejb/MappingTableFacade
java:module/MappingTableFacade

[0m[0m14:27:24,803 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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
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

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AssistantConfigFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantConfigFacade!com.jdimension.jlawyer.persistence.AssistantConfigFacadeLocal
java:app/j-lawyer-server-ejb/AssistantConfigFacade!com.jdimension.jlawyer.persistence.AssistantConfigFacadeLocal
java:module/AssistantConfigFacade!com.jdimension.jlawyer.persistence.AssistantConfigFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantConfigFacade
java:app/j-lawyer-server-ejb/AssistantConfigFacade
java:module/AssistantConfigFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CampaignAddressesFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:app/j-lawyer-server-ejb/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:module/CampaignAddressesFacade!com.jdimension.jlawyer.persistence.CampaignAddressesFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CampaignAddressesFacade
java:app/j-lawyer-server-ejb/CampaignAddressesFacade
java:module/CampaignAddressesFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InstantMessageMentionFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:app/j-lawyer-server-ejb/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:module/InstantMessageMentionFacade!com.jdimension.jlawyer.persistence.InstantMessageMentionFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InstantMessageMentionFacade
java:app/j-lawyer-server-ejb/InstantMessageMentionFacade
java:module/InstantMessageMentionFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileDocumentsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:module/ArchiveFileDocumentsBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileDocumentsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileDocumentsBeanFacade
java:module/ArchiveFileDocumentsBeanFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AppOptionGroupBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:module/AppOptionGroupBeanFacade!com.jdimension.jlawyer.persistence.AppOptionGroupBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:app/j-lawyer-server-ejb/AppOptionGroupBeanFacade
java:module/AppOptionGroupBeanFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚PaymentService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceLocal
java:app/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceLocal
java:module/PaymentService!com.jdimension.jlawyer.services.PaymentServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceRemote
java:app/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceRemote
java:module/PaymentService!com.jdimension.jlawyer.services.PaymentServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/PaymentService!com.jdimension.jlawyer.services.PaymentServiceRemote

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentFolderTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:module/DocumentFolderTemplateFacade!com.jdimension.jlawyer.persistence.DocumentFolderTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:app/j-lawyer-server-ejb/DocumentFolderTemplateFacade
java:module/DocumentFolderTemplateFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ServerSettingsBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:module/ServerSettingsBeanFacade!com.jdimension.jlawyer.persistence.ServerSettingsBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:app/j-lawyer-server-ejb/ServerSettingsBeanFacade
java:module/ServerSettingsBeanFacade

[0m[0m14:27:24,804 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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
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

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocumentNameTemplateFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentNameTemplateFacade!com.jdimension.jlawyer.persistence.DocumentNameTemplateFacadeLocal
java:app/j-lawyer-server-ejb/DocumentNameTemplateFacade!com.jdimension.jlawyer.persistence.DocumentNameTemplateFacadeLocal
java:module/DocumentNameTemplateFacade!com.jdimension.jlawyer.persistence.DocumentNameTemplateFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/DocumentNameTemplateFacade
java:app/j-lawyer-server-ejb/DocumentNameTemplateFacade
java:module/DocumentNameTemplateFacade

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:app/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:module/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/InvoiceService!com.jdimension.jlawyer.services.InvoiceServiceRemote

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚VoipService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚EpostQueueBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:app/j-lawyer-server-ejb/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:module/EpostQueueBeanFacade!com.jdimension.jlawyer.persistence.EpostQueueBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/EpostQueueBeanFacade
java:app/j-lawyer-server-ejb/EpostQueueBeanFacade
java:module/EpostQueueBeanFacade

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:app/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:module/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/TimesheetService!com.jdimension.jlawyer.services.TimesheetServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetService
java:app/j-lawyer-server-ejb/TimesheetService
java:module/TimesheetService

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚PartyTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:module/PartyTypeBeanFacade!com.jdimension.jlawyer.persistence.PartyTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/PartyTypeBeanFacade
java:app/j-lawyer-server-ejb/PartyTypeBeanFacade
java:module/PartyTypeBeanFacade

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚InvoiceFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:app/j-lawyer-server-ejb/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:module/InvoiceFacade!com.jdimension.jlawyer.persistence.InvoiceFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/InvoiceFacade
java:app/j-lawyer-server-ejb/InvoiceFacade
java:module/InvoiceFacade

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚MessagingService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚FormTypeBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:app/j-lawyer-server-ejb/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:module/FormTypeBeanFacade!com.jdimension.jlawyer.persistence.FormTypeBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/FormTypeBeanFacade
java:app/j-lawyer-server-ejb/FormTypeBeanFacade
java:module/FormTypeBeanFacade

[0m[0m14:27:24,805 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AppUserBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:module/AppUserBeanFacade!com.jdimension.jlawyer.persistence.AppUserBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppUserBeanFacade
java:app/j-lawyer-server-ejb/AppUserBeanFacade
java:module/AppUserBeanFacade

[0m[0m14:27:24,806 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CaseFolderFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:app/j-lawyer-server-ejb/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:module/CaseFolderFacade!com.jdimension.jlawyer.persistence.CaseFolderFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CaseFolderFacade
java:app/j-lawyer-server-ejb/CaseFolderFacade
java:module/CaseFolderFacade

[0m[0m14:27:24,806 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AssistantReplacementFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantReplacementFacade!com.jdimension.jlawyer.persistence.AssistantReplacementFacadeLocal
java:app/j-lawyer-server-ejb/AssistantReplacementFacade!com.jdimension.jlawyer.persistence.AssistantReplacementFacadeLocal
java:module/AssistantReplacementFacade!com.jdimension.jlawyer.persistence.AssistantReplacementFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AssistantReplacementFacade
java:app/j-lawyer-server-ejb/AssistantReplacementFacade
java:module/AssistantReplacementFacade

[0m[0m14:27:24,806 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ClaimLedgerFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerFacade!com.jdimension.jlawyer.persistence.ClaimLedgerFacadeLocal
java:app/j-lawyer-server-ejb/ClaimLedgerFacade!com.jdimension.jlawyer.persistence.ClaimLedgerFacadeLocal
java:module/ClaimLedgerFacade!com.jdimension.jlawyer.persistence.ClaimLedgerFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerFacade
java:app/j-lawyer-server-ejb/ClaimLedgerFacade
java:module/ClaimLedgerFacade

[0m[0m14:27:24,806 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚TimesheetAllowedPositionTplFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetAllowedPositionTplFacade!com.jdimension.jlawyer.persistence.TimesheetAllowedPositionTplFacadeLocal
java:app/j-lawyer-server-ejb/TimesheetAllowedPositionTplFacade!com.jdimension.jlawyer.persistence.TimesheetAllowedPositionTplFacadeLocal
java:module/TimesheetAllowedPositionTplFacade!com.jdimension.jlawyer.persistence.TimesheetAllowedPositionTplFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/TimesheetAllowedPositionTplFacade
java:app/j-lawyer-server-ejb/TimesheetAllowedPositionTplFacade
java:module/TimesheetAllowedPositionTplFacade

[0m[0m14:27:24,811 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ArchiveFileBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:module/ArchiveFileBeanFacade!com.jdimension.jlawyer.persistence.ArchiveFileBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:app/j-lawyer-server-ejb/ArchiveFileBeanFacade
java:module/ArchiveFileBeanFacade

[0m[0m14:27:24,823 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) 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

[0m[0m14:27:24,823 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚ClaimLedgerService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceLocal
java:app/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceLocal
java:module/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceRemote
java:app/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceRemote
java:module/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/ClaimLedgerService!com.jdimension.jlawyer.services.ClaimLedgerServiceRemote

[0m[0m14:27:24,824 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚CustomHooksService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:app/j-lawyer-server-ejb/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:module/CustomHooksService!com.jdimension.jlawyer.events.CustomHooksServiceLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/CustomHooksService
java:app/j-lawyer-server-ejb/CustomHooksService
java:module/CustomHooksService

[0m[0m14:27:24,824 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚IntegrationHookFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:app/j-lawyer-server-ejb/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:module/IntegrationHookFacade!com.jdimension.jlawyer.persistence.IntegrationHookFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/IntegrationHookFacade
java:app/j-lawyer-server-ejb/IntegrationHookFacade
java:module/IntegrationHookFacade

[0m[0m14:27:24,824 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚DocUtilityService‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceRemote
java:app/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceRemote
java:module/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceRemote
java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceRemote
ejb:j-lawyer-server/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceRemote
java:global/j-lawyer-server/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceLocal
java:app/j-lawyer-server-ejb/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceLocal
java:module/DocUtilityService!com.jdimension.jlawyer.services.DocUtilityServiceLocal

[0m[0m14:27:24,824 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named ‚AppRoleBeanFacade‘ in deployment unit ’subdeployment „j-lawyer-server-ejb.jar“ of deployment „j-lawyer-server.ear“‚ are as follows:

java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:app/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:module/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade
java:app/j-lawyer-server-ejb/AppRoleBeanFacade
java:module/AppRoleBeanFacade

[0m[0m14:27:24,863 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) WFLYTRAC0001: Tracer initialized: NoopTracer
[0m[0m14:27:24,998 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-3) No shutdown hook registered: Please call close() manually on application shutdown.
[0m[0m14:27:24,999 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-3) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@42abf4eb, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=Tante-Frida, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
[0m[0m14:27:25,008 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-4) No shutdown hook registered: Please call close() manually on application shutdown.
[0m[0m14:27:25,008 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-2) No shutdown hook registered: Please call close() manually on application shutdown.
[0m[0m14:27:25,008 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-2) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-server-war.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@79115ed5, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=Tante-Frida, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
[0m[0m14:27:25,008 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-4) WFLYTRAC0001: Tracer initialized: JaegerTracer(version=Java-1.6.0, serviceName=j-lawyer-server.ear!j-lawyer-server-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@3ff5684f, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=Tante-Frida, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
[0m[0m14:27:25,079 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 3.1.9 (Final)
[0m[0m14:27:25,288 INFO [org.jipijapa] (MSC service thread 1-7) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
[0m[0m14:27:25,308 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 83) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
[0m[0m14:27:25,308 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 81) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
[0m[0m14:27:25,311 INFO [org.infinispan.CONFIG] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m14:27:25,312 INFO [org.infinispan.CONFIG] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
[0m[0m14:27:25,337 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 84) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
[0m[0m14:27:25,345 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 81) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
[0m[0m14:27:25,345 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 83) HHH000204: Processing PersistenceUnitInfo [
name: j-lawyer-server-ejbPU
…]
[0m[0m14:27:25,351 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 84) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
[0m[0m14:27:25,478 INFO [org.hibernate.Version] (ServerService Thread Pool — 81) HHH000412: Hibernate Core {5.3.28.Final}
[0m[0m14:27:25,481 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 81) HHH000206: hibernate.properties not found
[0m[0m14:27:25,713 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 83) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
[0m[0m14:27:26,016 INFO [org.jipijapa] (MSC service thread 1-2) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
[0m[0m14:27:26,204 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 84) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
[0m[0m14:27:26,371 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
[0m[0m14:27:26,374 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean ‚OutgoingMailProcessor‘ with ‚activemq-ra.rar‘ resource adapter
[0m[0m14:27:26,394 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 84) HHH000400: Using dialect: org.hibernate.dialect.MariaDB103Dialect
[0m[0m14:27:26,430 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 84) Envers integration enabled? : true
[0m[0m14:27:26,535 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 81) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
[0m[0m14:27:26,536 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 81) HHH000400: Using dialect: org.hibernate.dialect.MariaDB103Dialect
[0m[0m14:27:26,539 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool — 81) Envers integration enabled? : true
[0m[0m14:27:26,991 INFO [stdout] (ServerService Thread Pool — 81) Starting j-lawyer.org database migrations…
[0m[0m14:27:27,208 INFO [org.flywaydb.core.FlywayExecutor] (ServerService Thread Pool — 81) Database: jdbc:mariadb://localhost/jlawyerdb?user=root&password=********&serverTimezone=Europe/Berlin&useSSL=false&allowPublicKeyRetrieval=true (MariaDB 10.11)
[0m[31m14:27:27,343 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 81) exception caught: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
Detected failed migration to version 1.13.0.18 (VersionBump).
Please remove any half-completed changes then run repair to fix the schema history.
Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE
at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.lambda$migrate$3(Flyway.java:200)
at deployment.j-lawyer-server.ear//org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:234)
at deployment.j-lawyer-server.ear//org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:118)
at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:187)
at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:733)
at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)

[0m[0m14:27:27,344 INFO [stdout] (ServerService Thread Pool — 84) Starting j-lawyer.org database migrations…
[0m[0m14:27:27,362 INFO [org.flywaydb.core.FlywayExecutor] (ServerService Thread Pool — 84) Database: jdbc:mariadb://localhost/jlawyerdb?user=root&password=********&serverTimezone=Europe/Berlin&useSSL=false&allowPublicKeyRetrieval=true (MariaDB 10.11)
[0m[31m14:27:27,441 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 84) exception caught: org.flywaydb.core.api.exception.FlywayValidateException: Validate failed: Migrations have failed validation
Detected failed migration to version 1.13.0.18 (VersionBump).
Please remove any half-completed changes then run repair to fix the schema history.
Need more flexibility with validation rules? Learn more: https://rd.gt/3AbJUZE
at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.lambda$migrate$3(Flyway.java:200)
at deployment.j-lawyer-server.ear//org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:234)
at deployment.j-lawyer-server.ear//org.flywaydb.core.FlywayExecutor.execute(FlywayExecutor.java:118)
at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:187)
at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:733)
at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)

[0m[0m14:27:28,218 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 81) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@11502efb
[0m[31m14:27:28,224 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 81) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1327)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1253)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
… 10 more
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
… 12 more

[0m[0m14:27:28,225 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 84) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@49192cbd
[0m[31m14:27:28,226 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 84) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:840)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1327)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1253)
at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
… 10 more
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
at org.hibernate@5.3.28.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
at org.hibernate@5.3.28.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1250)
… 12 more

[0m[31m14:27:28,250 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\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“,
„jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [assistant_config]“
}}
[0m[0m14:27:28,319 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
[0m[0m14:27:28,335 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
WFLYCTL0448: 519 additional services are down due to their dependencies being missing or failed
[0m[0m14:27:28,376 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
[0m[31m14:27:28,382 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 17796ms – Started 3890 of 4617 services (540 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
[0m[0m14:27:28,386 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
[0m[0m14:27:28,386 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
[0m

———————————————————————————————-

Ja, das ist jetzt viel und ein paar Warnings sind drin – habe aber selber keinen Plan davon.

Liebe Grüße,
T.
27. Februar 2026 um 16:21 als Antwort auf: Kein Login – Dateirechte nach Wiederherstellung #7416

Thorsten
Participant

Ja, nochmal zur Ergänzung:

Auf Github heißt es: Doku lesen – selber machen!

Dafür fehlt mir aber etwas Hintergrundwissen:

– Unter welchem Nutzer läuft denn der J-Law-Server? Unter dem eigens dafür eingerichteten Nutzer „j-lawyer-server“, unter dem aktuell angemeldeten Benutzer oder unter einem Nutzer, mit dem man sich beim Login bei J-Lawyer anmeldet?

– Mit welchem Nutzer greift denn dann das laufende Programm auf das Datenverezeichnis des Servers zu, etwa dem aktuell angemeldeten normalen Betriebssystem-Benutzer?

– Werden bei einem Restore irgendwelche Nutzerberechtigungen aus der alten Installation (von einem alten anderen Rechner) zurückgespielt, wo man jetzt überhaupt nicht mehr weiß, wie die Nutzer-ID war?

– Warum sollen die Daten im Datenverzeichnis dem Benuter „j-lawyer-server“ gehören, wenn doch dann ein anderer Nutzer darauf zugreift?

Wenn der normale Benutzer am Rechner auf die Daten zugreifen soll, warum kann dann der Backup-Manager die Daten nicht standardmäßig unter diesem Benutzer das Restore in das Datenverzeichnis schreiben und warum gibt es kein Login-Zugriff?

Ich denke, eine funktionierende Restore-Funktion ist für ALLE Nutzer entscheidend. Deshalb habe ich das mit dem Doku lesen – selber machen nicht ganz verstanden.

Liebe Grüße,
T.

5. Mai 2025 um 18:38 als Antwort auf: E-Rechnung – Fehlende Identifikation des Ausstellers #6998

Thorsten
Participant

So, Folgendes habe ich jetzt gemacht:

1. Unter den Administator-Einstellungen, bei Nutzer, nicht nur den „Anzeigenamen“ ausgefüllt, sondern auch Name und Vorname (hatte ich wohl vergessen und nur bei Kanzleiprofil eingetragen).

2. An gleicher Stelle habe ich meine Steuernummer gelöscht und stattdessen bei UStID meine WirtschaftsID eingetragen.

3. Unter Kanzleieinstellungen habe ich auch die Steuernummer gelöscht und die WiID bei UStID eingetragen.

Bei einem xml-Vergleich der Rechnungen vorher und nachher zeigt sich, daß dort im Feld Tax-Registration statt „FC“ mit Steuernummer nun „VA“ mit meiner WiID steht. Tja, und die Fehlermeldung kommt dann auch nicht mehr.
Dank meiner professionellen Vorgehensweise, gleich 3 Parameter auf einmal zu verändern, weiß man natürlich jetzt nicht, woran das wirklich gelegen haben könnte. Am Namenseintrag bei Nutzer wohl nicht unbedingt, weil die Namen kamen bei den Fehlerrechnungen ja auch schon richtig rüber. Collmex ordnet Belege u.a. anhand der UStID zu. Kann sein, daß die verschärften Wert auf eine solche ID legen – die ich ja nicht habe. Aber eine Wirtschaftsidentifikationsnummer bekommt ja jetzt jeder zugewiesen.

Jedenfalls ist diese Fehlermeldung zur Zeit ausgeräumt. Vielleicht wäre es dann sinnvoll, darauf zu achten, wann ein richtiges Feld für eine Wirtschaftsidentifikationsnummer in den E-Rechnungs-Kanon aufgenommen wird. Das könnte man dan implementieren, damit auch alles wieder seine Richtigkeit hat.

Vielen Dank für die schnelle Antwort.
LG, Thorsten

5. Mai 2025 um 17:42 als Antwort auf: E-Rechnung – Fehlende Identifikation des Ausstellers #6996

Thorsten
Participant

Hallo,
die Fehlermeldung kommt bei der XML-Anzeige der mit J-Lawyer erstellten Pdf-Rechnung – also wohl ZugFERD. Die normale PDF Anzeige erfolgt ohne Mecker. Bei Rechnungen von anderen Lieferanten habe ich so eine Fehlermeldung noch nicht bekommen. Viele verschicken aber auch noch keine E-Rechnungen.

3. Mai 2023 um 16:42 als Antwort auf: Multi-Fenster-Modus #5445

Thorsten
Participant

Nachtrag:

Wenn ich mit mehreren Instanzen arbeite – also beispielsweise für das Scanmodul eine eigene zweite Instanz aufmache, findet keine direkte Aktualisierung zwischen den Instanzen statt. Wenn ich also in der zweiten Instanz mit dem Scanmodul eine Datei in einer Akte speicher und ich im ersten Modul diese Akte offen habe, wird mir das neu gespeicherte Dokument nicht angezeigt. Dazu muß ich erst wieder raus und wieder rein in die Akte (muß neu eingelesen werden). Dann ist aber auch die zweite Instanz überflüssig.

Es spricht also einiges dafür, einen echten Multi-Window-Betrieb einzurichten und das nicht durch mehrere Instanzen zu simulieren.

Habe gestern mal mit der Arztsoftware „T2med“ rumprobiert. Da werden offene Fenster/Module mit Hilfe von einer Art Fensterbuttons am oberen Bildschirmrand „gemerkt“ und können durch Klick wieder angewählt werden – ohne daß man wieder neu in die Akte einsteigen muß. Die Software ist so ziemlich das gleiche wie J-Lawyer, nur eben für Ärzte und mit Fokus auf die zentrale Patientenakte als Journal mit zugehörigen Ereignissen. Eine moderne Kanzleisoftware könnte auch stärker auf ein Akten-Ereignisjournal als zentraler Fokus in der Akte abstellen. Spricht ja nichts dagegen, alte Strukturen mal ein bißchen zu lüften.

Viele Grüße,
Thorsten

24. Juni 2022 um 15:47 als Antwort auf: E-Mail aus Akte versenden ohne Anhang / Dokument erstellen #4997

Thorsten
Participant

Hallo Jens,

ah, ok, also erst die Mail zur Akte speichern und dann per Doppelklick antworten – dann klappt es auch mit den Anhängen. Gut, das zwingt einen zu einem geordneten Arbeitsablauf.

In meinem Beispiel bin ich leider wieder auf eine „failed to parse“ E-Mail von einem Mandanten gestoßen. Da kann ich dann leider nicht drauf antworten. Aber das ist eine andere Baustelle.

Viele Grüße,
Thorsten

24. Juni 2022 um 15:30 als Antwort auf: E-Mail aus Akte versenden ohne Anhang / Dokument erstellen #4995

Thorsten
Participant

Hallo,

ja, danke für den schnellen Hinweis. Die Logik ist in Ordnung, daß man an der Adresse des Beteiligten ansetzt.

Bei einer Antwort aus dem Posteingang könnte man ja händisch eine Zuordnung zur Akte auswählen. Ich gebe allerdings zu, daß ich auch kein Freund von „Bandwurm E-Mails“ bin und man besser immer eine neue Nachricht schreiben sollte.

Aber so komme ich erstmal zurecht – Danke!

Viele Grüße,
Thorsten

8. Februar 2022 um 20:54 als Antwort auf: Arbeiten auf 3 Rechnern an verschiedenen Orten ohne Netzwerk #4805

Thorsten
Participant

So, update und Nachbetrachtung:

Mittlerweile habe ich die Probleme mit der Internetverbindung des Servers über den Arbeits-PC gelöst. Im Prinzip ist da garnicht viel zu machen, nur einstellen, daß die Netzwerkschnittstelle „gemeinsam mit anderen Rechnern“ betrieben werden soll. Außerdem müssen beide Rechner – PC und Server – zusätzlich zu DHCP noch eine weitere statische Adresse zugewiesen bekommen, unter der sie immer fest zu erreichen sind. Das war mir vorher nicht klar, dachte immer DHCP oder statisch – geht aber beides.

Den Server kann ich also immer in meine Aktentasche stecken und vor Ort an den unterschiedlichen Arbeitsplätzen mit dem jeweiligen Arbeitsrechner verbinden. Auf den Arbeitsplätzen ist jeweils der J-Lawyer Client installiert. Das Einloggen auf dem Server funktioniert am einfachsten ohne ssh und Tunnel. Das ist auch kein Problem, weil die Verbindung ja direkt vor meiner Nase und nur auf meinem Schreibtisch ist. Die Clients erkennen unproblematisch jeweils den Server. Man könnte sich aber auch eine sichere Verbindung einrichten, muß dann nur die ssh-Schlüsseldatei auf allen drei Arbeitsplätzen abgleichen.

Das Datensicherungsbackup des Servers inklusive html Kopien kopiere ich mir bei Feierabend mit rsync auf den lokalen Rechner und von dort noch einmal auf einen Stick. Damit habe ich ausreichend Kopien. Schön wäre natürlich, wenn das Programm selbst (und zusätzlich) das Backup + html-Kopien auf eine externe Datenquelle kopieren könnte.

Probleme habe ich noch mit dem integrierten E-Mail-Client der Software. Aber das Problem ist bereits gemeldet und in Arbeit (hoffe ich). Solange nutze ich noch einen externen E-Mail-Client – was durchaus umständlich ist. Mit der mobilen Nutzung auf 3 Arbeitsplätzen hat das aber nichts zu tun.

Noch ein Randproblem ist, daß ich auf dem selbstverwalteten Server stets die aktuellsten Aktualisierungen und Sicherheitsupdates einspielen kann (per ssh von meinem Arbeits-PC aus). Allerdings ist mir dabei unlägst die Netzwerkkonfiguration überschrieben worden. Also entweder „never change a running system“ oder „immer aktuell“. Beides hat seine Vorzüge. Die Konfiguration konnte ich dann auch bald wieder herstellen.

Momentan läuft bei mir persönlich auch der Workflow mit der kanzlei-Software noch nicht ganz routinemäßig, aber ich bin guter Dinge.

Ich werde weiter berichten…

6. Januar 2022 um 23:05 als Antwort auf: Diverse Fehlermeldungen in der Clientsoftware #4707

Thorsten
Participant

Ah, ok, sehe gerade, daß es dazu schon ein Ticket gibt.
Vielleicht ist das bei mir ja auch so ein Problem, weil Anmeldename nicht die Mail-Adresse ist.
Wenn es mal daran liegt…

Das Problem mit dem nicht Laden von Mails ist damit aber noch nicht aufgefangen.

6. Januar 2022 um 22:59 als Antwort auf: Diverse Fehlermeldungen in der Clientsoftware #4706

Thorsten
Participant

Ja, dazu habe ich auch mal eine Frage bzw. immer noch ein Problem.

Bei mir „traut“ mein Provider offensichtlich auch nicht dem Server. Provider ist Alfahosting. Also die Testmails vom Server funktionieren nicht. Die Mails vom Client funktionieren nur teilweise.

Ich bin jetzt doch etwas skeptisch, daß das immer so einfach an der Netzwerkkonfiguration des Servers liegen soll. Bei anderen Providern wird die Testmail ja akzeptiert. Mit einem Thunderbird gibt es auch keine Probleme.

Warum ist dann der Mailkontakt mit dem Server immer so ein Problem – nicht nur bei mir, sondern auch bei anderen und nicht nur bei Alfahosting, sondern auch bei Strato und Co.?

Der E-Mail-Client des J-Law-Clients ist auch hakelig. Aktuell habe ich hier eine Mail von einem Kollegen, die der Client von meinem eigentlichen Provider nicht runterladen will. Umgeleitet auf einen alternativen Provider kann die Mail zwar dann geladen werden, ist aber unschön formatiert und fängt ersteinmal mit einem großen Block kryptischem html an, bevor der Rest normal dargestellt wird – und ich habe die html Ansicht eingeschaltet.

Der Provider zuckt nur mit den Achseln und meint es läge am Client – und hier heißt es, der Provider mag den Server nicht. Beides hilft mir nicht weiter. E-Mail mit den richtigen Konten ist extrem zentral für die Kommunikation.

Hat denn der Martin eine Lösung für sein Problem gefunden?

Grüße.
Autor

Beiträge

15 Beiträge anzeigen - 1 bis 15 (von insgesamt 18)

1 2 →

Kanzleisoftware | Kostenlos | Open Source

Kanzleisoftware | Kostenlos | Open Source

Thorsten

Erstellte Forenantworten