[PROBLEM] J-Laywer Server installieren

[Thartat]

Hallo,
ich versuch gerade den J-Laywer Server auf meinem STrato Server zu installieren umd danach mit dem Client darauf zuzugreifen.

Beim Starten des Servers kommt folgender fehler:

17:43:20,530 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
17:43:20,514 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
17:43:20,545 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
17:43:20,561 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 2.0.19.Final stopping
17:43:20,592 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = mysql
17:43:20,608 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
17:43:20,530 ERROR [org.jboss.as.controller.client] (ServerService Thread Pool — 58) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@445a00f8 for operation add at address [
(„subsystem“ => „messaging-activemq“),
(„server“ => „default“),
(„security-setting“ => „#“),
(„role“ => „guest“)
] failed handling operation rollback — java.lang.IllegalStateException
17:43:20,749 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:43:20,795 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 36ms
Drücken Sie eine beliebige Taste . . .

[j-lawyer.org]

Hallo,

das schaut mir nicht wie ein vollständiges Log aus. Ggf. mal das vollständige server.log per E-Mail bereitstellen.

https://www.j-lawyer.org/?topic=wo-findet-man-die-fehlerprotokolle-des-j-lawyer-org-servers-und-clients

Ansonsten ist das hier bei nahezu JEDEM Strato-Server das Problem:

https://www.j-lawyer.org/?topic=fehler-beim-start-des-servers-auf-ubuntu-vserver

Grüße
Jens / j-lawyer.org

• Diese Antwort wurde vor vor 3 years, 9 months von j-lawyer.org bearbeitet.

[Thartat]

Sorry hätte nicht gedacht das der komplette Log Interessant ist. Strato Server läuft mit Windows. und wird als Remotedesktop verwendet.

C:\Program Files\j-lawyer-server>set JAVA_HOME=C:\Program Files\j-lawyer-server\jre

C:\Program Files\j-lawyer-server>cd wildfly/bin

C:\Program Files\j-lawyer-server\wildfly\bin>standalone -c standalone.xml -b 0.0.0.0
Calling „C:\Program Files\j-lawyer-server\wildfly\bin\standalone.conf.bat“
Setting JAVA property to „C:\Program Files\j-lawyer-server\jre\bin\java“
===============================================================================

JBoss Bootstrap Environment

JBOSS_HOME: „C:\Program Files\j-lawyer-server\wildfly“

JAVA: „C:\Program Files\j-lawyer-server\jre\bin\java“

JAVA_OPTS: „-Dprogram.name=standalone.bat -Xms256M -Xmx1024M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=384m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman “

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

17:42:55,270 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.0.Final
17:42:56,756 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.5.Final
17:42:56,803 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
17:42:57,209 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) starting
17:42:57,428 INFO [org.jboss.vfs] (MSC service thread 1-7) VFS000002: Failed to clean existing content for temp file provider of type temp. Enable DEBUG level log to find what caused this
17:42:58,631 INFO [org.wildfly.security] (ServerService Thread Pool — 25) ELY00001: WildFly Elytron version 1.8.0.Final
17:42:59,897 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.
17:42:59,975 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool — 29) 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.
17:43:00,022 WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 20) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.
17:43:02,272 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
17:43:02,319 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.6.5.Final
17:43:02,334 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.6.5.Final
17:43:02,428 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.
17:43:02,428 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 61) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
17:43:02,444 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool — 59) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
17:43:02,459 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 49) WFLYCLINF0001: Activating Infinispan subsystem.
17:43:02,459 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 56) WFLYJSF0007: Activated the following JSF Implementations: [main]
17:43:02,475 INFO [org.jboss.as.naming] (ServerService Thread Pool — 62) WFLYNAM0001: Activating Naming Subsystem
17:43:02,475 INFO [org.jboss.as.security] (ServerService Thread Pool — 68) WFLYSEC0002: Activating Security Subsystem
17:43:02,475 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 72) WFLYWS0002: Activating WebServices Extension
17:43:02,490 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
17:43:02,506 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 51) WFLYRS0016: RESTEasy version 3.6.3.Final
17:43:02,600 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool — 60) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
17:43:02,615 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
17:43:02,631 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.19.Final starting
17:43:02,631 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.12.Final)
17:43:02,694 INFO [org.wildfly.extension.io] (ServerService Thread Pool — 50) WFLYIO001: Worker ‚default‘ has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
17:43:02,772 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
17:43:02,803 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
17:43:02,819 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
17:43:02,819 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
17:43:02,959 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)
17:43:02,976 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = mysql
17:43:03,055 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.8.Final
17:43:03,115 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
17:43:03,132 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
17:43:03,213 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 71) WFLYUT0014: Creating file handler for path ‚C:\Program Files\j-lawyer-server\wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
17:43:03,240 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
17:43:03,240 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
17:43:03,272 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
17:43:03,287 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
17:43:03,397 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) 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: bind /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:1363)
at java.lang.Thread.run(Thread.java:748)

17:43:03,544 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
17:43:03,694 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
17:43:03,694 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jlawyerdb]
17:43:04,069 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
17:43:04,100 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Program Files\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
17:43:04,117 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Program Files\j-lawyer-server\wildfly\standalone\deployments
17:43:04,131 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of „j-lawyer-server.ear“ (runtime-name: „j-lawyer-server.ear“)
17:43:04,365 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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: bind /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:1377)
at java.lang.Thread.run(Thread.java:748)

17:43:04,365 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) 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: bind /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)

17:43:06,070 INFO [org.jboss.vfs] (MSC service thread 1-2) VFS000002: Failed to clean existing content for temp file provider of type deployment. Enable DEBUG level log to find what caused this
17:43:19,639 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib\jcifs-1.3.18.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
17:43:19,639 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib\jsch-0.1.54.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
17:43:19,639 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib\commons-vfs2-2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
17:43:19,639 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib\commons-net-3.5.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear does not point to a valid jar for a Class-Path reference.
17:43:19,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/xmlrpc-client-3.1.3.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
17:43:19,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/xmlrpc-common-3.1.3.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
17:43:19,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/ws-commons-util-1.0.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
17:43:19,655 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/log4j-1.2.16.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-fax.jar does not point to a valid jar for a Class-Path reference.
17:43:19,670 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jena-iri-0.9.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,670 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry slf4j-api-1.5.6.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,670 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry log4j-1.2.16.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,670 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry java-rdfa-htmlparser-0.4.2-RC2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry htmlparser-1.2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/java-rdfa-0.4.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-core-2.3.0.1.jar does not point to a valid jar for a Class-Path reference.
17:43:19,703 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/FastInfoset.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,703 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/gmbal-api-only.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,703 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/ha-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,703 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/javax.mail_1.4.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jaxws-rt.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jaxws-tools.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/management-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/mimepull.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/policy.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/saaj-impl.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/stax-ex.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,749 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/stax2-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,749 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/streambuffer.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,749 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/woodstox-core-asl.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,749 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jaxws-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,749 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jsr181-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,764 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/javax.annotation.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,764 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/saaj-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,764 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/activation.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,764 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/jaxb-api.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,764 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/hamcrest-core-1.3.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,780 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry lib/org-netbeans-modules-java-j2seproject-copylibstask.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/j-lawyer-drebis-stubs.jar does not point to a valid jar for a Class-Path reference.
17:43:19,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-runtime-2.3.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry txw2-2.3.2.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,795 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry istack-commons-runtime-3.0.8.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,811 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry stax-ex-1.8.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,811 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry FastInfoset-1.2.16.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,811 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jakarta.activation-api-1.2.1.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/lib/jaxb-impl-2.3.2.jar does not point to a valid jar for a Class-Path reference.
17:43:19,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
17:43:19,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
17:43:19,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
17:43:19,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
17:43:19,858 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
17:43:19,983 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry lib/tika-app-1.5.jar in /C:/Program Files/j-lawyer-server/wildfly/bin/content/j-lawyer-server.ear/j-lawyer-server-ejb.jar does not point to a valid jar for a Class-Path reference.
17:43:19,999 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: bind /0.0.0.0:9990“}}
17:43:20,014 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: bind /0.0.0.0:8080“}}
17:43:20,014 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: bind /0.0.0.0:8443“}}
17:43:20,014 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]“]
}
17:43:20,030 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: bind /0.0.0.0:9990“}}
17:43:20,077 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-io.war) in 44ms
17:43:20,092 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-ejb.jar) in 49ms
17:43:20,092 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-entities.jar) in 51ms
17:43:20,108 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-io.war) in 70ms
17:43:20,186 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0208: Stopped subdeployment (runtime-name: j-lawyer-server-war.war) in 156ms
17:43:20,467 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 426ms
17:43:20,483 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
17:43:20,514 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: Host default-host stopping
17:43:20,514 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool — 58) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@445a00f8 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)

17:43:20,530 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:/jlawyerdb]
17:43:20,514 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
17:43:20,545 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
17:43:20,561 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 2.0.19.Final stopping
17:43:20,592 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = mysql
17:43:20,608 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2
17:43:20,530 ERROR [org.jboss.as.controller.client] (ServerService Thread Pool — 58) WFLYCTL0190: Step handler org.jboss.as.controller.AbstractAddStepHandler$1@445a00f8 for operation add at address [
(„subsystem“ => „messaging-activemq“),
(„server“ => „default“),
(„security-setting“ => „#“),
(„role“ => „guest“)
] failed handling operation rollback — java.lang.IllegalStateException
17:43:20,749 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
17:43:20,795 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) stopped in 36ms
Drücken Sie eine beliebige Taste . . .
Batchvorgang abbrechen (J/N)?

[j-lawyer.org]

Port 8080 ist bereits belegt:

org.wildfly.undertow.listener.default: Address already in use: bind /0.0.0.0:8080

Wenn bei Installation die Variante „als Dienst installieren“ genutzt wurde, muss der Server nicht manuell gestartet werden. Er läuft dann automatisch im Hintergrund. Diensteverwaltung prüfen.

[Thartat]

Wie greife ich denn jetzt von einem anderen Computer auf den Server zu? Mit dem Root Passwort finde ich keine J-Lawyer Box.

[j-lawyer.org]

root-Passwort unter Windows??

Im Logindialog des Clients, unter „Verbindung“ muss die IP / der Hostname des Strato-Servers eingegeben werden. Die voreingestellten Nutzer sind in der Installationsanleitung zu finden und sollten anschließend geändert werden.

[Thartat]

Jetzt bekomm ich die Fehlermeldung „Aufbau des SSH-Tunnels gescheitert: timeout: socket is not established“

[j-lawyer.org]

SSH-Tunnel? Haben Sie auf dem Windows-Server einen SSH-Server installiert?

Wenn nicht, dann ist Sicherheit „Standard“ zu verwenden.

[Thartat]

Vielen Vielen Dank!

jetzt hab ich nur noch „Anmeldedaten oder verbindungsparameter falsch“

In Verbindung Nutzer: root und Passwort geb ich das Root Passwort von dem Server ein, richtig?

Dann kann ich eigentlich nur der Port bzw die Host/ IP falsch sein

[j-lawyer.org]

Wie erwähnt, die voreingestellten Nutzer findet man in der Install-Anleitung:

https://www.j-lawyer.org/?page_id=100

Das Passwort für die Datenbank gehört niemals in die Hände der Nutzer, daher ist im Logindialog auch niemals ein Datenbankpasswort einzugeben, sondern Nutzer und Passwort für einen Nutzer der Kanzleisoftware.

[Thartat]

Hallo, wo finde ich den Nutzer und das Passwort das ich bei Verbnindung hinterlege?

[j-lawyer.org]

Hallo, wo finde ich den Nutzer und das Passwort das ich bei Verbnindung hinterlege?

Bin mir gerade nicht sicher was gemeint ist – geht es um die Angaben unter „Verbindung“ im Login-Dialog? Oder geht es um Nutzername und Passwort? Für den zweiten Punkt hatte ich oben bereits einen Link hinterlassen, wo die voreingestellten Nutzer zu finden sind.

Grüße!

[Thartat]

Die IP Adresse hab ich geändert wie beschrieben (Bearbeiten Sie die Datei /wildfly-9.0.2.Final/standalone/configuration/standalone-full.xml)

Die IP Adresse ist auch die richtie hab ich im cmd gegengeprüft. Anschließend auch neu gestartet!

Nun weiß ich nicht was ich in den weiteren Einstellung eingeben muss. Aktuell versuch ich es mit den vorgegeben Benutzer Admin + Passwort und es geht nicht.

[j-lawyer.org]

Dann bitte nochmal das Server.log per Mail schicken

https://www.j-lawyer.org/?topic=wo-findet-man-die-fehlerprotokolle-des-j-lawyer-org-servers-und-clients

[j-lawyer.org]

PS: Laufen denn Server und Client auf dem selben Gerät? Wenn nicht, muss statt „localhost“ dort die IP des Servers eingetragen werden.

[Autor]

Beiträge