我们在链接安全策略时遇到错误-詹金斯（Jenkins）部署时模块状态不一致。
我们知道如何通过从生成的（Glassfish: Error in linking security policy for）中删除安全策略来绕过此问题，但是我们对可能的根本原因更感兴趣。
谢谢。
整个痕迹：[javax.enterprise.system.core] [tid：ThreadID = 119 ThreadName = admin-thread-pool（8）] [timeMillis：1586526062207] [levelValue：1000] [[生命周期处理中的异常org.glassfish.deployment.common.DeploymentException：链接安全策略时出错-模块状态不一致位于com.sun.enterprise.security.ee.SecurityUtil.linkPolicyFile（SecurityUtil.java:336）在com.sun.enterprise.security.ee.SecurityDeployer.linkPolicies（SecurityDeployer.java:319）位于com.sun.enterprise.security.ee.SecurityDeployer.access $ 100（SecurityDeployer.java:87）在com.sun.enterprise.security.ee.SecurityDeployer $ AppDeployEventListener.event（SecurityDeployer.java:145）在org.glassfish.kernel.event.EventsImpl.send（EventsImpl.java:131）在org.glassfish.internal.data.ApplicationInfo.load（ApplicationInfo.java:329）在com.sun.enterprise.v3.server.ApplicationLifecycle.deploy（ApplicationLifecycle.java:497）在com.sun.enterprise.v3.server.ApplicationLifecycle.deploy（ApplicationLifecycle.java:220）在org.glassfish.deployment.admin.DeployCommand.execute（DeployCommand.java:487）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ 2 $ 1.run（CommandRunnerImpl.java:539）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ 2 $ 1.run（CommandRunnerImpl.java:535）在java.security.AccessController.doPrivileged（本机方法）在javax.security.auth.Subject.doAs（Subject.java:360）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ 2.execute（CommandRunnerImpl.java:534）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ 3.run（CommandRunnerImpl.java:565）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ 3.run（CommandRunnerImpl.java:557）在java.security.AccessController.doPrivileged（本机方法）在javax.security.auth.Subject.doAs（Subject.java:360）在com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand（CommandRunnerImpl.java:556）在com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand（CommandRunnerImpl.java:1464）在com.sun.enterprise.v3.admin.CommandRunnerImpl.access $ 1300（CommandRunnerImpl.java:109）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ ExecutionContext.execute（CommandRunnerImpl.java:1846）在com.sun.enterprise.v3.admin.CommandRunnerImpl $ ExecutionContext.execute（CommandRunnerImpl.java:1722）在org.glassfish.admin.rest.utils.ResourceUtil.runCommand（ResourceUtil.java:263）在org.glassfish.admin.rest.utils.ResourceUtil.runCommand（ResourceUtil.java:234）在org.glassfish.admin.rest.utils.ResourceUtil.runCommand（ResourceUtil.java:285）在org.glassfish.admin.rest.resources.TemplateListOfResource.createResource（TemplateListOfResource.java:136）在sun.reflect.NativeMethodAccessorImpl.invoke0（本机方法）处在sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）在sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）在java.lang.reflect.Method.invoke（Method.java:498）在org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory $ 1.invoke（ResourceMethodInvocationHandlerFactory.java:81）在org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher $ 1.run（AbstractJavaResourceMethodDispatcher.java:144）在org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke（AbstractJavaResourceMethodDispatcher.java:161）在org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider $ ResponseOutInvoker.doDispatch（JavaResourceMethodDispatcherProvider.java:160）处在org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch（AbstractJavaResourceMethodDispatcher.java:99）处在org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke（ResourceMethodInvoker.java:389）在org.glassfish.jersey.server.model.ResourceMethodInvoker.apply（ResourceMethodInvoker.java:347）在org.glassfish.jersey.server.model.ResourceMethodInvoker.apply（ResourceMethodInvoker.java:102）在org.glassfish.jersey.server.ServerRuntime $ 2.run（ServerRuntime.java:326）在org.glassfish.jersey.internal.Errors $ 1.call（Errors.java:271）在org.glassfish.jersey.internal.Errors $ 1.call（Errors.java:267）在org.glassfish.jersey.internal.Errors.process（Errors.java:315）在org.glassfish.jersey.internal.Errors.process（Errors.java:297）在org.glassfish.jersey.internal.Errors.process（Errors.java:267）在org.glassfish.jersey.process.internal.RequestScope.runInScope（RequestScope.java:317）在org.glassfish.jersey.server.ServerRuntime.process（ServerRuntime.java:305）在org.glassfish.jersey.server.ApplicationHandler.handle（ApplicationHandler.java:1154）在org.glassfish.jersey.grizzly2.httpserver.GrizzlyHttpContainer.service（GrizzlyHttpContainer.java:384）在org.glassfish.admin.rest.adapter.RestAdapter $ 2.service（RestAdapter.java:316）在org.glassfish.admin.rest.adapter.RestAdapter.service（RestAdapter.java:179）在com.sun.enterprise.v3.services.impl.ContainerMapper $ HttpHandlerCallable.call（ContainerMapper.java:466）在com.sun.enterprise.v3.services.impl.ContainerMapper.service（ContainerMapper.java:169）在org.glassfish.grizzly.http.server.HttpHandler.runService（HttpHandler.java:206）在org.glassfish.grizzly.http.server.HttpHandler.doHandle（HttpHandler.java:180）在org.glassfish.grizzly.http.server.HttpServerFilter.handleRead（HttpServerFilter.java:235）在org.glassfish.grizzly.filterchain.ExecutorResolver $ 9.execute（ExecutorResolver.java:119）在org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter（DefaultFilterChain.java:284）在org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart（DefaultFilterChain.java:201）在org.glassfish.grizzly.filterchain.DefaultFilterChain.execute（DefaultFilterChain.java:133）在org.glassfish.grizzly.filterchain.DefaultFilterChain.process（DefaultFilterChain.java:112）在org.glassfish.grizzly.ProcessorExecutor.execute（ProcessorExecutor.java:77）在org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent（TCPNIOTransport.java:526）在org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent（AbstractIOStrategy.java:112）在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0（WorkerThreadIOStrategy.java:117）at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access $ 100（WorkerThreadIOStrategy.java:56）在org.glassfish.grizzly.strategies.WorkerThreadIOStrategy $ WorkerThreadRunnable.run（WorkerThreadIOStrategy.java:137）中在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.doWork（AbstractThreadPool.java:591）在org.glassfish.grizzly.threadpool.AbstractThreadPool $ Worker.run（AbstractThreadPool.java:571）在java.lang.Thread.run（Thread.java:748）]]
问题已解决。
[当作业将战争部署到自动部署文件夹中时就存在。
已将其更改为使用asadmin deploy，它可以正常工作。