将WildFly 9.x与NetBeans 8.1

Question

this问题的一部分。为了在NetBeans IDE 8.1（最终版本）中使用WildFly 9.0.2 final，仍然会出现一些严重的后果。

IDE（集成插件）永远不会自动部署应用程序，即使＆＃34; Deploy on Save＆＃34; IDE上的选项已启用（已选中/已打开）。使用GlassFish Server时，这一切都会正确发生。

它已经是reported，其状态是＆＃34;已解决修复＆＃34;对于NetBeans 8.0，但很难依赖（抱歉）。

我已将相对较大的Java EE应用程序的大部分从GlassFish 4.1迁移到WildFly 9.0.2 final，包括JDBC领域和JAAS。一旦应用程序部署在服务器上，它就会非常好，但是只要对应用程序进行一些更改，它总是需要硬部署应用程序。当对XHTML / JSP文件（经常需要）进行一次或几次更改时，硬部署应用程序确实会导致内存溢出＆＃34;在很短的时间内发出。使用GlassFish Server时会发生这种情况。

停止并重新启动服务器也会导致严重的问题，但很多时候（几乎总是），特别是在尝试停止服务器而不从服务器取消部署应用程序的情况下，这会导致抛出以下异常（取消部署应用程序之后停止服务器需要从头开始重新部署应用程序，这是一个非常耗时的过程。）

16:45:32,218 INFO  [org.jboss.as.server] (management-handler-thread - 20) WFLYSRV0211: Suspending server
16:45:32,234 INFO  [org.jboss.as.protocol] (Remoting "om-f6b0ea3ad206:MANAGEMENT" task-7) WFLYPRT0057:  cancelled task by interrupting thread Thread[management-handler-thread - 20,5,management-handler-thread]
16:45:32,234 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 20) WFLYCTL0190: Step handler org.jboss.as.server.operations.ServerShutdownHandler$1@1cd3b8b for operation {"operation" => "shutdown","operation-headers" => {"caller-type" => "user","access-mechanism" => "NATIVE"},"address" => undefined} at address [] failed handling operation rollback -- java.lang.NullPointerException: java.lang.NullPointerException
    at org.hornetq.ra.inflow.HornetQActivation.teardown(HornetQActivation.java:417)
    at org.hornetq.ra.inflow.HornetQActivation.stop(HornetQActivation.java:312)
    at org.hornetq.ra.HornetQResourceAdapter.endpointDeactivation(HornetQResourceAdapter.java:185)
    at org.jboss.jca.core.rar.EndpointImpl.deactivate(EndpointImpl.java:260)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.deactivate(MessageDrivenComponent.java:251)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.access$100(MessageDrivenComponent.java:61)
    at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$1.preSuspend(MessageDrivenComponent.java:87)
    at org.jboss.as.server.suspend.SuspendController.suspend(SuspendController.java:72)
    at org.jboss.as.server.operations.ServerShutdownHandler$1$1.handleResult(ServerShutdownHandler.java:134)
    at org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1401)
    at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1381)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1332)
    at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1292)
    at org.jboss.as.controller.AbstractOperationContext$Step.access$300(AbstractOperationContext.java:1180)
    at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:937)
    at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:885)
    at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601)
    at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354)
    at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330)
    at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1183)
    at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:362)
    at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:218)
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:201)
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:128)
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:150)
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:146)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.security.auth.Subject.doAs(Subject.java:422)
    at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
    at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:146)
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
    at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    at org.jboss.threads.JBossThread.run(JBossThread.java:320)

抛出此异常后，停止服务器的进程将无限期地进行，直到几分钟后出现以下消息。

这是否需要一些额外的步骤才能使IDE的插件以通常的方式运行？我觉得IDE的插件无法与服务器/构建器正确通信。

有解决方案/解决方法吗？