Problem bei Installation des Docker-Containers

Startseite › Foren › Installation › Problem bei Installation des Docker-Containers

Verschlagwortet: 

7 Beiträge anzeigen - 1 bis 7 (von insgesamt 7)
  • Autor
    Beiträge
  • 29. November 2024 um 17:33 #6589
    Dersim Özdag
    Participant

    Hallo zusammen,

    ich wollte heute mal j-lawyer ausprobieren, habe aber immer das gleiche Problem: Nach einrichten der Docker-Installation startet der Server nicht vollständig. Ein Einloggen ist leider nicht möglich und swagger-ui gibt 404 zurück. WildFly startet jedoch.

    Hier der Log:

    date stream content
    2024/11/29 15:01:36 stdout [0m[0m14:01:36,494 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
    2024/11/29 15:01:36 stdout [0m[0m14:01:36,487 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    2024/11/29 15:01:36 stdout [0m[31m14:01:36,463 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 59865ms – Started 3451 of 4111 services (473 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
    2024/11/29 15:01:36 stdout [0m[0m14:01:36,437 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2024/11/29 15:01:36 stdout WFLYCTL0448: 452 additional services are down due to their dependencies being missing or failed
    2024/11/29 15:01:36 stdout service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:36 stdout WFLYCTL0186: Services which failed to start: 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]
    2024/11/29 15:01:36 stdout [0m[0m14:01:36,064 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    2024/11/29 15:01:36 stdout [0m[0m14:01:36,048 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2024/11/29 15:01:35 stdout }}
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“,
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout „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]
    2024/11/29 15:01:35 stdout [0m[31m14:01:35,633 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“ => {
    2024/11/29 15:01:35 stdout
    2024/11/29 15:01:35 stdout … 22 more
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
    2024/11/29 15:01:35 stdout … 10 more
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
    2024/11/29 15:01:35 stdout at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
    2024/11/29 15:01:35 stdout at java.base/java.lang.Thread.run(Thread.java:834)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
    2024/11/29 15:01:35 stdout at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
    2024/11/29 15:01:35 stdout at java.base/java.security.AccessController.doPrivileged(Native Method)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
    2024/11/29 15:01:35 stdout [0m[31m14:01:35,529 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 90) 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]
    2024/11/29 15:01:35 stdout
    2024/11/29 15:01:35 stdout … 22 more
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set
    2024/11/29 15:01:35 stdout … 10 more
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:171)
    2024/11/29 15:01:35 stdout at org.hibernate.jipijapa-hibernate5-3@26.1.3.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    2024/11/29 15:01:35 stdout at org.hibernate@5.3.28.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
    2024/11/29 15:01:35 stdout Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513)
    2024/11/29 15:01:35 stdout at java.base/java.lang.Thread.run(Thread.java:834)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    2024/11/29 15:01:35 stdout at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:214)
    2024/11/29 15:01:35 stdout at org.wildfly.security.elytron-base@1.19.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:664)
    2024/11/29 15:01:35 stdout at java.base/java.security.AccessController.doPrivileged(Native Method)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:129)
    2024/11/29 15:01:35 stdout at org.jboss.as.jpa@26.1.3.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:199)
    2024/11/29 15:01:35 stdout [0m[31m14:01:35,528 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 89) 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“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    2024/11/29 15:01:35 stdout [0m[33m14:01:35,524 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 89) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024/11/29 15:01:35 stdout [0m[33m14:01:35,522 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 90) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024/11/29 15:01:35 stdout [0m[0m14:01:35,428 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 90) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024/11/29 15:01:35 stdout [0m[0m14:01:35,429 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 89) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024/11/29 15:01:35 stdout [0m[0m14:01:35,173 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0042: Started message driven bean ‚OutgoingMailProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024/11/29 15:01:35 stdout [0m[0m14:01:35,172 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024/11/29 15:01:35 stdout [0m[0m14:01:35,083 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 89) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024/11/29 15:01:33 stdout [0m[0m14:01:33,664 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 90) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024/11/29 15:01:32 stdout [0m[0m14:01:32,953 INFO [org.jipijapa] (MSC service thread 1-1) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
    2024/11/29 15:01:31 stdout [0m[0m14:01:31,304 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 90) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    2024/11/29 15:01:30 stdout [0m[0m14:01:30,292 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 90) HHH000206: hibernate.properties not found
    2024/11/29 15:01:30 stdout [0m[0m14:01:30,289 INFO [org.hibernate.Version] (ServerService Thread Pool — 90) HHH000412: Hibernate Core {5.3.28.Final}
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,609 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 91) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,545 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 91) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
    2024/11/29 15:01:29 stdout …]
    2024/11/29 15:01:29 stdout name: j-lawyer-server-ejbPU
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,475 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 89) HHH000204: Processing PersistenceUnitInfo [
    2024/11/29 15:01:29 stdout …]
    2024/11/29 15:01:29 stdout name: j-lawyer-server-ejbPU
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,444 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 90) HHH000204: Processing PersistenceUnitInfo [
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,390 INFO [org.infinispan.CONFIG] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,366 INFO [org.infinispan.CONFIG] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,292 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 89) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024/11/29 15:01:29 stdout [0m[0m14:01:29,273 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 90) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024/11/29 15:01:28 stdout [0m[0m14:01:28,585 INFO [org.jipijapa] (MSC service thread 1-5) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
    2024/11/29 15:01:28 stdout [0m[0m14:01:28,023 INFO [org.jboss.weld.Version] (MSC service thread 1-6) WELD-000900: 3.1.9 (Final)
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,814 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) 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@53d251c2, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=4e1d1ebd1278, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,813 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-8) No shutdown hook registered: Please call close() manually on application shutdown.
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,716 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-5) WFLYTRAC0001: Tracer initialized: NoopTracer
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,642 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-7) 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@5e9bddab, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=4e1d1ebd1278, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,642 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-server-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@35f9473c, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=4e1d1ebd1278, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,640 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-3) No shutdown hook registered: Please call close() manually on application shutdown.
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,628 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-7) No shutdown hook registered: Please call close() manually on application shutdown.
    2024/11/29 15:01:27 stdout
    2024/11/29 15:01:27 stdout java:module/AppRoleBeanFacade
    2024/11/29 15:01:27 stdout java:app/j-lawyer-server-ejb/AppRoleBeanFacade
    2024/11/29 15:01:27 stdout java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade
    2024/11/29 15:01:27 stdout java:module/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
    2024/11/29 15:01:27 stdout java:app/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
    2024/11/29 15:01:27 stdout java:global/j-lawyer-server/j-lawyer-server-ejb/AppRoleBeanFacade!com.jdimension.jlawyer.persistence.AppRoleBeanFacadeLocal
    2024/11/29 15:01:27 stdout
    2024/11/29 15:01:27 stdout [0m[0m14:01:27,533 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-5) 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:
    2024/11/29 15:01:27 stdout

    29. November 2024 um 17:37 #6591
    j-lawyer.org
    Keymaster

    Hallo,

    der Docker-Container ist nicht für den produktiven Einsatz gedacht und wird hier nur spärlich supported. Er ist primär für die Integratoren gedacht.

    Das Log oben weist daraufhin, dass keine Verbindung zur Datenbank besteht (oder ein anderes datenbankbezogenes Problem besteht). Ist das das gesamte Log? Ansonsten mal in den Container attachen und die Datei wildfly/standalone/log/server.log lesen.

    VG
    Jens / j-lawyer.org

    29. November 2024 um 20:20 #6593
    Dersim Özdag
    Participant

    Hi,

    Danke für deine Antwort!
    anbei das ganze Log:

    2024-11-29 17:19:32,521 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.2.Final
    2024-11-29 17:19:35,550 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.13.Final
    2024-11-29 17:19:35,571 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
    2024-11-29 17:19:35,943 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) starting
    2024-11-29 17:19:35,950 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
    [Standalone] =
    awt.toolkit = sun.awt.X11.XToolkit
    file.encoding = UTF-8
    file.separator = /
    java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.print.PSPrinterJob
    java.class.path = /opt/jboss/wildfly/jboss-modules.jar
    java.class.version = 55.0
    java.home = /usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el7_8.x86_64
    java.io.tmpdir = /tmp
    java.library.path = /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
    java.net.preferIPv4Stack = true
    java.runtime.name = OpenJDK Runtime Environment
    java.runtime.version = 11.0.8+10-LTS
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Oracle Corporation
    java.specification.version = 11
    java.util.logging.manager = org.jboss.logmanager.LogManager
    java.vendor = N/A
    java.vendor.url = https://openjdk.java.net/
    java.vendor.url.bug = https://bugreport.java.com/bugreport/
    java.vendor.version = 18.9
    java.version = 11.0.8
    java.version.date = 2020-07-14
    java.vm.compressedOopsMode = Zero based
    java.vm.info = mixed mode, sharing
    java.vm.name = OpenJDK 64-Bit Server VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Oracle Corporation
    java.vm.specification.version = 11
    java.vm.vendor = Oracle Corporation
    java.vm.version = 11.0.8+10-LTS
    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
    jboss.bind.address = 0.0.0.0
    jboss.home.dir = /opt/jboss/wildfly
    jboss.host.name = 6531dceb8d04
    jboss.modules.dir = /opt/jboss/wildfly/modules
    jboss.modules.system.pkgs = org.jboss.byteman
    jboss.node.name = 6531dceb8d04
    jboss.qualified.host.name = 6531dceb8d04
    jboss.server.base.dir = /opt/jboss/wildfly/standalone
    jboss.server.config.dir = /opt/jboss/wildfly/standalone/configuration
    jboss.server.data.dir = /opt/jboss/wildfly/standalone/data
    jboss.server.deploy.dir = /opt/jboss/wildfly/standalone/data/content
    jboss.server.log.dir = /opt/jboss/wildfly/standalone/log
    jboss.server.name = 6531dceb8d04
    jboss.server.persist.config = true
    jboss.server.temp.dir = /opt/jboss/wildfly/standalone/tmp
    jdk.debug = release
    line.separator =

    logging.configuration = file:/opt/jboss/wildfly/standalone/configuration/logging.properties
    module.path = /opt/jboss/wildfly/modules
    org.jboss.boot.log.file = /opt/jboss/wildfly/standalone/log/server.log
    org.jboss.resolver.warning = true
    os.arch = amd64
    os.name = Linux
    os.version = 4.4.302+
    path.separator = :
    sun.arch.data.model = 64
    sun.boot.library.path = /usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el7_8.x86_64/lib
    sun.cpu.endian = little
    sun.cpu.isalist =
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.command = /opt/jboss/wildfly/jboss-modules.jar -mp /opt/jboss/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/jboss/wildfly -Djboss.server.base.dir=/opt/jboss/wildfly/standalone -b 0.0.0.0
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = UTF-8
    sun.management.compiler = HotSpot 64-Bit Tiered Compilers
    sun.os.patch.level = unknown
    user.country = US
    user.dir = /opt/jboss
    user.home = /opt/jboss
    user.language = en
    user.name = jboss
    user.timezone = UTC
    2024-11-29 17:19:35,957 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms256m -Xmx3072m -XX:MetaspaceSize=128M -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 -Dorg.jboss.boot.log.file=/opt/jboss/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/jboss/wildfly/standalone/configuration/logging.properties
    2024-11-29 17:19:39,366 INFO [org.wildfly.security] (ServerService Thread Pool — 26) ELY00001: WildFly Elytron version 1.19.1.Final
    2024-11-29 17:19:43,190 INFO [org.jboss.as.repository] (ServerService Thread Pool — 30) WFLYDR0001: Content added at location /opt/jboss/wildfly/standalone/data/content/ac/a4cd6c026bd3ed7420f5c05fae91b054af1946/content
    2024-11-29 17:19:43,272 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
    2024-11-29 17:19:43,345 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.8.7.Final
    2024-11-29 17:19:43,369 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.8.7.Final
    2024-11-29 17:19:43,489 INFO [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool — 53) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
    2024-11-29 17:19:43,517 INFO [org.wildfly.extension.health] (ServerService Thread Pool — 54) WFLYHEALTH0001: Activating Base Health Subsystem
    2024-11-29 17:19:43,516 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 55) WFLYCLINF0001: Activating Infinispan subsystem.
    2024-11-29 17:19:43,555 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 57) WFLYRS0016: RESTEasy version 4.7.7.Final
    2024-11-29 17:19:43,633 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 62) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
    2024-11-29 17:19:43,590 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
    2024-11-29 17:19:43,662 INFO [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool — 66) WFLYCONF0001: Activating MicroProfile Config Subsystem
    2024-11-29 17:19:43,639 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
    2024-11-29 17:19:43,717 INFO [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool — 67) WFLYJWT0001: Activating MicroProfile JWT Subsystem
    2024-11-29 17:19:43,757 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.5.3.Final)
    2024-11-29 17:19:43,771 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.
    2024-11-29 17:19:43,793 INFO [org.wildfly.extension.metrics] (ServerService Thread Pool — 65) WFLYMETRICS0001: Activating Base Metrics Subsystem
    2024-11-29 17:19:43,794 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
    2024-11-29 17:19:43,801 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 68) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
    2024-11-29 17:19:43,876 INFO [org.jboss.as.naming] (ServerService Thread Pool — 69) WFLYNAM0001: Activating Naming Subsystem
    2024-11-29 17:19:43,887 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 78) WFLYWS0002: Activating WebServices Extension
    2024-11-29 17:19:43,937 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
    2024-11-29 17:19:43,943 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = mysql
    2024-11-29 17:19:43,993 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.25.Final
    2024-11-29 17:19:44,506 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
    2024-11-29 17:19:44,501 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
    2024-11-29 17:19:44,774 WARN [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY00023: KeyStore file ‚/opt/jboss/wildfly/standalone/configuration/application.keystore‘ does not exist. Used blank.
    2024-11-29 17:19:44,921 WARN [org.wildfly.extension.elytron] (MSC service thread 1-7) WFLYELY01084: KeyStore /opt/jboss/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
    2024-11-29 17:19:44,964 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.2.19.Final starting
    2024-11-29 17:19:45,190 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.
    2024-11-29 17:19:45,215 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
    2024-11-29 17:19:45,629 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 77) WFLYUT0014: Creating file handler for path ‚/opt/jboss/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
    2024-11-29 17:19:45,649 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
    2024-11-29 17:19:45,668 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) Queuing requests.
    2024-11-29 17:19:45,674 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
    2024-11-29 17:19:45,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
    2024-11-29 17:19:46,053 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
    2024-11-29 17:19:46,484 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
    2024-11-29 17:19:46,824 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jlawyerdb]
    2024-11-29 17:19:46,824 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    2024-11-29 17:19:47,313 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) 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.
    2024-11-29 17:19:47,323 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
    2024-11-29 17:19:47,338 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
    2024-11-29 17:19:47,424 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“)
    2024-11-29 17:19:47,732 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.5.0.Final (Apache CXF 3.4.10)
    2024-11-29 17:19:47,853 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/jboss/wildfly/standalone/data/activemq/journal,bindingsDirectory=/opt/jboss/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/opt/jboss/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/opt/jboss/wildfly/standalone/data/activemq/paging)
    2024-11-29 17:19:48,003 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221013: Using NIO Journal
    2024-11-29 17:19:49,019 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
    2024-11-29 17:19:49,022 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
    2024-11-29 17:19:49,024 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
    2024-11-29 17:19:49,025 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
    2024-11-29 17:19:49,462 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221034: Waiting indefinitely to obtain live lock
    2024-11-29 17:19:49,463 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221035: Live Server Obtained live lock
    2024-11-29 17:19:52,517 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
    2024-11-29 17:19:52,944 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
    2024-11-29 17:19:52,949 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.searchIndexProcessorQueue on address jms.queue.searchIndexProcessorQueue
    2024-11-29 17:19:52,955 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.outgoingMailProcessorQueue on address jms.queue.outgoingMailProcessorQueue
    2024-11-29 17:19:54,307 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2024-11-29 17:19:54,312 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2024-11-29 17:19:54,313 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
    2024-11-29 17:19:54,307 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    2024-11-29 17:19:56,006 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221007: Server is now live
    2024-11-29 17:19:56,007 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [default, nodeID=225a1f31-ae76-11ef-801b-0242ac160003]
    2024-11-29 17:19:56,057 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 84) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „6531dceb8d04“. If this new address is incorrect please manually configure the connector to use the proper one.
    2024-11-29 17:19:56,120 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    2024-11-29 17:19:56,122 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
    2024-11-29 17:19:56,253 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
    2024-11-29 17:19:56,494 INFO [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-3) AMQ151007: Resource adaptor started
    2024-11-29 17:19:56,495 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
    2024-11-29 17:19:56,503 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
    2024-11-29 17:19:56,504 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2024-11-29 17:20:10,187 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,203 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,203 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,204 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,204 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,205 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,205 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,210 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,210 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,211 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,211 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,213 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,213 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,269 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,270 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,270 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,274 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,279 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,281 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,281 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,282 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,282 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,284 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,284 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,304 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,306 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,306 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
    2024-11-29 17:20:10,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
    2024-11-29 17:20:10,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
    2024-11-29 17:20:10,410 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) 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.
    2024-11-29 17:20:10,411 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) 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.
    2024-11-29 17:20:11,077 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/searchIndexProcessorQueue‘ for Jakarta Enterprise Beans ‚SearchIndexProcessor‘ will be ignored.
    2024-11-29 17:20:11,079 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/outgoingMailProcessorQueue‘ for Jakarta Enterprise Beans ‚OutgoingMailProcessor‘ will be ignored.
    2024-11-29 17:20:11,255 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2024-11-29 17:20:11,257 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2024-11-29 17:20:12,603 INFO [org.jipijapa] (MSC service thread 1-8) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
    2024-11-29 17:20:12,603 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
    2024-11-29 17:20:12,930 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
    2024-11-29 17:20:13,620 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 6.0.23.Final
    2024-11-29 17:20:13,959 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000128: Infinispan version: Infinispan ‚Triskaidekaphobia‘ 13.0.10.Final
    2024-11-29 17:20:14,866 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
    2024-11-29 17:20:14,895 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
    2024-11-29 17:20:14,910 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
    2024-11-29 17:20:14,941 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) 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

    2024-11-29 17:20:14,983 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller‘
    2024-11-29 17:20:15,192 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-1) WFLYTRAC0001: Tracer initialized: NoopTracer
    2024-11-29 17:20:15,291 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
    2024-11-29 17:20:15,321 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,327 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,328 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,329 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,329 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,330 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,330 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,331 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,332 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,332 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,333 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,333 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,334 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,335 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,335 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,336 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,336 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,337 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,338 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,338 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,937 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
    2024-11-29 17:20:15,970 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,971 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,974 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,983 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,984 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,985 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,986 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,987 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:15,988 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,989 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.FormsServiceLocal
    java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
    java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
    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

    2024-11-29 17:20:15,990 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,990 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,991 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:15,992 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,993 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,994 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,995 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,995 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,996 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,997 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,998 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,999 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,000 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,001 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,002 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,002 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,003 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,004 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,005 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,006 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,007 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,007 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,008 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,009 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,010 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named ‚DrebisService‘ 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/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote

    2024-11-29 17:20:16,011 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,012 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,012 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,013 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,014 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,015 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,016 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,017 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,017 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,018 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,019 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,020 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,021 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,022 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,023 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,025 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,033 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,035 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,038 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,041 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,042 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,042 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,044 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,044 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,050 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,051 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,052 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,053 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,054 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:16,057 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.VoipServiceLocal
    java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
    java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
    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

    2024-11-29 17:20:16,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,065 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,066 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,067 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.MessagingServiceLocal
    java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
    java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
    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

    2024-11-29 17:20:16,068 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,069 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,070 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,074 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,071 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 85) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller‘
    2024-11-29 17:20:16,079 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,080 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,081 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,082 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,086 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,266 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-2) WFLYTRAC0001: Tracer initialized: NoopTracer
    2024-11-29 17:20:17,117 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-4) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,127 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-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@1cdda755, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,179 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:17,180 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 85) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:17,192 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024-11-29 17:20:17,203 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024-11-29 17:20:17,223 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-3) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,235 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-8) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,236 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) 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@76beb693, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,241 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-server-war.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@5506d5f2, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,259 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 88) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
    2024-11-29 17:20:17,281 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 88) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
    2024-11-29 17:20:17,298 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 82) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2024-11-29 17:20:17,298 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 85) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2024-11-29 17:20:17,423 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.1.9 (Final)
    2024-11-29 17:20:17,670 INFO [org.hibernate.Version] (ServerService Thread Pool — 85) HHH000412: Hibernate Core {5.3.28.Final}
    2024-11-29 17:20:17,673 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 85) HHH000206: hibernate.properties not found
    2024-11-29 17:20:17,836 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
    2024-11-29 17:20:19,270 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 85) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    2024-11-29 17:20:20,737 INFO [org.jipijapa] (MSC service thread 1-1) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
    2024-11-29 17:20:21,251 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 88) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:22,200 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0042: Started message driven bean ‚OutgoingMailProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024-11-29 17:20:22,200 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024-11-29 17:20:22,595 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:23,497 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 88) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024-11-29 17:20:23,498 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 82) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024-11-29 17:20:23,871 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 82) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024-11-29 17:20:23,867 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 88) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024-11-29 17:20:23,884 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 88) 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(Native Method)
    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:834)
    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

    2024-11-29 17:20:23,931 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) 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“: 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(Native Method)
    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:834)
    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

    2024-11-29 17:20:24,020 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\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“,
    „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]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“
    }}
    2024-11-29 17:20:24,357 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2024-11-29 17:20:24,371 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“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    WFLYCTL0448: 452 additional services are down due to their dependencies being missing or failed
    2024-11-29 17:20:24,557 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2024-11-29 17:20:24,581 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 54611ms – Started 3451 of 4111 services (473 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
    2024-11-29 17:20:24,594 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    2024-11-29 17:20:24,595 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

    29. November 2024 um 20:20 #6592
    Dersim Özdag
    Participant

    Hi, danke dir für deine Antwort!

    Der ganze Log ist hier:

    2024-11-29 17:19:32,521 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.2.Final
    2024-11-29 17:19:35,550 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.13.Final
    2024-11-29 17:19:35,571 INFO [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
    2024-11-29 17:19:35,943 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) starting
    2024-11-29 17:19:35,950 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:
    [Standalone] =
    awt.toolkit = sun.awt.X11.XToolkit
    file.encoding = UTF-8
    file.separator = /
    java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.print.PSPrinterJob
    java.class.path = /opt/jboss/wildfly/jboss-modules.jar
    java.class.version = 55.0
    java.home = /usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el7_8.x86_64
    java.io.tmpdir = /tmp
    java.library.path = /usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
    java.net.preferIPv4Stack = true
    java.runtime.name = OpenJDK Runtime Environment
    java.runtime.version = 11.0.8+10-LTS
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Oracle Corporation
    java.specification.version = 11
    java.util.logging.manager = org.jboss.logmanager.LogManager
    java.vendor = N/A
    java.vendor.url = https://openjdk.java.net/
    java.vendor.url.bug = https://bugreport.java.com/bugreport/
    java.vendor.version = 18.9
    java.version = 11.0.8
    java.version.date = 2020-07-14
    java.vm.compressedOopsMode = Zero based
    java.vm.info = mixed mode, sharing
    java.vm.name = OpenJDK 64-Bit Server VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Oracle Corporation
    java.vm.specification.version = 11
    java.vm.vendor = Oracle Corporation
    java.vm.version = 11.0.8+10-LTS
    javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
    jboss.bind.address = 0.0.0.0
    jboss.home.dir = /opt/jboss/wildfly
    jboss.host.name = 6531dceb8d04
    jboss.modules.dir = /opt/jboss/wildfly/modules
    jboss.modules.system.pkgs = org.jboss.byteman
    jboss.node.name = 6531dceb8d04
    jboss.qualified.host.name = 6531dceb8d04
    jboss.server.base.dir = /opt/jboss/wildfly/standalone
    jboss.server.config.dir = /opt/jboss/wildfly/standalone/configuration
    jboss.server.data.dir = /opt/jboss/wildfly/standalone/data
    jboss.server.deploy.dir = /opt/jboss/wildfly/standalone/data/content
    jboss.server.log.dir = /opt/jboss/wildfly/standalone/log
    jboss.server.name = 6531dceb8d04
    jboss.server.persist.config = true
    jboss.server.temp.dir = /opt/jboss/wildfly/standalone/tmp
    jdk.debug = release
    line.separator =

    logging.configuration = file:/opt/jboss/wildfly/standalone/configuration/logging.properties
    module.path = /opt/jboss/wildfly/modules
    org.jboss.boot.log.file = /opt/jboss/wildfly/standalone/log/server.log
    org.jboss.resolver.warning = true
    os.arch = amd64
    os.name = Linux
    os.version = 4.4.302+
    path.separator = :
    sun.arch.data.model = 64
    sun.boot.library.path = /usr/lib/jvm/java-11-openjdk-11.0.8.10-0.el7_8.x86_64/lib
    sun.cpu.endian = little
    sun.cpu.isalist =
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.command = /opt/jboss/wildfly/jboss-modules.jar -mp /opt/jboss/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/jboss/wildfly -Djboss.server.base.dir=/opt/jboss/wildfly/standalone -b 0.0.0.0
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = UTF-8
    sun.management.compiler = HotSpot 64-Bit Tiered Compilers
    sun.os.patch.level = unknown
    user.country = US
    user.dir = /opt/jboss
    user.home = /opt/jboss
    user.language = en
    user.name = jboss
    user.timezone = UTC
    2024-11-29 17:19:35,957 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -D[Standalone] -Xms256m -Xmx3072m -XX:MetaspaceSize=128M -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 -Dorg.jboss.boot.log.file=/opt/jboss/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/jboss/wildfly/standalone/configuration/logging.properties
    2024-11-29 17:19:39,366 INFO [org.wildfly.security] (ServerService Thread Pool — 26) ELY00001: WildFly Elytron version 1.19.1.Final
    2024-11-29 17:19:43,190 INFO [org.jboss.as.repository] (ServerService Thread Pool — 30) WFLYDR0001: Content added at location /opt/jboss/wildfly/standalone/data/content/ac/a4cd6c026bd3ed7420f5c05fae91b054af1946/content
    2024-11-29 17:19:43,272 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
    2024-11-29 17:19:43,345 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.8.7.Final
    2024-11-29 17:19:43,369 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.8.7.Final
    2024-11-29 17:19:43,489 INFO [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool — 53) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
    2024-11-29 17:19:43,517 INFO [org.wildfly.extension.health] (ServerService Thread Pool — 54) WFLYHEALTH0001: Activating Base Health Subsystem
    2024-11-29 17:19:43,516 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 55) WFLYCLINF0001: Activating Infinispan subsystem.
    2024-11-29 17:19:43,555 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool — 57) WFLYRS0016: RESTEasy version 4.7.7.Final
    2024-11-29 17:19:43,633 INFO [org.jboss.as.jsf] (ServerService Thread Pool — 62) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
    2024-11-29 17:19:43,590 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
    2024-11-29 17:19:43,662 INFO [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool — 66) WFLYCONF0001: Activating MicroProfile Config Subsystem
    2024-11-29 17:19:43,639 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
    2024-11-29 17:19:43,717 INFO [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool — 67) WFLYJWT0001: Activating MicroProfile JWT Subsystem
    2024-11-29 17:19:43,757 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.5.3.Final)
    2024-11-29 17:19:43,771 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.
    2024-11-29 17:19:43,793 INFO [org.wildfly.extension.metrics] (ServerService Thread Pool — 65) WFLYMETRICS0001: Activating Base Metrics Subsystem
    2024-11-29 17:19:43,794 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
    2024-11-29 17:19:43,801 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool — 68) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
    2024-11-29 17:19:43,876 INFO [org.jboss.as.naming] (ServerService Thread Pool — 69) WFLYNAM0001: Activating Naming Subsystem
    2024-11-29 17:19:43,887 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 78) WFLYWS0002: Activating WebServices Extension
    2024-11-29 17:19:43,937 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 45) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
    2024-11-29 17:19:43,943 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = mysql
    2024-11-29 17:19:43,993 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.25.Final
    2024-11-29 17:19:44,506 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
    2024-11-29 17:19:44,501 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
    2024-11-29 17:19:44,774 WARN [org.wildfly.extension.elytron] (MSC service thread 1-5) WFLYELY00023: KeyStore file ‚/opt/jboss/wildfly/standalone/configuration/application.keystore‘ does not exist. Used blank.
    2024-11-29 17:19:44,921 WARN [org.wildfly.extension.elytron] (MSC service thread 1-7) WFLYELY01084: KeyStore /opt/jboss/wildfly/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
    2024-11-29 17:19:44,964 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.2.19.Final starting
    2024-11-29 17:19:45,190 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.
    2024-11-29 17:19:45,215 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
    2024-11-29 17:19:45,629 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool — 77) WFLYUT0014: Creating file handler for path ‚/opt/jboss/wildfly/welcome-content‘ with options [directory-listing: ‚false‘, follow-symlink: ‚false‘, case-sensitive: ‚true‘, safe-symlink-paths: ‚[]‘]
    2024-11-29 17:19:45,649 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
    2024-11-29 17:19:45,668 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) Queuing requests.
    2024-11-29 17:19:45,674 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
    2024-11-29 17:19:45,881 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080
    2024-11-29 17:19:46,053 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
    2024-11-29 17:19:46,484 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8443
    2024-11-29 17:19:46,824 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jlawyerdb]
    2024-11-29 17:19:46,824 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    2024-11-29 17:19:47,313 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) 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.
    2024-11-29 17:19:47,323 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
    2024-11-29 17:19:47,338 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
    2024-11-29 17:19:47,424 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“)
    2024-11-29 17:19:47,732 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.5.0.Final (Apache CXF 3.4.10)
    2024-11-29 17:19:47,853 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/jboss/wildfly/standalone/data/activemq/journal,bindingsDirectory=/opt/jboss/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/opt/jboss/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/opt/jboss/wildfly/standalone/data/activemq/paging)
    2024-11-29 17:19:48,003 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221013: Using NIO Journal
    2024-11-29 17:19:49,019 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
    2024-11-29 17:19:49,022 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
    2024-11-29 17:19:49,024 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
    2024-11-29 17:19:49,025 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
    2024-11-29 17:19:49,462 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221034: Waiting indefinitely to obtain live lock
    2024-11-29 17:19:49,463 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221035: Live Server Obtained live lock
    2024-11-29 17:19:52,517 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
    2024-11-29 17:19:52,944 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
    2024-11-29 17:19:52,949 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.searchIndexProcessorQueue on address jms.queue.searchIndexProcessorQueue
    2024-11-29 17:19:52,955 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221003: Deploying ANYCAST queue jms.queue.outgoingMailProcessorQueue on address jms.queue.outgoingMailProcessorQueue
    2024-11-29 17:19:54,307 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2024-11-29 17:19:54,312 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
    2024-11-29 17:19:54,313 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
    2024-11-29 17:19:54,307 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
    2024-11-29 17:19:56,006 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221007: Server is now live
    2024-11-29 17:19:56,007 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool — 80) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.19.1 [default, nodeID=225a1f31-ae76-11ef-801b-0242ac160003]
    2024-11-29 17:19:56,057 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool — 84) AMQ122005: Invalid „host“ value „0.0.0.0“ detected for „http-connector“ connector. Switching to „6531dceb8d04“. If this new address is incorrect please manually configure the connector to use the proper one.
    2024-11-29 17:19:56,120 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    2024-11-29 17:19:56,122 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool — 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
    2024-11-29 17:19:56,253 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
    2024-11-29 17:19:56,494 INFO [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-3) AMQ151007: Resource adaptor started
    2024-11-29 17:19:56,495 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
    2024-11-29 17:19:56,503 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
    2024-11-29 17:19:56,504 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
    2024-11-29 17:20:10,187 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,203 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,203 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,204 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,204 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,205 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,205 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,206 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,207 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,209 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,210 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,210 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,211 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,211 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,213 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,213 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,269 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,270 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,270 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,271 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,274 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,279 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,280 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,281 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,281 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,282 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,282 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,283 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,284 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,284 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,285 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,286 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,287 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,304 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,305 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,306 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,306 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-war.war“)
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-entities.jar“)
    2024-11-29 17:20:10,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-io.war“)
    2024-11-29 17:20:10,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-ejb.jar“)
    2024-11-29 17:20:10,354 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: „j-lawyer-server-io.war“)
    2024-11-29 17:20:10,410 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) 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.
    2024-11-29 17:20:10,411 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) 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.
    2024-11-29 17:20:11,077 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/searchIndexProcessorQueue‘ for Jakarta Enterprise Beans ‚SearchIndexProcessor‘ will be ignored.
    2024-11-29 17:20:11,079 WARN [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0525: The ‚mappedName‘ in Jakarta Enterprise Beans annotations is not supported. Value of ‚queue/outgoingMailProcessorQueue‘ for Jakarta Enterprise Beans ‚OutgoingMailProcessor‘ will be ignored.
    2024-11-29 17:20:11,255 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2024-11-29 17:20:11,257 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Read persistence.xml for j-lawyer-server-ejbPU
    2024-11-29 17:20:12,603 INFO [org.jipijapa] (MSC service thread 1-8) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU
    2024-11-29 17:20:12,603 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
    2024-11-29 17:20:12,930 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server.ear
    2024-11-29 17:20:13,620 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 6.0.23.Final
    2024-11-29 17:20:13,959 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000128: Infinispan version: Infinispan ‚Triskaidekaphobia‘ 13.0.10.Final
    2024-11-29 17:20:14,866 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment j-lawyer-server-io.war
    2024-11-29 17:20:14,895 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment j-lawyer-server-entities.jar
    2024-11-29 17:20:14,910 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment j-lawyer-server-war.war
    2024-11-29 17:20:14,941 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) 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

    2024-11-29 17:20:14,983 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 82) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller‘
    2024-11-29 17:20:15,192 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-1) WFLYTRAC0001: Tracer initialized: NoopTracer
    2024-11-29 17:20:15,291 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment j-lawyer-io.war
    2024-11-29 17:20:15,321 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,327 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,328 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,329 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,329 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,330 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,330 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,331 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,332 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,332 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,333 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,333 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,334 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,335 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,335 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,336 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,336 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,337 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,338 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,338 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-4) 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

    2024-11-29 17:20:15,937 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment j-lawyer-server-ejb.jar
    2024-11-29 17:20:15,970 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,971 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,974 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,983 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,984 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,985 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,986 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,987 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:15,988 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,989 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.FormsServiceLocal
    java:app/j-lawyer-server-ejb/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
    java:module/FormsService!com.jdimension.jlawyer.services.FormsServiceLocal
    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

    2024-11-29 17:20:15,990 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,990 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,991 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:15,992 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,993 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,994 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,995 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,995 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,996 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,997 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,998 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:15,999 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,000 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,001 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,002 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,002 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,003 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,004 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,005 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,006 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,007 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,007 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,008 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,009 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,010 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named ‚DrebisService‘ 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/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceLocal
    java:global/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:app/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:module/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    java:jboss/exported/j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote
    ejb:j-lawyer-server/j-lawyer-server-ejb/DrebisService!com.jdimension.jlawyer.services.DrebisServiceRemote

    2024-11-29 17:20:16,011 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,012 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,012 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,013 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,014 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,015 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,016 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,017 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,017 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,018 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,019 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,020 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,021 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,022 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,023 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,025 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,033 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,035 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,038 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,041 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,042 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,042 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,044 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,044 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,050 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,051 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,052 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,053 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,054 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.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
    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

    2024-11-29 17:20:16,057 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.VoipServiceLocal
    java:app/j-lawyer-server-ejb/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
    java:module/VoipService!com.jdimension.jlawyer.services.VoipServiceLocal
    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

    2024-11-29 17:20:16,059 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,060 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,065 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,066 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,067 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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.MessagingServiceLocal
    java:app/j-lawyer-server-ejb/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
    java:module/MessagingService!com.jdimension.jlawyer.services.MessagingServiceLocal
    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

    2024-11-29 17:20:16,068 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,069 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,070 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,074 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,071 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 85) ISPN000556: Starting user marshaller ‚org.wildfly.clustering.infinispan.spi.marshalling.InfinispanProtoStreamMarshaller‘
    2024-11-29 17:20:16,079 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,080 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,081 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,082 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,086 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) 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

    2024-11-29 17:20:16,266 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-2) WFLYTRAC0001: Tracer initialized: NoopTracer
    2024-11-29 17:20:17,117 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-4) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,127 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-io.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@1cdda755, closeEnqueueTimeout=1000), sampler=ConstSampler(decision=true, tags={sampler.type=const, sampler.param=true}), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,179 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:17,180 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 85) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:17,192 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024-11-29 17:20:17,203 INFO [org.infinispan.CONFIG] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
    2024-11-29 17:20:17,223 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-3) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,235 INFO [io.jaegertracing.internal.JaegerTracer] (MSC service thread 1-8) No shutdown hook registered: Please call close() manually on application shutdown.
    2024-11-29 17:20:17,236 INFO [org.wildfly.microprofile.opentracing.smallrye] (MSC service thread 1-8) 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@76beb693, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,241 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-server-war.war, reporter=RemoteReporter(sender=org.wildfly.extension.microprofile.opentracing.spi.sender.WildFlySender@5506d5f2, closeEnqueueTimeout=1000), sampler=RemoteControlledSampler(maxOperations=2000, manager=HttpSamplingManager(hostPort=localhost:5778), sampler=ProbabilisticSampler(tags={sampler.type=probabilistic, sampler.param=0.001})), tags={hostname=6531dceb8d04, jaeger.version=Java-1.6.0, ip=172.22.0.3}, zipkinSharedRpcSpan=false, expandExceptionLogs=false, useTraceId128Bit=false)
    2024-11-29 17:20:17,259 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool — 88) ISPN000025: wakeUpInterval is <= 0, not starting expired purge thread
    2024-11-29 17:20:17,281 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 88) WFLYCLINF0002: Started http-remoting-connector cache from ejb container
    2024-11-29 17:20:17,298 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 82) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2024-11-29 17:20:17,298 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool — 85) HHH000204: Processing PersistenceUnitInfo [
    name: j-lawyer-server-ejbPU
    …]
    2024-11-29 17:20:17,423 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 3.1.9 (Final)
    2024-11-29 17:20:17,670 INFO [org.hibernate.Version] (ServerService Thread Pool — 85) HHH000412: Hibernate Core {5.3.28.Final}
    2024-11-29 17:20:17,673 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool — 85) HHH000206: hibernate.properties not found
    2024-11-29 17:20:17,836 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
    2024-11-29 17:20:19,270 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool — 85) HCANN000001: Hibernate Commons Annotations {5.0.5.Final}
    2024-11-29 17:20:20,737 INFO [org.jipijapa] (MSC service thread 1-1) JIPIORMV53020253: Second level cache enabled for j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU
    2024-11-29 17:20:21,251 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 88) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:22,200 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0042: Started message driven bean ‚OutgoingMailProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024-11-29 17:20:22,200 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0042: Started message driven bean ‚SearchIndexProcessor‘ with ‚activemq-ra.rar‘ resource adapter
    2024-11-29 17:20:22,595 INFO [org.jboss.as.jpa] (ServerService Thread Pool — 82) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service ‚j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU‘
    2024-11-29 17:20:23,497 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 88) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024-11-29 17:20:23,498 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool — 82) HHH000400: Using dialect: org.hibernate.dialect.MySQL8Dialect
    2024-11-29 17:20:23,871 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 82) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024-11-29 17:20:23,867 WARN [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool — 88) HHH000341: Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘
    2024-11-29 17:20:23,884 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 88) 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(Native Method)
    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:834)
    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

    2024-11-29 17:20:23,931 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) 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“: 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(Native Method)
    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:834)
    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

    2024-11-29 17:20:24,020 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\““ => „org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“,
    „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]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when ‚hibernate.dialect‘ not set“
    }}
    2024-11-29 17:20:24,357 INFO [org.jboss.as.server] (ServerService Thread Pool — 46) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2024-11-29 17:20:24,371 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“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    WFLYCTL0448: 452 additional services are down due to their dependencies being missing or failed
    2024-11-29 17:20:24,557 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2024-11-29 17:20:24,581 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 26.1.3.Final (WildFly Core 18.1.2.Final) started (with errors) in 54611ms – Started 3451 of 4111 services (473 services failed or missing dependencies, 383 services are lazy, passive or on-demand) – Server configuration file in use: standalone.xml
    2024-11-29 17:20:24,594 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    2024-11-29 17:20:24,595 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

    29. November 2024 um 20:21 #6598
    j-lawyer.org
    Keymaster

    Danke! So richtig schlau werde ich aus dem Log nicht. Wird nur der Server-Container gestartet, oder nutzt Du compose? Es gehören ja ein Datenbankcontainer und ein j-lawyer-Container zusammen.

    1. Dezember 2024 um 15:27 #6599
    Dersim Özdag
    Participant

    Genau, ich hab mit docker compose das ganze gestartet. Habe es zuerst mit der mitgelieferten Datenbank ausprobiert, aber da kam der gleiche Fehler. Habe dann selbst eine mariadb als Container genommen und mit dem SQL aus dem github die Datenbank eingerichtet. Auch hier das Ergebnis wie oben. Ich werde leider auch nicht schlau draus.

    1. Dezember 2024 um 23:32 #6602
    j-lawyer.org
    Keymaster

    Das Log vom 29.11. um 20:20 hat folgenden Eintrag:

    Could not obtain connection metadata : Unknown column ‚RESERVED‘ in ‚WHERE‘

    D.h. hier funktioniert die Verbindung zur Datenbank, Anwendung und Datenbank verstehen sich aber nicht, weil eine nicht unterstützte Version verwendet wird. Hier wäre zu prüfen, welche MySQL / MariaDB-Version verwendet wurde.

  • Autor
    Beiträge
7 Beiträge anzeigen - 1 bis 7 (von insgesamt 7)
  • Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.