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.
Product Version = NetBeans IDE Dev (Build 201509170002) and 8.0.2 Operating System = Mac OS X version 10.10.4 running on x86_64 Java; VM; Vendor = 1.8.0_45 Runtime = Java HotSpot(TM) 64-Bit Server VM 25.45-b02 Reproducibility: Happens every time When I attempt to run a web application on Wildfly, the deployment fails: Netbeans starts Wildfly (apparently without error). Netbeans builds the application, the appears to try and start the server again before deployment, which fails because the first instance is already bound to the relevant ports. Netbeans appears unaware that the server has started; it cannot be stopped from Netbeans, but must be stopped from the command line. The built war file works when manually deployed to Wildfly. From Build Log: ------------------------------------------------------------------------ BUILD SUCCESS ------------------------------------------------------------------------ Total time: 3.985s Finished at: Thu Sep 17 15:56:22 PDT 2015 Final Memory: 8M/123M ------------------------------------------------------------------------ NetBeans: Deploying on WildFly Application Server profile mode: false debug mode: false force redeploy: true Starting WildFly Application Server WildFly Application Server Started Distributing /path/to/file.war to [org.netbeans.modules.javaee.wildfly.WildflyDeploymentManager$1@6deb4b35] java.lang.reflect.InvocationTargetException From Server Log (which gets cleared before Netbeans starts Wildfly the second time): JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /Applications/Wildfly/wildfly-9.0.1.Final JAVA: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/java JAVA_OPTS: -XX:+UseCompressedOops -XX:+UseCompressedOops -Xms128m -Xmx512m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 15:56:23,978 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final 15:56:25,212 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 15:56:25,367 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting 15:56:27,472 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 24) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. 15:56:27,515 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) 15:56:27,557 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.1.Final 15:56:27,574 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.1.Final 15:56:27,686 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem. 15:56:27,720 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors 15:56:27,747 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main] 15:56:27,785 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.9.Final 15:56:27,804 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) 15:56:27,859 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. 15:56:27,863 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem 15:56:27,863 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem 15:56:27,866 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=4.9.2.Final 15:56:27,901 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension 15:56:27,985 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting 15:56:27,986 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.9.Final starting 15:56:28,019 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service 15:56:28,027 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 15:56:28,376 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path /Applications/Wildfly/wildfly-9.0.1.Final/welcome-content 15:56:28,474 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server. 15:56:28,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting 15:56:28,687 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:150) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:437) at sun.nio.ch.Net.bind(Net.java:429) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:182) at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243) at org.wildfly.extension.undertow.HttpListenerService.startListening(HttpListenerService.java:115) at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:147) ... 5 more 15:56:29,128 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /Applications/Wildfly/wildfly-9.0.1.Final/standalone/deployments 15:56:29,262 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:269) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:160) at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:235) ... 5 more Caused by: java.net.BindException: Address already in use at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:437) at sun.nio.ch.Net.bind(Net.java:429) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67) at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:182) at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:243) at org.jboss.as.domain.http.server.ManagementHttpServer.start(ManagementHttpServer.java:147) ... 6 more 15:56:29,273 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("core-service" => "management"), ("management-interface" => "http-interface") ]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.serverManagement.controller.management.http" => "org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service Caused by: java.lang.RuntimeException: java.net.BindException: Address already in use Caused by: java.net.BindException: Address already in use"}, "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.serverManagement.controller.management.http.shutdown"], "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"] } } 15:56:29,280 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.ws.config"], "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"] }} 15:56:29,283 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "undertow"), ("server" => "default-server"), ("http-listener" => "default") ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener Caused by: java.net.BindException: Address already in use"}} 15:56:29,287 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => [ "jboss.ejb.default-local-ejb-receiver-service", "jboss.ejb3.ejbClientContext.default", "jboss.ejb3.localEjbReceiver.value" ], "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"] }} 15:56:29,290 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "ejb3"), ("service" => "remote") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]} 15:56:29,375 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] WFLYCTL0186: Services which failed to start: service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Could not start http listener service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: WFLYSRV0083: Failed to start the http-interface service 15:56:29,601 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled 15:56:29,602 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled 15:56:29,602 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 6190ms - Started 180 of 369 services (8 services failed or missing dependencies, 210 services are lazy, passive or on-demand
Works just fine for me. Obviously your http port is already occupied: Caused by: java.net.BindException: Address already in use
(In reply to Petr Hejl from comment #1) > Works just fine for me. Obviously your http port is already occupied: Caused > by: java.net.BindException: Address already in use As I stated in the original description, netbeans starts wildfly TWICE, once before it starts the build, and again after the build is completed. The port is bound to the first instance, and the second instance throws the BindException. based on the behavior, it appears that netbeans can't tell the first instance started successfully and tries to start it again, which will always cause a BindException. I've tried this many times with clean installs of both netbeans and wildfly and always gotten the same results. The available documentation doesn't seem to address this situation. If you've been able to get this to work properly, can you please let me know how. Thanks
Can you attach the log from the first start and the IDE log? Perhaps a firewall might be blocking the startup detection.
Created attachment 156364 [details] server.log
(In reply to Petr Hejl from comment #3) > Can you attach the log from the first start and the IDE log? Perhaps a > firewall might be blocking the startup detection. FWIW, I don't believe there's a firewall running on these systems. The firewall at system preferences/security & privacy is disabled. I haven't had any firewall trouble with other services running on the local system (Glassfish, Tomcat, derby, PostgreSQL, etc.). I stopped wildfly (from cli) cleared server.log and attempted to run a project from netbeans. I've attached the resulting server.log. The first startup ends at 09:43:30.655, the second begins at 09:34:37.905 I'm not sure where the IDE log is in the file system, but here's a copy-paste from the IDE window (again, cleared right before I tried to run a project) Thanks for any insight you can offer INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,MetaforerssAir5 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment] java.lang.NullPointerException at java.io.File.<init>(File.java:277) at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.<init>(WildflyDatasourceManager.java:100) at org.netbeans.modules.javaee.wildfly.ide.WildflyOptionalDeploymentManagerFactory.getDatasourceManager(WildflyOptionalDeploymentManagerFactory.java:109) at org.netbeans.modules.j2ee.deployment.plugins.spi.support.ProxyOptionalFactory.getDatasourceManager(ProxyOptionalFactory.java:134) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getDatasourceManager(ServerInstance.java:676) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployDatasources(ServerInstance.java:747) at org.netbeans.modules.j2ee.deployment.impl.DeploymentHelper.deployDatasources(DeploymentHelper.java:115) [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:239) at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:208) at org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:90) at org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:87) at org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:209) at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:163) at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:162) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153) INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,MetaforerssAir5 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true INFO [org.netbeans.modules.javaee.wildfly.ide.WildflyOutputSupport]: Instance WildFly Application Server started again without proper stop INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment] java.lang.NullPointerException at java.io.File.<init>(File.java:277) at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.<init>(WildflyDatasourceManager.java:100) at org.netbeans.modules.javaee.wildfly.ide.WildflyOptionalDeploymentManagerFactory.getDatasourceManager(WildflyOptionalDeploymentManagerFactory.java:109) at org.netbeans.modules.j2ee.deployment.plugins.spi.support.ProxyOptionalFactory.getDatasourceManager(ProxyOptionalFactory.java:134) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getDatasourceManager(ServerInstance.java:676) at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployDatasources(ServerInstance.java:747) at org.netbeans.modules.j2ee.deployment.impl.DeploymentHelper.deployDatasources(DeploymentHelper.java:115) [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:239) at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:208) at org.netbeans.modules.maven.j2ee.execution.ExecutionChecker.executionResult(ExecutionChecker.java:93) at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:252) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153)
I believe there has to be some specific in your setup. Unfortunately it looks like the attached server log contains only the second startup.
Please start the IDE with -J-Dorg.netbeans.modules.javaee.wildfly.level=0, try again and attach the server log (http://wiki.netbeans.org/FaqLogMessagesFile). Also the server log with bot starts would be fine if possible (Isn't it preserved in server.log in the filesystem as rotated log?)
Created attachment 156480 [details] server.log from 2015-10-01
Created attachment 156481 [details] messages.log from 2015-10-01
Attached new server.log and messages.log server.log contains both attempts to start wildfly. Here is the end of the first attempt: 2015-10-01 15:25:34,617 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started in 5810ms - Started 197 of 373 services (210 services are lazy, passive or on-demand) And the start of the second: 2015-10-01 15:25:47,500 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final I noticed this in messages.log: Caused: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://localhost:9999. The connection failed perhaps this is another manifestation of this bug? https://netbeans.org/bugzilla/show_bug.cgi?id=241805 even though the bug claims this was addressed over a year ago. FWIW I appear to be running version 1.0.21 of the wildfly plugin (based on the log file, as it's not shown as a plugin anymore
Similar issue here: WildFly 9.0.1.Final seems to start fine, but NetBeans doesn't seem to be aware that WildFly is running. I was OK with WildFly 8.1.0.Final Product Version: NetBeans IDE 8.0.2 (Build 201411181905) Updates: NetBeans IDE is updated to version NetBeans 8.0.2 Patch 2 Java: 1.8.0_51; Java HotSpot(TM) 64-Bit Server VM 25.51-b03 Runtime: Java(TM) SE Runtime Environment 1.8.0_51-b16 System: Windows 7 version 6.1 running on amd64; Cp1252; de_CH (nb)
Where is the plugin coming from? Is it some update or have you built it? org.netbeans.modules.javaee.wildfly/1 [1.0.21 20150805-8230772f5f18] Can you try to reproduce the issue with the clean installation of dev build?
Can you share the .netbeans/web-main/config/J2EE/InstalledServers/.nbattrs? It may contain FS path so remove it if it is sensitive for you. Also can you describe how the server was registered? Especially value of management port suggested or filled during the registration?
This is because the wildfly 9 is not properly recognized with NetBeans 8.0.2 except if you use the plugin update from the plugin portal. Same for old dev builds, this has been fixed since (the admin port is 9990 in WF9 not 9999 which is JBoss AS 7 and WildFly 8)
Any updates?
The newer nightly builds appear to have resolved this issue. Thanks for your assistance chasing this down
I have this same issue with a nightly build (201602150002)
(In reply to ricardovm from comment #17) > I have this same issue with a nightly build (201602150002) Could you be more specific as I don't have any issue like this on the same build ? Which OS, which JVM on Netbeans and on WidlFLy ? Be careful that WildFly 10 requires Java8 thus to run the Netbeans plugin Netbeans must be running also on Java 8.
(In reply to ehsavoie from comment #18) > (In reply to ricardovm from comment #17) > > I have this same issue with a nightly build (201602150002) > > Could you be more specific as I don't have any issue like this on the same > build ? Which OS, which JVM on Netbeans and on WidlFLy ? Be careful that > WildFly 10 requires Java8 thus to run the Netbeans plugin Netbeans must be > running also on Java 8. Mac OS X 10.11.3 java version "1.8.0_73" (used by NB and WF) WildFly 9.0.1 NetBeans nightly build (201602150002) (same problem with latest 8.1 stable)
I gess I solved this problem on my machine. Can't really prove that this was actually the problem because I had to make a fresh installation and it works fine. But while restoring my backups, I found this: JBOSS_HOME=..../wildfly-9.0.1.Final Netbeans WildFly plugin config: ..../wildfly-9.0.0.Final/standalone/configurations/standalone.xml (note version numbers) If I have both versions, it works. If I remove 9.0.0, I get this bug. I think it should show a message saying that the configuration file was not found. I guess when I moved from 9.0.0 to 9.0.1, deleting the first one, I forgot to change Netbeans configuration (it's not my main IDE yet).
There is a warning now when you change the server basedir, asking if you want to use the 'new' configuration file