Startseite › Foren › Hilfe bei Problemen › J- Lawyer startet nicht mehr
- Dieses Thema hat 8 Antworten sowie 2 Stimmen und wurde zuletzt vor vor 3 Jahren, 11 Monaten von Dennis aktualisiert.
-
AutorBeiträge
-
8. November 2020 um 20:48 #3928DennisTeilnehmer
J Lawyer startet nicht mehr. Auch nach einem Neustart des MacBook, einem Neustart von MySQL, sowie dem Versuch den J Lawyer Server manuell zu starten, hängt sich der Client beim Start immer nach der Passworteingabe auf, während die Anwendung geladen wird. Nachfolgend die Fehlermeldung:
Last login: Sun Nov 8 19:03:57 on console
Sansi-MBP-2:~ sansi78$ cd
Sansi-MBP-2:~ sansi78$ cd /Applications/j-lawyer-server
Sansi-MBP-2:j-lawyer-server sansi78$ sudo sh start-server-mac.sh
Password:
=========================================================================JBoss Bootstrap Environment
JBOSS_HOME: /Applications/j-lawyer-server/wildfly
JAVA: /Applications/j-lawyer-server/.install4j/jre.bundle/Contents/Home/bin/java
JAVA_OPTS: -server -Xms256m -Xmx1024m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
19:10:23,705 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
19:10:25,109 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
19:10:25,129 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
19:10:25,384 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
19:10:26,732 INFO [org.wildfly.security] (ServerService Thread Pool — 26) ELY00001: WildFly Elytron version 1.8.0.Final
19:10:30,242 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/core-service=management/management-interface=http-interface‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
19:10:30,364 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 22) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
19:10:30,380 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool — 35) WFLYCTL0028: Attribute ’security-realm‘ in the resource at address ‚/subsystem=undertow/server=default-server/https-listener=https‘ is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
19:10:32,790 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
19:10:32,814 INFO [org.xnio] (MSC service thread 1-4) XNIO version 3.6.5.Final
19:10:32,831 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.6.5.Final
19:10:32,934 WARN [org.jboss.as.txn] (ServerService Thread Pool — 70) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
19:10:32,979 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool — 60) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
19:10:32,994 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 49) WFLYCLINF0001: Activating Infinispan subsystem.
19:10:32,999 INFO [org.jboss.as.security] (ServerService Thread Pool — 68) WFLYSEC0002: Activating Security Subsystem
19:10:33,008 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 72) WFLYWS0002: Activating WebServices Extension
19:10:33,009 INFO [org.jboss.as.naming] (ServerService Thread Pool — 62) WFLYNAM0001: Activating Naming Subsystem
19:10:33,032 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool — 59) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
19:10:33,033 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
19:10:33,064 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
19:10:33,077 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 50) WFLYIO001: Worker ‚default‘ has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
19:10:33,080 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
19:10:33,086 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.12.Final)
19:10:33,115 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=5.0.3.Final
19:10:33,137 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
19:10:33,201 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
19:10:33,232 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
19:10:33,359 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2
19:10:33,406 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.8.Final
19:10:33,604 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
19:10:33,687 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.19.Final starting
19:10:33,773 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql
19:10:33,949 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
19:10:33,949 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
19:10:34,019 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host.
19:10:34,020 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing.
19:10:34,105 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 71) WFLYUT0014: Creating file handler for path ‚/Applications/j-lawyer-server/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
19:10:34,139 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 51) WFLYRS0016: RESTEasy version 3.6.3.Final
19:10:34,406 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
19:10:34,408 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
19:10:34,524 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
19:10:34,577 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.undertow.listener.default: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.default: Address already in use /0.0.0.0:8080
at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)19:10:34,646 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/jlawyerdb]
19:10:34,651 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
19:10:36,519 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
19:10:36,568 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /Applications/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
19:10:36,584 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /Applications/j-lawyer-server/wildfly/standalone/deployments
19:10:36,605 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“)
19:10:36,758 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.undertow.listener.https: org.jboss.msc.service.StartException in service org.wildfly.undertow.listener.https: Address already in use /0.0.0.0:8443
at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:209)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
at java.lang.Thread.run(Thread.java:748)19:10:36,906 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.management.http.extensible: org.jboss.msc.service.StartException in service org.wildfly.management.http.extensible: java.net.BindException: Address already in use /0.0.0.0:9990
at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:349)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)19:11:06,147 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
19:11:06,149 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
19:11:06,155 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
19:11:06,155 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
19:11:06,161 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/xmlrpc-client-3.1.3.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
19:11:06,162 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/xmlrpc-common-3.1.3.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
19:11:06,163 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
19:11:06,170 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/log4j-1.2.16.jar in /content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
19:11:06,187 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,224 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/j-lawyer-server.ear/lib/jaxb-core-2.3.0.1.jar does not point to a valid jar for a Class-Path reference.
19:11:06,241 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/FastInfoset.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,251 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/gmbal-api-only.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,251 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/ha-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,251 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/javax.mail_1.4.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,252 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jaxws-rt.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,253 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jaxws-tools.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,253 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/management-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,254 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/mimepull.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,254 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/policy.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,254 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/saaj-impl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,254 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/stax-ex.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,256 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/stax2-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,257 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/streambuffer.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,257 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/woodstox-core-asl.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,265 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jaxws-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,274 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jsr181-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,274 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/javax.annotation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,276 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/saaj-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,277 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/activation.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,277 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/jaxb-api.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,279 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/hamcrest-core-1.3.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,279 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/org-netbeans-modules-java-j2seproject-copylibstask.jar in /content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
19:11:06,294 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,295 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,296 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
19:11:06,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
19:11:06,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
19:11:06,333 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
19:11:06,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
19:11:06,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
19:11:06,366 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) 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.
19:11:06,634 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („add“) failed – address: ([
(„core-service“ => „management“),
(„management-interface“ => „http-interface“)
]) – failure description: {„WFLYCTL0080: Failed services“ => {„org.wildfly.management.http.extensible“ => „java.net.BindException: Address already in use /0.0.0.0:9990“}}
19:11:06,638 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („add“) failed – address: ([
(„subsystem“ => „undertow“),
(„server“ => „default-server“),
(„http-listener“ => „default“)
]) – failure description: {„WFLYCTL0080: Failed services“ => {„org.wildfly.undertow.listener.default“ => „Address already in use /0.0.0.0:8080“}}
19:11:06,639 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („add“) failed – address: ([
(„subsystem“ => „undertow“),
(„server“ => „default-server“),
(„https-listener“ => „https“)
]) – failure description: {„WFLYCTL0080: Failed services“ => {„org.wildfly.undertow.listener.https“ => „Address already in use /0.0.0.0:8443“}}
19:11:06,641 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („add“) failed – address: ([
(„subsystem“ => „messaging-activemq“),
(„server“ => „default“)
]) – failure description: {
„WFLYCTL0412: Required services that are not installed:“ => [„jboss.http-upgrade-registry.default“],
„WFLYCTL0180: Services with missing/unavailable dependencies“ => [„jboss.messaging-activemq.default is missing [jboss.http-upgrade-registry.default]“]
}
19:11:06,642 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („add“) failed – address: ([
(„core-service“ => „management“),
(„management-interface“ => „http-interface“)
]) – failure description: {„WFLYCTL0080: Failed services“ => {„org.wildfly.management.http.extensible“ => „java.net.BindException: Address already in use /0.0.0.0:9990“}}
19:11:06,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-io.war) in 40ms
19:11:06,705 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-ejb.jar) in 46ms
19:11:06,707 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-entities.jar) in 48ms
19:11:06,708 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-war.war) in 49ms
19:11:06,708 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-io.war) in 47ms
19:11:06,790 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment j-lawyer-server.ear (runtime-name: j-lawyer-server.ear) in 129ms
19:11:06,807 ERROR [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0021: Deploy of deployment „j-lawyer-server.ear“ was rolled back with the following failure message: undefined
19:11:06,815 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool — 58) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@2e1deee9 for operation add at address [
(„subsystem“ => „messaging-activemq“),
(„server“ => „default“),
(„security-setting“ => „#“),
(„role“ => „guest“)
] failed handling operation rollback — java.lang.IllegalStateException: java.lang.IllegalStateException
at org.wildfly.extension.messaging.activemq.ActiveMQServerService.getValue(ActiveMQServerService.java:326)
at org.wildfly.extension.messaging.activemq.ActiveMQServerService.getValue(ActiveMQServerService.java:79)
at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1110)
at org.jboss.msc.service.DelegatingServiceController.getValue(DelegatingServiceController.java:103)
at org.wildfly.extension.messaging.activemq.SecurityRoleAdd.getServer(SecurityRoleAdd.java:84)
at org.wildfly.extension.messaging.activemq.SecurityRoleAdd.rollbackRuntime(SecurityRoleAdd.java:74)
at org.jboss.as.controller.AbstractAddStepHandler$1$1.handleRollback(AbstractAddStepHandler.java:164)
at org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1561)
at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1533)
at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1515)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1472)
at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1455)
at org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1319)
at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:876)
at org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:862)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:769)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:485)19:11:06,825 ERROR [org.jboss.as.controller.client] (ServerService Thread Pool — 58) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@2e1deee9 for operation add at address [
(„subsystem“ => „messaging-activemq“),
(„server“ => „default“),
(„security-setting“ => „#“),
(„role“ => „guest“)
] failed handling operation rollback — java.lang.IllegalStateException
19:11:06,855 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
19:11:06,863 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping
19:11:06,880 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
19:11:06,880 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
19:11:06,901 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 2.0.19.Final stopping
19:11:06,910 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = mysql
19:11:06,919 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
19:11:06,963 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
19:11:06,979 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 12ms
Sansi-MBP-2:j-lawyer-server sansi78$Was kann ich tun?
8. November 2020 um 20:54 #3929j-lawyer.orgAdministratorDie Ausgabe beim manuellen Start meint
Address already in use /0.0.0.0:9990
Das heisst dass entweder der j-lawyer.org Server bereits läuft, oder eine andere Software den Netzwerkport 9990 belegt, der von j-lawyer benötigt wird.
Wird der Server denn grundsätzlich manuell gestartet, oder automatisch?
Wenn automatisch, dann bitte wie folgt vorgehen:
– /Applications/j-lawyer-server/wildfly/standalone/log/server.log löschen
– MacBook neu starten
– nach dem Neustart 2min warten
– das server.log an mich per E-MailGrüße,
Jens
(j-lawyer.org)8. November 2020 um 21:10 #3930DennisTeilnehmerDanke Jens.
Ich probiere das gleich aus. Mich verwundert nur, dass ich einen anderen Nutzer starten kann und der auch ohne Probleme funktioniert, das habe ich eben noch festgestellt.
Grüße,
Dennis
8. November 2020 um 21:19 #3931j-lawyer.orgAdministratorIch probiere das gleich aus. Mich verwundert nur, dass ich einen anderen Nutzer starten kann und der auch ohne Probleme funktioniert
Das verstehe ich nicht genau – der Login im j-lawyer.org Client funktioniert, wenn Du einen anderen Nutzer nimmst?
8. November 2020 um 21:48 #3932DennisTeilnehmerganz genau so ist es…ich habe noch den Nutzer „user“ eingerichtet…den kann ich starten, die Akten werden angezeigt.
Deinen Weg habe ich auch probiert. Die Löschung wurde aber zurückgewiesen „denied“
8. November 2020 um 21:49 #3933j-lawyer.orgAdministratorIst das Passwort des einen Nutzers aus Versehen geändert worden? Hast du noch einen anderen Admin-Nutzer, mit dem Du das Passwort neu setzen kannst?
8. November 2020 um 21:54 #3934DennisTeilnehmer…der Client hängt sich auch immer an der selben Stelle auf, nämlich bei „Laden der fehlenden Wiedervorlagen“
8. November 2020 um 22:05 #3935j-lawyer.orgAdministratorDas wird sich ohne Fernwartung schlecht lösen lassen. Bei Bedarf AnyDesk installieren (anydesk.com/de) und die Nr. per Email an mich.
8. November 2020 um 22:09 #3936DennisTeilnehmerDas Passwort dürfte nicht geändert worden sein. Wenn ich ein falsches eingebe, dann kommt auch sofort eine entsprechende Fehlermeldung. Ich gehe daher davon aus, dass das PW richtig ist.
Einen anderen admin Nutzer habe ich nicht.
Ok, ich lade mir Anydesk runter.
-
AutorBeiträge
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.