This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
This bug was originally marked as duplicate of bug 249135, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE Dev (Build 201507150001) VM: Java HotSpot(TM) Client VM, 25.45-b02, Java(TM) SE Runtime Environment, 1.8.0_45-b14 OS: Windows 7 User Comments: GUEST: Started wildfly flynnk: Loading a copy of our project. GUEST: Running a wildfly-maven-web application. GUEST: NetBeans debuggin application hosted on WildFly 8.1.0 GUEST: I do not know what caused this error. A red icon was showing in the bottom right corner of Netbeans and I thought I should report it. GUEST: Travando GUEST: Run project on WildFly 8.1 GUEST: When starting up wildfly 8.2.0 GUEST: Unknown GUEST: i started the server at that time this error occured .. plz solve this Bineeth68: This exception has been raised when trying to run, Wild Fly 8.1 Server. GUEST: Iniciando Netbeans GUEST: while wildfly was starting i got this exception GUEST: starting wildfly 9.0.0.final Stacktrace: java.util.concurrent.RejectedExecutionException: Task org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities$3@1c7800c rejected from org.xnio.XnioWorker$TaskPool@39e3c3[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) at org.xnio.XnioWorker.execute(XnioWorker.java:741) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:464) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:243)
Created attachment 154680 [details] stacktrace
*** This bug has been marked as a duplicate of bug 249078 ***