操作“读取属性"JBoss EAP 7 启动期间失败 [英] Operation "read-attribute" failed during JBoss EAP 7 startup

查看:37
本文介绍了操作“读取属性"JBoss EAP 7 启动期间失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在 J​​Boss EAP 7 上以 SSL 模式部署了我的应用程序.
我的应用程序已部署并成功运行,但在启动期间,每次服务器启动并同时部署 WAR 时,我都会在控制台上收到以下错误,没有抛出异常.

I have deployed my application on JBoss EAP 7 in SSL mode.
My application gets deployed and runs successfully but during start up, I get following error on console every time when server starts up and WAR is simultaneously deployed, no exception is thrown.

11:28:11,402 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 92) WFLYCTL0013: Operation ("read-attribute") failed - address: ([
    ("subsystem" => "undertow"),
    ("server" => "default-server"),
    ("https-listener" => "defaultssl")
]) - failure description: "WFLYCTL0216: Management resource '[(\"subsystem\" => \"undertow\")]' not found"

我一直在搜索红帽 JBoss 知识库,但没有找到任何解决此问题的方法.

I have been searching Red Hat JBoss Knowledgebase, but have not found any solution to this issue.

如果我在应用服务器完全启动并初始化后部署我的 WAR,则不会重现此问题.

这个问题并不影响我的申请.

此问题不会在 JBoss EAP 6.x、JBoss AS 7.1.x 和 Wildfly 上重现.
出现此类问题的原因是什么?

This issue is not reproduced on JBoss EAP 6.x, JBoss AS 7.1.x and Wildfly.
What can be the reason of such issue?

推荐答案

我观察了 JBoss EAP 7 应用服务器的行为.在服务器初始化期间不加载 undertow 子系统.当应用程序在启动期间尝试访问 undertow 子系统的详细信息时,会出现此问题.在服务器启动后部署应用程序时,不会发生此问题.

I observed the behavior of the JBoss EAP 7 application server. The undertow subsystem is not loaded during the server initialization. This issue occurs when application tries to access the details of the undertow subsystem during startup. When the application is deployed after server has started this issue does not occur.

这篇关于操作“读取属性"JBoss EAP 7 启动期间失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆