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.
Wildfly plugin web app/war deployment failing. If I drop the war in wildfly-8.0.0.Final/standalone/deployments directory then the app deploys 100% Note I am running Version: 1.0.6 of the Wildfly plugin from: http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz Product Version = NetBeans IDE 8.0 Beta (Build 201401141042) Operating System = Mac OS X version 10.9.1 running on x86_64 Java; VM; Vendor = 1.7.0_45 Runtime = Java HotSpot(TM) 64-Bit Server VM 24.45-b08
Created attachment 145183 [details] IDE log
I am experiencing the same issue. I have WildFly 8.0.0.CR1 working with the plugin. When I migrated to WildFly 8.0.0.Final the plugin no longer works correctly. The 8.0.0.Final server can be started with the plugin, however after starting it the plugin does not detect that it is running. Then when I deploy via NetBeans, it appears the plugin decides WildFly is not running and tries to start it. This fails as the ports are in use and the deployment is not successful. Like I said everything works with 8.0.0.CR1 (same project). Product Version: NetBeans IDE 8.0 Beta (Build 201401141042) Java: 1.7.0_51; Java HotSpot(TM) 64-Bit Server VM 24.51-b03 Runtime: Java(TM) SE Runtime Environment 1.7.0_51-b13 System: Windows 8 version 6.2 running on amd64; Cp1252; en_US (nb) WildFly plugin version: 1.0.4
Hi RayDeCampo, the WildFly team has removed the port 9999 for administration, using only 9090. Thus the plugin has to be updated to 1.0.6 at least to work with Wildfly Final. Either use the update center (http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz) or the nightly builds.
Comment on attachment 145183 [details] IDE log INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment] The module has not been deployed. See the server log for details. [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:259) at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:266) at org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:87) at org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:87) at org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:207) at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:161) at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:159) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153) INFO [org.netbeans.modules.j2ee.deployment.impl.TargetServer]: Cannot incrementally deploy to more than one target INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment] The module has not been deployed. See the server log for details. [catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:259) at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:266) at org.netbeans.modules.maven.j2ee.execution.ExecutionChecker.executionResult(ExecutionChecker.java:93) at org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:249) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:153) Could you please attach the wildfly logs ?
Created attachment 145280 [details] WildFly server log WildFly log added
This looks like a WildFly issue, with some Weld service not started when you want it. "Services that may be the cause:" => [ "jboss.deployment.unit.\"pyramid-1.0-SNAPSHOT\".beanmanager", "jboss.jdbc-driver.derbyclient_jar", "jboss.remoting.remotingConnectorInfoService.http-remoting-connector" Could you send me the war so I can reproduce it (I might even fix WildFly ;o) )? Or maybe you could try to deploy your war using the jboss-cli (which is basically what the plugin does).
I want your war then ;o) I'll give it a look this afternoon.
i have the exact same issue using a project migrated migrated from glasfish 4. The problem seems to be that the War is deployed as an exploded folder and not as a WAR-file. That's what wildfly first complains about. After that it refuses to find classes in web-in/lib an web-inf/classes. Manual deployment as a war-file works without any issue. Maybe it's a misconfiguration of netbeans/maven because the plugin would use jboss-cli and not an exploded WAR-file, or am i wrong? Is there a way to check if the plugin is called correctly?
Integrated into 'main-silver', will be available in build *201402220001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/aa0c5abad9ee User: Emmanuel Hugonnet <ehsavoie@netbeans.org> Log: ng bug #241864 : now components without the expected extension are correctly deployed if Deploy on Save is checked.