jboss 相关问题

我导出了我想要部署的战争档案。我在内部使用 JPA，带有持久性单元。我在我的standalone.xml 文件中添加了数据源标签，如下所示：我导出了我想要部署的战争档案。我在里面使用 JPA，带有持久性单元。我在我的 standalone.xml 文件中添加了数据源标签，如下所示： <datasource jndi-name="java:jboss/datasources/bdd_colis" pool-name="bdd_colis_pool" enabled="true" use-java-context="true"> <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers> 当我启动服务器时，它会返回标题中指定的错误，并显示以下输出： ... 23:20:28,069 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting 23:20:28,134 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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. 23:20:28,134 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) 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. 23:20:28,229 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080 23:20:28,387 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] 23:20:28,388 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/bdd_colis] 23:20:28,633 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore /home/calliste/wildfly-10.1.0.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost 23:20:28,638 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "dataRecovery-0.0.1-SNAPSHOT.war" (runtime-name: "dataRecovery-0.0.1-SNAPSHOT.war") 23:20:28,655 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory /home/calliste/wildfly-10.1.0.Final/standalone/deployments 23:20:28,869 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443 23:20:28,897 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final 23:20:28,936 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:28,937 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 61) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:28,938 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 61) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:28,939 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:28,938 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 62) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:28,940 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 62) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:29,065 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6) 23:20:31,155 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for bdd_colis 23:20:31,410 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment dataRecovery-0.0.1-SNAPSHOT.war 23:20:31,463 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.2.4.Final 23:20:31,541 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'ColisDao' in deployment unit 'deployment "dataRecovery-0.0.1-SNAPSHOT.war"' are as follows: java:global/dataRecovery-0.0.1-SNAPSHOT/ColisDao!dataRecovery.ColisDao java:app/dataRecovery-0.0.1-SNAPSHOT/ColisDao!dataRecovery.ColisDao java:module/ColisDao!dataRecovery.ColisDao java:global/dataRecovery-0.0.1-SNAPSHOT/ColisDao java:app/dataRecovery-0.0.1-SNAPSHOT/ColisDao java:module/ColisDao 23:20:31,696 WARN [org.jboss.as.ee] (MSC service thread 1-3) WFLYEE0007: Not installing optional component org.apache.cxf.transport.servlet.CXFServlet due to an exception (enable DEBUG log level to see the cause) 23:20:31,703 WARN [org.jboss.as.ee] (MSC service thread 1-3) WFLYEE0007: Not installing optional component org.springframework.web.context.ContextLoaderListener due to an exception (enable DEBUG log level to see the cause) 23:20:31,741 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:31,742 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 64) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 23:20:31,889 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.5 (Final) 23:20:32,320 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 64) WFLYCLINF0002: Started client-mappings cache from ejb container 23:20:32,392 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "dataRecovery-0.0.1-SNAPSHOT.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jdbc.DataSource"], "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.persistenceunit.\"dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis\" is missing [jboss.naming.context.java.jdbc.DataSource]", "jboss.persistenceunit.\"dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jdbc.DataSource]" ] } 23:20:32,433 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "dataRecovery-0.0.1-SNAPSHOT.war" (runtime-name : "dataRecovery-0.0.1-SNAPSHOT.war") 23:20:32,434 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.naming.context.java.jdbc.DataSource (missing) dependents: [service jboss.persistenceunit."dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis".__FIRST_PHASE__, service jboss.persistenceunit."dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis"] 23:20:32,591 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management 23:20:32,591 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 23:20:32,591 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 7689ms - Started 438 of 700 services (25 services failed or missing dependencies, 405 services are lazy, passive or on-demand) 23:20:32,673 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 7) WFLYCLINF0003: Stopped client-mappings cache from ejb container 23:20:32,688 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment dataRecovery-0.0.1-SNAPSHOT.war (runtime-name: dataRecovery-0.0.1-SNAPSHOT.war) in 66ms 23:20:32,763 WARN [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0357: Notification of type deployment-undeployed is not described for the resource at the address [] 23:20:32,779 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /home/calliste/wildfly-10.1.0.Final/standalone/data/content/77/1bd22de0dbe2bbece064a17d0127813d1d7a66/content 23:20:32,780 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "dataRecovery-0.0.1-SNAPSHOT.war" (runtime-name: "dataRecovery-0.0.1-SNAPSHOT.war") 23:20:32,783 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.WeldInstantiator, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".CdiValidatorFactoryService, WFLYCTL0208: ... and 7 more ] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.WeldInstantiator, service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", WFLYCTL0208: ... and 8 more ] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".beanmanager (missing) dependents: [service jboss.persistenceunit."dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis"] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".moduleDeploymentRuntimeInformationStart, service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.VIEW."dataRecovery.ColisDao".LOCAL (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.WeldInstantiator] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."com.sun.faces.config.ConfigureListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".JndiBindingsService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START, WFLYCTL0208: ... and 5 more ] service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START] service jboss.naming.context.java.app."dataRecovery-0.0.1-SNAPSHOT".env (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".BeanManager (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".DefaultContextService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".DefaultDataSource (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".DefaultManagedExecutorService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".DefaultManagedScheduledExecutorService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".DefaultManagedThreadFactory (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".EJBContext (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".TimerService (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".TransactionSynchronizationRegistry (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".UserTransaction (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".env (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.naming.context.java.module."dataRecovery-0.0.1-SNAPSHOT"."dataRecovery-0.0.1-SNAPSHOT".env."dataRecovery.ColisDao".em (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".jndiDependencyService] service jboss.persistenceunit."dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis" (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component."javax.faces.webapp.FacetTag".START, service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT", service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".component.ColisDao.START, WFLYCTL0208: ... and 7 more ] service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT" (missing) dependents: [service jboss.deployment.unit."dataRecovery-0.0.1-SNAPSHOT.war".deploymentCompleteService] service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT"] service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService] service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService] service org.wildfly.request-controller.control-point."dataRecovery-0.0.1-SNAPSHOT.war".undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host."/dataRecovery-0.0.1-SNAPSHOT".UndertowDeploymentInfoService] 我想解决这种依赖性。有什么建议？我没有足够的积分将其添加为评论，因此如果它的答案更适合作为评论，请转换它... 使用 CLI (bin/jboss-cli.sh)，不再推荐编辑 XML 文件我几乎可以肯定，您尝试部署的应用程序中存在错误：我使用了 CLI 命令 /subsystem=datasources/data-source=bdd_colis:add(jndi-name="java:jboss/datasources/bdd_colis",enabled=true, use-java-context=true,connection-url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE", driver-name=h2, user-name=sa, password=sa 并在standalone.xml中取得了相同的结果： <datasource jndi-name="java:jboss/datasources/bdd_colis" pool-name="bdd_colis" enabled="true" use-java-context="true"> <connection-url> jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE </connection-url> <driver>h2</driver> <security> <user-name>sa</user-name> <password>sa</password> </security> </datasource> 您看到的依赖项错误是由于缺少服务而存在的。我猜测，您的应用程序中的某处定义了名为 java.jdbc.DataSource 的资源，该资源应该在服务器上可用，但它不是——因此出现命名上下文错误： 23:20:32,392 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "dataRecovery-0.0.1-SNAPSHOT.war")]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jdbc.DataSource"], "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.persistenceunit.\"dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis\" is missing [jboss.naming.context.java.jdbc.DataSource]", "jboss.persistenceunit.\"dataRecovery-0.0.1-SNAPSHOT.war#bdd_colis\".__FIRST_PHASE__ is missing [jboss.naming.context.java.jdbc.DataSource]" ] } 尝试准备导致此问题的最少代码片段，您应该解决它 - 或将其发布在这里。这将解决问题在 web.xml 中 <resource-ref> <res-ref-name>java:jboss/datasources/bdd_colis</res-ref-name> <res-type><data_soruce_for_h2></res-type> <res-auth>Container</res-auth> </resource-ref>

java jpa jboss wildfly

回答 2 投票 0

如何解决AspectJ LTW设置中的错误“找不到指定的方面'AspectLogger'”？

我正在尝试设置 AspectJ 加载时编织（LTW）来记录我的 Java Web 应用程序中的方法执行时间。它是一个使用 Servlet、jsp（未使用 Spring）编写并部署在 jBoss 上的 Web 应用程序...

java jboss aop aspectj instrumentation

回答 1 投票 0

错误：在 JBoss EAP 8.0 上部署的 Spring Boot 3.3 WAR 中“在设置 'java.util.logging.manager' 系统属性之前访问了 LogManager”

我正在使用 Spring Boot 3.3.2 开发一个 REST 应用程序，打包为 WAR，并将其部署在 JBoss EAP 8.0 上。我的应用程序使用 Java 21。应用程序部署成功，但我遇到了

java spring spring-boot maven jboss

回答 1 投票 0

如何在 jboss 7.4.17 容器上安装 appdynamics 代理...？

今天我开始了一个玩jboss的任务，我拉了最新的容器并尝试让appdynamics正确安装...... registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rh...

jboss openshift appdynamics

回答 1 投票 0

RedHat Maven 存储库中工件的版本有何含义？

RedHat Maven 存储库包含许多流行项目的二进制文件，这些项目也在 Maven Central 中。然而，版本并不完全匹配，并且在许多情况下 RH 存储库中有多个二进制文件

maven jboss redhat maven-central binary-reproducibility

回答 1 投票 0

JBoss 8 与 java 8 兼容吗？

我正在尝试将ear应用程序从JBoss 7.1 eap迁移到jboss 8，它与java 8兼容吗？我收到以下错误错误：发生 JNI 错误，请检查您的安装并...

java jboss

回答 1 投票 0

如何访问keycloak h2数据库的users表

我有一个本地钥匙斗篷设置。我想直接从 keycloak 的 h2 数据库查询用户数据。我已经使用以下命令打开了 keycloak h2 控制台 java -cp "C:\Users\kow...

database jboss keycloak h2 idp

回答 0 投票 0

jboss 相关问题

最新问题