Anmelde- oder Vebindungsparameter falsch

Hallo Gemeinde,
Ich würde j-lawyer gerne auf Windows 11 24 H 2 x64 installieren und ausprobieren.
Die Installation funktioniert scheinbar problemlos, aber der j-lawyer client braucht ca. mind 15 Minuten bis der Anmeldebildschirm erscheint.
Bei der Anmeldung kommt dann die o.g. Fehlermeldung.
In der registry und im Datei explorer habe ich alle Einträge mit MySQL sorfältig entfernt und das Programm danach nochmals installiert.
Auffällig ist auch, daß der Dienst j-lawyer server sich öfters beendet.
Hier ist die Server. log.

]‘
2025-03-24 17:23:56,753 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
2025-03-24 17:23:56,816 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\journal,bindingsDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\largemessages,pagingDirectory=C:\Program Files\j-lawyer-server\wildfly\standalone\data\activemq\paging)
2025-03-24 17:23:56,854 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221013: Using NIO Journal
2025-03-24 17:25:25,704 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
2025-03-24 17:25:25,706 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
2025-03-24 17:25:25,708 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2025-03-24 17:25:25,709 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
2025-03-24 17:25:25,864 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221034: Waiting indefinitely to obtain live lock
2025-03-24 17:25:25,865 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221035: Live Server Obtained live lock
2025-03-24 17:25:27,094 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
2025-03-24 17:25:27,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
2025-03-24 17:25:27,110 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221003: Deploying ANYCAST queue jms.queue.searchIndexProcessorQueue on address jms.queue.searchIndexProcessorQueue
2025-03-24 17:25:27,112 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221003: Deploying ANYCAST queue jms.queue.outgoingMailProcessorQueue on address jms.queue.outgoingMailProcessorQueue
2025-03-24 17:25:27,115 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2025-03-24 17:25:27,115 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2025-03-24 17:25:27,115 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
2025-03-24 17:25:27,115 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
2025-03-24 17:25:27,743 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221007: Server is now live
2025-03-24 17:25:27,744 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 154) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [default, nodeID=dab191e0-8e1d-11ee-8f82-b0a4607a48b5]
2025-03-24 17:25:27,765 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 158) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „DESKTOP-EV2SMF6“. If this new address is incorrect please manually configure the connector to use the proper one.
2025-03-24 17:25:27,783 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 158) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2025-03-24 17:25:27,785 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 155) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
2025-03-24 17:25:27,836 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0007: Registered connection factory java:/JmsXA
2025-03-24 17:25:27,924 INFO [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-5) AMQ151007: Resource adaptor started
2025-03-24 17:25:27,924 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-5) IJ020002: Deployed: file://RaActivatoractivemq-ra
2025-03-24 17:25:27,931 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
2025-03-24 17:25:27,931 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
2025-03-24 17:28:51,899 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.5.0.Final (Apache CXF 3.4.10)
2025-03-24 17:28:56,749 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was ‚add‘ at address ‚[
(„core-service“ => „management“),
(„management-interface“ => „http-interface“)
]‘

Die Error Meldung am Schluß sagt mir leider nichts.
Das Programm scheint nach dem Möglichkeiten wirklich klasse zu sein, aber, außer nach einer Neuinstallation des Betriebssystems habe ich das Programm nie zum Laufen gebracht.
Besten Dank für die Hilfe