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 257402 - Stopping of server WildFly Application Server has timed-out
Summary: Stopping of server WildFly Application Server has timed-out
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.1
Hardware: PC Windows 8.1 x64
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2016-01-04 21:37 UTC by bennyn
Modified: 2016-05-19 01:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screenshot of error notification (6.23 KB, image/png)
2016-01-04 21:37 UTC, bennyn 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bennyn 2016-01-04 21:37:15 UTC 
Created attachment 157997 [details]
Screenshot of error notification

I am using NetBeans IDE 8.1 (Build 201510222201) running on Java 1.8.025 (64-Bit) and Windows 8.1 (64-Bit). I created a standard Java web application (using NetBeans' wizard) and selected a WildFly Standalone Application Server to run my web app. 

The app can be deployed on WildFly but when I want to stop the server, then NetBeans always shows me "Stopping of server WildFly Application Server has timed-out".

The last entry that can be seen in the WildFly log is:

21:55:44,761 INFO  [org.jboss.as.protocol] (Remoting "romeo:MANAGEMENT" task-7) WFLYPRT0057:  cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]

I expected this behaviour with WildFly AS "10.0.0.CR5" & "9.0.2.Final". I tried the same on my other computer (running Windows 10) without success.
Comment 1 Petr Hejl 2016-05-18 12:09:39 UTC 
I'm able to reproduce when using the "standalone" configuration (not just default "standalone-full").
Comment 2 Petr Hejl 2016-05-18 12:14:18 UTC 
It is even stranger, can reproduce until I touch the http port.
1) start standalone
2) stop -> fail

but
1) start standalone
2) browse to app url or deploy app
3) stop -> ok
Comment 3 Petr Hejl 2016-05-18 12:25:29 UTC 
Now it looks the difference is only the delay between the start and stop. When one waits a little after start is finished and invoke stop later everything works.
Comment 4 Petr Hejl 2016-05-18 12:43:59 UTC 
Now I'm not able to reproduce. Seems to be random.
Comment 5 ehsavoie 2016-05-18 13:20:35 UTC 
Has the server boot finished when you called the stop ?
Does the deployment succeeded ?
There might be a race on the deployment ops during the boot (from the scanner) and the shutdown https://issues.jboss.org/browse/WFCORE-1430
Comment 6 Petr Hejl 2016-05-18 13:48:50 UTC 
Should be fixed in web-main b56a3088fd41.
Comment 7 Quality Engineering 2016-05-19 01:44:19 UTC 
Integrated into 'main-silver', will be available in build *201605190002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/b56a3088fd41
User: Petr Hejl <phejl@netbeans.org>
Log: #257402 - Stopping of server WildFly Application Server has timed-out