Please use the Apache issue tracking system for new NetBeans issues ( !!

Bug 241805

Summary: Plugin cannot communicate with WildFly 8 Final
Product: serverplugins Reporter: jomu <jomu>
Component: WildFlyAssignee: ehsavoie <ehsavoie>
Status: RESOLVED FIXED QA Contact: issues <>
Priority: P2    
Version: 8.0   
Target Milestone: TBD   
Hardware: PC   
OS: Windows 7   
Issue Type: DEFECT Exception Report:

Description jomu 2014-02-13 09:38:52 UTC
Server port setup changed in RC1 and Final. Plugin can communicate with RC1 but no longer with WildFly Final. 
Plugin tries to communicate on port 9999 (management-native) which is no longer available by default in Final.
Please change either the implementation or show appropriate message to instance setup to add needed management-native port.
Comment 1 jomu 2014-02-13 09:39:28 UTC
Stackrace: Connection refused: no further information
	at Method)
	at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(
	at ...asynchronous invocation...(Unknown Source)
	at org.jboss.remoting3.EndpointImpl.doConnect(
	at org.jboss.remoting3.EndpointImpl.doConnect(
	at org.jboss.remoting3.EndpointImpl.connect(
	at org.jboss.remoting3.EndpointImpl.connect(
Caused: JBAS012174: Could not connect to remote://localhost:9999. The connection failed
Caused: java.lang.reflect.InvocationTargetException
	at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.netbeans.modules.javaee.wildfly.ide.commands.WildflyClient.executeOnModelNode(
	at org.netbeans.modules.javaee.wildfly.ide.commands.WildflyClient.undeploy(
	at org.netbeans.modules.javaee.wildfly.ide.commands.WildflyClient.undeploy(
	at org.netbeans.modules.javaee.wildfly.ide.commands.WildflyClient.deploy(
[catch] at org.netbeans.modules.javaee.wildfly.WildFlyDeploymentManager.distribute(
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(
	at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(
	at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(
	at org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(
	at org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(
	at org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(
	at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(
Comment 2 jomu 2014-02-13 09:42:48 UTC
Fix by updating standalone.xml in WildFly 8 Final:

<socket-binding-group ...>
   <socket-binding name="management-native" interface="management" port="${}"/>

            <native-interface security-realm="ManagementRealm">
                <socket-binding native="management-native"/>
Comment 3 ehsavoie 2014-02-13 09:47:43 UTC
This has been fixed in the 1.6 version of the plugin which is not the version you are using (I assume you are using the version packaged with the beta).
Comment 4 jomu 2014-02-13 09:55:03 UTC
You are right, it is version 1.0.4. 
How can I update? I tried to update in Netbeans and there is no update available.
Comment 5 jomu 2014-02-13 10:03:03 UTC
I used the following additional update center:, seems to work
Comment 6 graham-stewart 2014-08-16 04:00:47 UTC
This problem with the wildfly plugin still exists in version 1.0.17 which is the latest download in the plugin centre and version 8.1.0.Final of wildfly.
Comment 7 graham-stewart 2014-08-16 07:57:36 UTC
After further research: Jboss have removed the native management interface on port 9999. "Note that since CR1 we have finally dropped the native management port 9999, which instead uses the HTTP management port (9990)." Posted by Jason Greene on Feb 11, 2014.

I tried to use the update centre listed by jomu however this fails during the download report a network error downloading Do not know why this is being downloaded because on the update for WildFly Application Server is ticked.
Comment 8 ehsavoie 2014-08-19 07:06:15 UTC
The plugin will always use port 9990 for communicating with the server.
If you are using a version prior to 8.0 or if you change this port then it will not work.
This is not a bug you might want to create an enhancement request to make this port configurable in the plugin.
By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo