登录
当前位置： 首页 > 知识库问答 >
问题：

jboss。部署。单元“测试基地。战争”。解析：WFLYSRV0153：无法处理部署“testit base.war”的阶段解析

燕扬
2023-03-14

我们计划将应用程序从Jboss EAP 6.4迁移到WILDFLY 19，并在其中部署war文件时面临以下错误。

    Manifest-Version: 1.0
    Built-By: jenkins
    Created-By: Apache Maven 3.3.9
    Build-Jdk: 1.8.0_151

平台：Wildfly 19

服务器中使用的JDK版本

    openjdk version "1.8.0_282"
    OpenJDK Runtime Environment (build 1.8.0_282-b08)
    OpenJDK 64-Bit Server VM (build 25.282-b08, mixed mode)

这会导致兼容性问题吗？同样的战争部署在JBOSS EAP 6.4和JDK 1.8中。0_151安装在服务器上。有人能帮我理解这个问题吗？提前感谢

    2021-03-03 19:00:58,126 INFO  [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
    2021-03-03 19:00:58,180 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "testit-base.war" (runtime-name: "testit-base.war")
    2021-03-03 19:00:58,184 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "externalapi.war" (runtime-name: "externalapi.war")
    2021-03-03 19:00:58,185 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "wmq.jmsra.rar" (runtime-name: "wmq.jmsra.rar")
    2021-03-03 19:00:58,234 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/server/deployments
    2021-03-03 19:00:59,051 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
    2021-03-03 19:00:59,253 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
    2021-03-03 19:00:59,875 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.4.1.Final (Apache CXF 3.3.5)
    2021-03-03 19:01:00,359 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
    2021-03-03 19:01:01,132 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry connector.jar in /content/wmq.jmsra.rar/com.ibm.mq.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,180 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jta.jar in /content/wmq.jmsra.rar/com.ibm.mq.jmqi.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,183 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry ldap.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,184 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jndi.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,184 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry fscontext.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,184 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry providerutil.jar in /content/wmq.jmsra.rar/com.ibm.mqjms.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,203 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jms.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.jms.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,206 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry rmm.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,207 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry CL3Export.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:01,207 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry CL3Nonexport.jar in /content/wmq.jmsra.rar/com.ibm.msg.client.wmq.v6.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:04,020 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020001: Required license terms for file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/
    2021-03-03 19:01:04,953 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment externalapi.war
    2021-03-03 19:01:05,350 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.18.Final
    2021-03-03 19:01:05,628 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 6.0.18.Final
    2021-03-03 19:01:05,859 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /content/testit-base.war/WEB-INF/lib/liquibase-core-3.5.3.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:05,862 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xercesImpl.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:05,862 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xml-apis.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:05,863 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry serializer.jar in /content/testit-base.war/WEB-INF/lib/xalan-2.7.0.jar  does not point to a valid jar for a Class-Path reference.
    2021-03-03 19:01:06,129 ERROR [stderr] (MSC service thread 1-3) Could not initialize log file, java.nio.file.AccessDeniedException: mqjms.log.0.lck
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) March 3, 2021 7:01:06 PM CET[MSC service thread 1-3] ResourceAdapterImpl
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) WMQ messaging : '7.5.0.6-p750-006-160226'.
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) EXPLANATION:
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) null
    2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
    2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) ACTION:
    2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) null
    2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) --------------------------------------------------------------------
    2021-03-03 19:01:06,433 WARN  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020017: Invalid archive: file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/
    2021-03-03 19:01:06,499 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."testit-base.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."testit-base.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "testit-base.war"
            at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
            at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
            at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
            at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
            at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
            at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
            at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
            at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363)
            at java.lang.Thread.run(Thread.java:748)
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
            at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:663)
            at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:248)
            at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:156)
            at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:83)
            at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:50)
            at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
            at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
            ... 8 more
    
    2021-03-03 19:01:07,346 WARN  [org.jboss.as.jaxrs] (MSC service thread 1-4) WFLYRS0018: Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment. Consider setting the 'resteasy.preferJacksonOverJsonB' property to 'false' to restore JSON-B.
    2021-03-03 19:01:07,455 INFO  [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 3.1.3 (Final)
    2021-03-03 19:01:07,762 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 67) WFLYCLINF0002: Started client-mappings cache from ejb container
    2021-03-03 19:01:09,806 INFO  [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 67) RESTEASY002225: Deploying javax.ws.rs.core.Application: class ExternalApiApplication
    2021-03-03 19:01:09,808 WARN  [org.jboss.as.weld] (ServerService Thread Pool -- 67) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi, org.jboss.weld.api]
    2021-03-03 19:01:09,966 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0021: Registered web context: '/externalapi' for server 'default-server'
    2021-03-03 19:01:09,978 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testit-base.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"testit-base.war\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of deployment \"testit-base.war\"
        Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
    2021-03-03 19:01:09,996 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "wmq.jmsra.rar" (runtime-name : "wmq.jmsra.rar")
    2021-03-03 19:01:09,996 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "externalapi.war" (runtime-name : "externalapi.war")
    2021-03-03 19:01:09,996 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "testit-base.war" (runtime-name : "testit-base.war")
    2021-03-03 19:01:09,998 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    WFLYCTL0186:   Services which failed to start:      service jboss.deployment.unit."testit-base.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "testit-base.war"
    
    2021-03-03 19:01:10,146 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
    2021-03-03 19:01:10,149 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
    2021-03-03 19:01:10,149 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
    2021-03-03 19:01:10,149 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 19.0.0.Final (WildFly Core 11.0.0.Final) started (with errors) in 28607ms - Started 487 of 679 services (1 services failed or missing dependencies, 338 services are lazy, passive or on-demand)

资源适配器设置如下，

    <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
        <resource-adapters>
            <resource-adapter id="wmq.jmsra.rar">
                <archive>
                    wmq.jmsra.rar
                </archive>
                <transaction-support>NoTransaction</transaction-support>
                <connection-definitions>
                    <connection-definition class-name="com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl" jndi-name="java:jboss/WMQConnectionFactory" pool-name="WMQConnectionFactory">
                        <config-property name="channel">
                            CL.SC1023AC.TIMS
                        </config-property>
                        <config-property name="hostName">
                            sc1023ac.domain.com
                        </config-property>
                        <config-property name="transportType">
                            Client
                        </config-property>
                        <config-property name="queueManager">
                            SC1023AC
                        </config-property>
                        <config-property name="port">
                            49400
                        </config-property>
                    </connection-definition>
                </connection-definitions>
                <admin-objects>
                    <admin-object class-name="com.ibm.mq.connector.outbound.MQQueueProxy" jndi-name="java:jboss/queue/PurchaseOrderExportQueue" pool-name="purchaseOrderExport">
                        <config-property name="baseQueueName">
                            RQ.SCCO4234
                        </config-property>
                    </admin-object>>
                </admin-objects>
            </resource-adapter>
        </resource-adapters>
    </subsystem>


    <subsystem xmlns="urn:jboss:domain:ejb3:6.0">
        <session-bean>
            <stateless>
                <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
            </stateless>
            <stateful default-access-timeout="5000" cache-ref="distributable" passivation-disabled-cache-ref="simple"/>
            <singleton default-access-timeout="5000"/>
        </session-bean>
        <mdb>
            <resource-adapter-ref resource-adapter-name="${ejb.resource-adapter-name:wmq.jmsra.rar}"/>
            <!--resource-adapter-ref resource-adapter-name="wmq.jmsra.rar"/-->
            <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
        </mdb>

共有2个答案

匡玉堂
2023-03-14

看起来您正在尝试部署自己的JMS服务，而不是使用Artemis，但仍有人在尝试使用默认值，因为我假设您使用的是独立的而不是独立的完整配置文件，而默认值可能不存在

艾自强
2023-03-14

您的WMQ资源适配器无法正常工作，如中所述：

2021-03-03 19:01:06,129 ERROR [stderr] (MSC service thread 1-3) Could not initialize log file, java.nio.file.AccessDeniedException: mqjms.log.0.lck
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) March 3, 2021 7:01:06 PM CET[MSC service thread 1-3] ResourceAdapterImpl
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) WMQ messaging : '7.5.0.6-p750-006-160226'.
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) EXPLANATION:
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,165 ERROR [stderr] (MSC service thread 1-3)
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) ACTION:
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) null
2021-03-03 19:01:06,166 ERROR [stderr] (MSC service thread 1-3) --------------------------------------------------------------------
2021-03-03 19:01:06,433 WARN  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-3) IJ020017: Invalid archive: file:/opt/wildfly/server/tmp/vfs/temp/temp9866aa9ab5895a5a/content-7c3c685b4673a9c7/contents/

这使得EJB失败

 类似资料：
  • 无法处理部署的阶段结构

    我读过其他的题目，但我不太明白这一点。我有一个使用log4j的EJB模块。我想将该EJB打包到一个JAR文件中，并放在web项目的WEB-INF/lib路径中。web项目有一个从EJB执行函数的servlet，仅此而已。但添加器似乎不起作用,因为文件已创建但未写入。 顺便说一下，我使用的是JBoss7.1.1。

  • 无法从Eclipse Juno向jboss 7部署战争

    我有一个关于部署我的应用程序的问题。向jboss7开战。 我的测试环境： OS:Ubuntu12.10 Eclipse:Eclipse Juno（Eclipse 4.2） JBoss:JBoss AS 7.1.1最终版 JBoss工具：JBoss工具4 JDK版本：JDK 7 如果使用默认服务器配置，当我启动服务器时，它将成功启动，我的应用程序也将启动。战争可以正常进行 请参阅此屏幕截图 我在服务

  • Maven RESTEasy jboss。战争部署失败

    我正在自学RESTEasy，它将与Maven一起构建，并部署在jBoss中，然后再与Jenkins集成。 目前，我已经创建了一个非常简单的RESTEasy网络服务，并用maven构建了它。我有一个文件和爆炸的战争（这是我相信的战争的解压文件夹），一个与和文件夹在我的netbean里面项目目标文件夹。 我已经安装了JBoss7。x、 并成功启动并验证了它在我的

  • 部署像tomcat7这样的JBoss中的战争

    我对tomcat很熟悉。我们使用服务器在eclipse中创建一个项目。xml和一些。配置文件。我们生成。战争档案。我们将这个war文件复制到我们的生产服务器webapps文件夹中，然后在webapps文件夹中生成一个同名的新文件夹。我们在那里更改生产服务器配置（在文件夹中）。 我们的一个客户想在他的JBoss服务器上部署war。我们试图通过将war复制到/standalone/deployment

  • jboss eap-6.1无法处理部署POST_MODULE\"education.war\"

    使用了hibernate、spring mvc。文件夹： 网状物xml 主上下文文件 根上下文。xml 在我成功编译并运行这个应用程序之前，先添加hibernate代码和这个xml文件，然后遇到错误。 错误代码 16:40:50,403错误[org.jboss.as.server]（管理-处理程序-线程-12）JBAS015870：部署education.war的部署回滚了以下失败消息：{"JBA

  • 无法处理部署\“report.jar\”的POST_MODULE阶段，原因为：java.lang.NullPointerException

    我试图在Jboss fsw中部署jar文件，但是部署失败，出现以下消息 POST_MODULE:org.jboss.msc.service.startService在服务jboss.deployment.unit中出现异常。“report.jar”。POST_MODULE:JBAS018733:在org.jboss.as.server.deployment.deploymentunitphases

相关问答

jboss eap-6.1无法处理部署POST_MODULE\"education.war\"无法处理部署\“report.jar\”的POST_MODULE阶段，原因为：java.lang.NullPointerExceptionIntelliJ Tomcat推迟战争部署码头部署战争文件失败SpringBootServletializer在战争部署中的重要性

相关文章

详解ASP.NET Core Docker部署spring boot测试打包部署的方法docker+gitlab+gitlab-runner部署详解Tomcat和Weblogic部署纯html文件过程解析浅析docker-compose部署mysql无法访问的问题

相关阅读

部署构件到Nexus毫末算法部署岗面经数据处理面试题与解析1单元测试PyTorch：RNN，TensorBoard，部署PyTorch，数据增强

相关工具

简单xml解析demo测试用例注解testcase-annotationini格式解析解析html网页的数据理解机

相关文档

部署 kubernetes 集群Laravel 开发环境部署 6.xVue 单元测试策略与实践30 秒就能理解的 JavaScript 代码片段深入解析 Go
快捷导航： 新手教程 算法原理 架构设计 Java进阶 数据库进阶 大厂专栏 面试经验 编程笔记 编程问答 所有专题 文档资料 工具软件 电子书籍 小牛导航
在线工具： 房贷计算器 个税计算器 Linux命令查询 Json格式化 正则表达式 颜色转换 AES加解密 SHA1加密 MD5加密 毒鸡汤 字数统计 随机密码生成 进制转换 Base64编解码 励志句子
Copyright © 2019-2024 小牛知识库@xnip.cn. All Rights Reserved.