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 244427 - Netbeans 8 had problems deploying to Wildfly 8.1 CR1 or CR2
Summary: Netbeans 8 had problems deploying to Wildfly 8.1 CR1 or CR2
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P2 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-11 19:26 UTC by kjjaeger
Modified: 2014-06-06 14:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Log file from Netbeans (57.12 KB, application/octet-stream)
2014-05-11 19:26 UTC, kjjaeger
Details
This is the error I was getting before when using the domain option (59.02 KB, application/octet-stream)
2014-05-11 19:30 UTC, kjjaeger
Details
This is my standalone-full.xml from a recent Wildfly 8.1 - build 1100 (23.84 KB, text/xml)
2014-05-13 00:43 UTC, kjjaeger
Details
This is my standalone.xml from the same Wildfly 8.1 - build 1100 (18.83 KB, text/xml)
2014-05-13 00:44 UTC, kjjaeger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kjjaeger 2014-05-11 19:26:12 UTC
Created attachment 147219 [details]
Log file from Netbeans

There are serious problems deploying to Wildfly 8.1.  It seems to happen the most when choosing the "domain" option for the server configuration.  This time I used standalone with standalone-full.xml as the configuration file.
Comment 1 kjjaeger 2014-05-11 19:30:17 UTC
Created attachment 147220 [details]
This is the error I was getting before when using the domain option
Comment 2 ehsavoie 2014-05-12 07:28:45 UTC
This seems to be related to datasources and their parsing in the XML file.
I'll take a look. Could you provide the standalone-full.xml you are using ?
Comment 3 kjjaeger 2014-05-13 00:43:11 UTC
Created attachment 147241 [details]
This is my standalone-full.xml from a recent Wildfly 8.1 - build 1100

I think I should attache the standalone.xml because it is doing the same thing now.
Comment 4 kjjaeger 2014-05-13 00:44:41 UTC
Created attachment 147242 [details]
This is my standalone.xml from the same Wildfly 8.1 - build 1100

I am adding this as well because there are the only two XML configurations I have used.
Comment 5 kjjaeger 2014-05-13 00:46:38 UTC
This is the newest stacktrace.  I am getting these for standalone more now, not just domain mode.

INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.j2ee.deployment.plugins.spi.IncrementalDeployment.getDirectoryForNewApplication(IncrementalDeployment.java:147)
	at org.netbeans.modules.j2ee.deployment.impl.InitialServerFileDistributor.distribute(InitialServerFileDistributor.java:105)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.initialDistribute(TargetServer.java:261)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:666)
[catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:246)
	at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:266)
	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:208)
	at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:162)
	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.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.j2ee.deployment.plugins.spi.IncrementalDeployment.getDirectoryForNewApplication(IncrementalDeployment.java:147)
	at org.netbeans.modules.j2ee.deployment.impl.InitialServerFileDistributor.distribute(InitialServerFileDistributor.java:105)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.initialDistribute(TargetServer.java:261)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:666)
[catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:246)
	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)
INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,jaegermobile1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=C:\Users\Ken\Desktop\wildfly-8.1.0.Final-SNAPSHOT\standalone
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.j2ee.deployment.plugins.spi.IncrementalDeployment.getDirectoryForNewApplication(IncrementalDeployment.java:147)
	at org.netbeans.modules.j2ee.deployment.impl.InitialServerFileDistributor.distribute(InitialServerFileDistributor.java:105)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.initialDistribute(TargetServer.java:261)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:666)
[catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:246)
	at org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:266)
	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:208)
	at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:162)
	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.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.j2ee.deployment.plugins.spi.IncrementalDeployment.getDirectoryForNewApplication(IncrementalDeployment.java:147)
	at org.netbeans.modules.j2ee.deployment.impl.InitialServerFileDistributor.distribute(InitialServerFileDistributor.java:105)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.initialDistribute(TargetServer.java:261)
	at org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:666)
[catch] at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:246)
	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)
Comment 6 kjjaeger 2014-05-13 01:16:44 UTC
I just switched to Wildfly 8.1 CR2 which I think was released today, and things are looking better now.

INFO [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: Could not create instance null
INFO [org.xnio]: XNIO version 3.2.2.Final
INFO [org.xnio.nio]: XNIO NIO Implementation Version 3.2.2.Final
INFO [org.jboss.remoting]: JBoss Remoting version 4.0.3.Final
INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,jaegermobile1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=C:\Users\Ken\Desktop\wildfly-8.1.0.CR2\standalone
INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,jaegermobile1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=C:\Users\Ken\Desktop\wildfly-8.1.0.CR2\standalone

My test application deployed just fine using either standalone.xml or standalone-full.xml  I have yet to try the "domain" option yet with Wildfly CR2, but I will try that next.  If it works I think you can call this resolved.
Comment 7 kjjaeger 2014-05-13 01:25:04 UTC
Well I spoke too soon.  When I recreated the Wildfly server as with the "domain" option I am back to this:

INFO [global]: JAVA_OPTS=-Xms128m -Xmx512m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,jaegermobile1 -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=C:\Users\Ken\Desktop\wildfly-8.1.0.CR2\standalone
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.deployDatasources(WildflyDatasourceManager.java:139)
	at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployDatasources(ServerInstance.java:750)
	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:266)
	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:208)
	at org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:162)
	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.devmodules.api.Deployment]
java.lang.NullPointerException
	at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.deployDatasources(WildflyDatasourceManager.java:139)
	at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.deployDatasources(ServerInstance.java:750)
	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: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)
Comment 8 kjjaeger 2014-05-13 02:32:52 UTC
I thought perhaps I should be choosing domain.xml as the configuration for the "domain" setting but I get this when using domain.xml

22:30:08,195 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
22:30:08,605 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
22:30:08,728 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.1.0.CR2 "Kenny" starting
22:30:09,198 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.1.0.CR2.jar:8.1.0.CR2]
	at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.1.0.CR2.jar:8.1.0.CR2]
	at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.1.0.CR2.jar:8.1.0.CR2]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60-ea]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,38]
Message: Unexpected element '{urn:jboss:domain:2.1}domain'
	at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
	at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.1.0.CR2.jar:8.1.0.CR2]
	... 3 more
Comment 9 ehsavoie 2014-05-13 04:49:06 UTC
Are you referring to Netbeans 'domain' option or to Wildfly domain configuration ?
The second is not supported currently and the first one shouldn't do anything.
Comment 10 ehsavoie 2014-05-13 09:20:51 UTC
If I remember correctly the domain.xml doesn't support the scanner so it won't work with the plugin because I deploy an exploded war when using the deploy on save option.

There were also a bunch of issues on the incoherence between the scanner and the admin API of Wildfly : https://issues.jboss.org/browse/WFLY-3305 which may create issues with the plugin. But I'm afraid the fix won't make it for 8.1.0

I'll take a look at this one when I have some time but it will be later on this week or maybe the next one.
Comment 11 ehsavoie 2014-05-19 14:46:09 UTC
Ok, you can't use the domain select box because domain mode is not going to work properly with Netbeans.
I made the choice of using exploded mode in some case to avoid repackaging the whole apllication and reploying everything on each save (I think you shouldn't hit the issue without deploy on save).
The domain mode can't have a file system scanner for deployments which is what i use for incremental deployment (overwritting files). So I can't copy the war files into the deployments dir.
Thus i will deactivate the domain combobox with only standalone as the choice.


As for the datasource issue, next on my list :o)
Comment 12 ehsavoie 2014-05-19 16:15:04 UTC
I don't have any issue with the 8.1.0.CR2 final build. Could you check that with the next realease of the plugin (1.0.15) ?
Comment 13 Quality Engineering 2014-05-20 02:49:28 UTC
Integrated into 'main-silver', will be available in build *201405200001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/2c6cd7481a42
User: Emmanuel Hugonnet <ehsavoie@netbeans.org>
Log: Fixing #244427: Locking the domain combo box as domain is not supported for development.