This issue was reported manually by lehel.
It already has 5 duplicates 


Build: NetBeans IDE Dev (Build 201507270002)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.0-b70, Java(TM) SE Runtime Environment, 1.8.0-b132
OS: Windows 7

User Comments:
lehel: Stopping WildFly Application server

rsb2097: Deployed application before starting server

GUEST: simple web project (javaEE7) deployed to wildfly 9.0 beta2. simply selected 'run' from the project tree

GUEST: WildFly 9

jan.kurnatowski: I was performing some additional tests related to Bug #253302. NVIDIA Network Service binds to port 9990, which is also used by WildFly Web Administration Console. Starting WildFly 9.0 Final from Netbeans while NVIDIA Network Service is already running causes the problem described in Bug #253302. In such a situation I couldn't figure out how to stop WildFly from within Netbeans (the stop button in the WildFly Application Server Output tab was disabled), so I tried the quickest (and dirtiest) way to stop the server: I killed WildFly Java process in Windows Task Manager. Then I stopped NVIDIA Network Service, closed Netbeans and repeated this scenario. This time WildFly started properly, but this exception was thrown.




Stacktrace: 
WFLYCC0030: Allocation stack trace:
   at java.lang.Thread.getStackTrace(Thread.java:1551)
   at org.jboss.as.controller.client.impl.RemotingModelControllerClient.<init>(RemotingModelControllerClient.java:74)
   at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:567)
   at org.jboss.as.controller.client.ModelControllerClient$Factory.create(ModelControllerClient.java:423)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:0)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)