Startseite › Foren › Installation › Upgrade unter Trixie
- This topic has 0 Antworten, 1 Stimme, and was last updated vor 4 hours, 30 minutes by
Toptec-IT.
-
AutorBeiträge
-
16. Januar 2026 um 11:19 #7298
Toptec-IT
ParticipantHallo,
bei einem test Update auf die aktuelle server version vom 11.01. kam es zu fehlern b3ei der Verbdinung mit der Datenbank unter Debian Trixi.
Mariadb 11.8.3
Debian Trixi2026-01-16 00:14:11,912 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.
2026-01-16 00:14:11,912 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.
2026-01-16 00:14:11,912 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.
2026-01-16 00:14:11,913 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.
2026-01-16 00:14:11,916 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.
2026-01-16 00:14:11,917 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
2026-01-16 00:14:11,917 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
2026-01-16 00:14:11,917 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
2026-01-16 00:14:11,917 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
2026-01-16 00:14:11,917 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) 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.
2026-01-16 00:14:14,955 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller‘
2026-01-16 00:14:15,041 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2026-01-16 00:14:15,042 INFO [org.infinispan.CONFIG] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2026-01-16 00:14:15,061 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
2026-01-16 00:14:15,077 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 82) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
2026-01-16 00:14:15,094 INFO [org.hibernate.Version] (ServerService Thread Pool — 85) HHH000412: Hibernate Core {5.3.28.Final}
2026-01-16 00:14:15,095 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 85) HHH000206: hibernate.properties not found
2026-01-16 00:14:15,097 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-3) No shutdown hook registered: Please call close() manually on application shutdown.
2026-01-16 00:14:15,098 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.WildFlyS
ender@345ce65b, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=mayer-J-Lawer, jaeger.version=Java-1.6.0, ip=127.0.1.1}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
2026-01-16 00:14:15,174 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.9 (Final)
2026-01-16 00:14:15,384 INFO [org.jipijapa] (MSC service thread 1-4) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
2026-01-16 00:14:15,531 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 85) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
2026-01-16 00:14:16,313 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 83) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
2026-01-16 00:14:16,380 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 83) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
2026-01-16 00:14:16,425 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 83) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
2026-01-16 00:14:16,425 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 83) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j
-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.jboss.as.jpa@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: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
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.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
… 22 more
ich habe anstelle des mysql connectors mal den Mariadb-java-client eingesetzt.
Dann war der Datenbank Fehler weg, aber es kam ein haufen neuer Fehler, habe da abgebrochen.Heute Abend würde ich das nochmal testen und schauen wie ich die fehler weg bekomme nach tausch der datenbank connector jar.
-
AutorBeiträge
- Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.
