部署后Wildfly 10.1停止了部署 [英] Wildfly 10.1 stopd deployment after deploying

问题描述

我正在将具有几个单独的war和ear文件的WebApplication部署到Wildfly 10.1服务器.

I am deploying a WebApplication with several separate war and ear-files to a wildfly 10.1 server.

我的工作是:清理deployments，data/content和tmp文件夹，然后将所有必需的war和ear文件复制到Deployments-folder.

What I do is this: I clean the deployments, data/content and tmp folder, then copy all necessary war and ear files into the deployments-folder.

然后，我可以通过Spring Tool Suite 3.8.1(基本上是Eclipse Neon)以调试模式或直接通过standalone.sh来启动服务器.

Then, I start the Server either in Debug-Mode via Spring Tool Suite 3.8.1 (basically Eclipse Neon) or directly via standalone.sh.

服务器正常启动，部署所有项目并发布此消息:

The server starts up normally, gets deploys all projects and publishes this message:

[org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 326001ms - Started 5819 of 6193 services (642 services are lazy, passive or on-demand)

大约半秒后出现的下一条消息是第一个Unregistered web context消息，随后是常规部署停止. 与此相关的日志中没有消息，ERROR或WARNING，SEVERE或FATAL都没有.

The next message that follows, roughly half a second later, is the first Unregistered web context-message, followed by a general deployment stop. There is no message in the log connected to this, neither an ERROR, nor a WARNING, SEVERE or FATAL in sight.

在停止所有部署之后，服务器仍在运行，但是无法访问上下文.

After stopping all Deployments, the server still runs, but no context is reachable.

在一对一地部署应用程序时，服务器会接受，部署并保持运行，这导致人们认为服务器本身存在问题.

When deploying the applications one-by-one, the server accepts, deploys and keeps running, which leads be to believe that there is something wrong with the server itself.

与内存相关的VM参数如下:-Xms1024m -Xmx4096m. 服务器未按超时运行，因为已经过全面测试，并会生成错误消息.

the memory-relevant VM-Arguments are these: -Xms1024m -Xmx4096m. The server does not run on a timeout, as that has been thorougly tested and produces error messages.

推荐答案

好吧，长话短说:评论就是解决方案.

Okay, long story short: comment was solution.

standalone.xml和jboss.as.management.blocking.timeout中作为命令行参数的参数deployment-timeout确实可以在同一件事上协同工作，考虑到阻止命令行参数看似优先.

The parameters deployment-timeout in standalone.xml and jboss.as.management.blocking.timeout as command line parameter do work together on the same thing, considering blocking the command line parameter seemingly has precedence.

因此，如果同时设置了两个值，并且管理阻止程序高于部署超时，则会发生以下情况:

So if both values are set, and the management blocker is higher than the deployment-timeout, the following happens:

• 开始部署
• 部署超时触发器
• 管理超时仍然有时间，并且不会触发停止服务器
• 应用程序在管理超时期限内部署.
• 部署后扫描程序检查部署目录中的故障
• 部署超时将所有部署标记为失败
• 由于存在故障，所有部署都将取消部署

所以:没有错误消息，照常部署，然后立即取消部署.如果其他人有，请检查这些值.

So: No error message, Deployment as usual, followed by instant undeployment. Should anyone else have that, check those values.

这篇关于部署后Wildfly 10.1停止了部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！