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.

Bug 254224

Summary:	WFLYCC0030: Allocation stack trace:
Product:	serverplugins	Reporter:	lehel
Component:	WildFly	Assignee:	ehsavoie <ehsavoie>
Status:	NEW ---
Severity:	normal	CC:	Charlie3D, cmac, emiddio, hablocher, hajuesch, ivan.bn, jan.kurnatowski, jockel, jomu, Katthacar, MackSix, ozziej, prodigy4440, rsb2097, soladnet, sviatopolk, s_fuhrm, vdtoorn, WongK
Priority:	P3
Version:	8.1
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	216845
Attachments:	stacktrace stacktrace stacktrace stacktrace stacktrace

Description lehel 2015-08-09 15:41:44 UTC

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)

Comment 1 lehel 2015-08-09 15:41:47 UTC

Created attachment 155233 [details]
stacktrace

Comment 2 Exceptions Reporter 2015-08-12 04:24:22 UTC

Created attachment 155277 [details]
stacktrace

Switching to another tab in the source file editor.

Comment 3 vdtoorn 2015-08-18 09:34:07 UTC

Created attachment 155419 [details]
stacktrace

After generation of jsp pages from entity classes.

Comment 4 MackSix 2015-09-22 16:42:21 UTC

Created attachment 156363 [details]
stacktrace

1. Opened a JSP project and it had notice of "Resolve Missing Server problem...".
2. Viewed problem and it showed a list of available servers, including WildFly 8.0.2. 
3. Cancelled.

WildFly 8.0.2 nor any other server was running. 

This was thrown.

Comment 5 MackSix 2015-09-24 16:30:48 UTC

Created attachment 156411 [details]
stacktrace

1. Added WildFly 8.2.0 and 9.0.0
2. Llaunced an application on 8.2.0 and then shutdown server.
3. Launched the application on 9.0.0 and then shutdown server. 

According to Process Explorer they were not running and after a 2 or 3 minuts, this popped up.

Comment 6 Petr Hejl 2015-09-25 10:20:21 UTC

*** Bug 254466 has been marked as a duplicate of this bug. ***