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.
I have installed the latest wildfly plugin on the latest netbeans and when I click "Run File" on a simple jsp page WildFly is started and I can see the following maven log statements in the console: NetBeans: Deploying on WildFly Application Server profile mode: false debug mode: false force redeploy: true but the application is not getting deployed and no browser window opens up. This is a maven app, the operating system is Fedora 19 and running java -version prints: java version "1.7.0_55" Oddly enough, using the exact same components (jdk, Netbeans, plugin) seems to be working just fine on a Ubuntu 12.04 machine!
Almost exactly same problem. BUT -- I have my desktop/workstation working fine and my personal laptop that doesn't work. Both running Fedora 20 (64bit). I just re-ran across this problem after getting wildfly 8.1.0Final on my laptop. In my case I am using a simple JSF app -- in fact the one generated by the Netbeans 'New Web App' wizard thing w/o any modifications. The NB built war (on my laptop) will deploy fine via WildFly admin console. Just gives this (when I run from NB): ant -f /home/fwelland/NetBeansProjects/FunWithSessions -Dbrowser.context=/home/fwelland/NetBeansProjects/FunWithSessions -DforceRedeploy=false -Ddirectory.deployment.supported=true -Dnb.wait.for.caches=true -Dnb.internal.action.name=run run init: deps-module-jar: deps-ear-jar: deps-jar: library-inclusion-in-archive: library-inclusion-in-manifest: compile: compile-jsps: /home/fwelland/NetBeansProjects/FunWithSessions/nbproject/build-impl.xml:1048: Deployment error. See the server log for details. BUILD FAILED (total time: 0 seconds)
Could you provide the following informations : - plugin version - java version - wildfly and netbeans log files. Also were the netbeans installations the same (it terms of other plugins) ?
I hammered on this again. I found a few things: For starters I have jumping up the WildFly 8.1 versions from cr1, cr2, and now Final. Normally when I do this, I delete the server from NB and add it back in. On the offending machine (my laptop) I did this; after unzipping WF Final and removing my WF cr1 dir. Tonight I notices that one of the server properties -- the important one -- path to the domain xml (in my case just standalone.xml) still referenced cr1. I know I created the server again -- but I didn't do the browse button on the domain -- just saw stuff and assumed it was correct. I doubt it was. I think an issue that caused this to be sticky was that I had a simple NB jsf/web app open whose 'run' config was pointing to Wildfly. NB gave me a warning about his as I deleted the server instance; i dismissed it and moved on. Today, while I was trouble shooting, I decide to point my 'run' config to GF 4 and make sure there wasn't something inherent in the project causing this. That worked just fine. Then I explored the WF server config and saw the mis-config. Deleted it again recreated the server; noting the xml path was OK; updated the project back to WF and everything worked. So really a mis-config on my part. But I will say the UI & Wizards didn't help prevent it -- maybe some bloody words on the server properties dialog when the xml isn't located in the specified path or something simple... As for the other working machine -- since I prototype and poc on my laptop -- it is really likely I didn't version jump WF on that workstation. I just rolled out a 8.1 final and configed the server in NB and all was well.... One key tip that also helped me take a second look at the server properties was the IDE log have NPE's while attempting to locate the WF configuration.
Thank you very much for this information !! I'll put a warning if both path differ because this might be wanted (you can use a configuration file outside the installation dir.
Not working for me I'm afraid..tried removing and re-adding the server and made sure the paths are all correct. When I run a "Run File" the last lines I see in the console are: NetBeans: Deploying on WildFly Application Server profile mode: false debug mode: false force redeploy: true and then nothing happens.. :) The NB "About" page shows the following: Product Version: NetBeans IDE 8.0 (Build 201403101706) Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 1.1 Java: 1.7.0_55; OpenJDK 64-Bit Server VM 24.51-b03 Runtime: OpenJDK Runtime Environment 1.7.0_55-mockbuild_2014_04_16_06_38-b00 System: Linux version 3.14.4-100.fc19.x86_64 running on amd64; UTF-8; en_GB (nb) User directory: /home/savvas.andreas/.netbeans/8.0 Cache directory: /home/savvas.andreas/.cache/netbeans/8.0
Savvas can you copy paste wildfly logs and also netbeans logs. Could you check throught Wildfly cli or web console that there is no application with the same name already in there. There were some incoherence of the status of an application between cli and fs so it might be that one (do't know if it is in 8.1). Also could you check that you are using tee 1.0.16 version of the plugin ?
So I did maybe a dozen or 2 'Run' operations last night (simple toy WAR). I would say 8 of 10 worked. The other failures looked like what we/i saw prior. I could immediately re-run and it would work. So maybe there is an issue still lurking. Here are my vitals: [fwelland@weedeater ~]$ uname -a Linux weedeater 3.14.5-200.fc20.x86_64 #1 SMP Mon Jun 2 14:26:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Product Version: NetBeans IDE 8.0 (Build 201403101706) Updates: NetBeans IDE is updated to version NetBeans 8.0 Patch 1.1 Java: 1.7.0_60; Java HotSpot(TM) 64-Bit Server VM 24.60-b09 Runtime: Java(TM) SE Runtime Environment 1.7.0_60-b19 System: Linux version 3.14.5-200.fc20.x86_64 running on amd64; UTF-8; en_US (nb) User directory: /home/fwelland/.netbeans/8.0 Cache directory: /home/fwelland/.cache/netbeans/8.0 My WildFly Plugin is: Version: 1.0.16 Source: Plugin Portal Having said all that -- I just hammer the green run button about 8 times with same WAR (first time started wildfly) and it worked fine each time... Last night I was actually changing code and running...
Like I said there is a bug lurking in Wildfly that may create this if the war is deployed as an archive and also by copy / paste of the exploded war. Maybe this is what is happening throught some execution path (the plgin being just an implementation I don't know how each path is processed from the IDE itself).
Hi ehsavoie, Thanks very much for looking into this. Below is a copy of the wf log statements that I see (don't worry about the app related stuff, been experimenting with javaee7 a bit...): JAVA_OPTS already set in environment; overriding default settings with values: -Xms1024m -Xmx2048m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,localhost.localdomain -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final JAVA: /usr/lib/jvm/java/bin/java JAVA_OPTS: -XX:+UseCompressedOops -Xms1024m -Xmx2048m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,localhost.localdomain -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone ========================================================================= 23:01:12,753 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final 23:01:12,920 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final 23:01:12,979 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final "WildFly" starting 23:01:13,915 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) 23:01:13,931 INFO [org.xnio] (MSC service thread 1-13) XNIO version 3.2.0.Final 23:01:13,938 INFO [org.xnio.nio] (MSC service thread 1-13) XNIO NIO Implementation Version 3.2.0.Final 23:01:13,960 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem. 23:01:13,977 INFO [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem 23:01:13,978 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main] 23:01:13,979 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem 23:01:13,986 INFO [org.jboss.as.security] (MSC service thread 1-14) JBAS013170: Current PicketBox version=4.0.20.Final 23:01:13,988 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem 23:01:14,046 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension 23:01:14,053 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final) 23:01:14,068 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.0.Final 23:01:14,068 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) 23:01:14,086 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2 23:01:14,105 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017502: Undertow 1.0.0.Final starting 23:01:14,105 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1) 23:01:14,107 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-11) JBAS010417: Started Driver service with driver-name = mysql 23:01:14,113 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017502: Undertow 1.0.0.Final starting 23:01:14,123 INFO [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service 23:01:14,125 INFO [org.jboss.as.mail.extension] (MSC service thread 1-14) JBAS015400: Bound mail session [java:jboss/mail/Default] 23:01:14,219 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017527: Creating file handler for path /home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/welcome-content 23:01:14,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server. 23:01:14,239 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017531: Host default-host starting 23:01:14,290 INFO [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080 23:01:14,379 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) JBAS016330: CORBA ORB Service started 23:01:14,393 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone/data/messagingjournal,bindingsDirectory=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone/data/messagingbindings,largeMessagesDirectory=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone/data/messaginglargemessages,pagingDirectory=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone/data/messagingpaging) 23:01:14,395 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock 23:01:14,427 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221012: Using AIO Journal 23:01:14,472 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 58) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability. 23:01:14,475 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-9) JBAS015012: Started FileSystemDeploymentService for directory /home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone/deployments 23:01:14,482 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015876: Starting deployment of "javaee7-1.0-SNAPSHOT.war" (runtime-name: "javaee7-1.0-SNAPSHOT.war") 23:01:14,505 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) JBAS016328: CORBA Naming Service started 23:01:14,505 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-12) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] 23:01:14,506 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-14) JBAS010400: Bound data source [java:/MySQLDS] 23:01:14,510 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support CORE 23:01:14,520 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support AMQP 23:01:14,523 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support STOMP 23:01:14,604 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock 23:01:14,604 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock 23:01:14,667 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.3.Final 23:01:14,894 INFO [org.jboss.as.jpa] (MSC service thread 1-13) JBAS011401: Read persistence.xml for local-mysql 23:01:15,001 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 59) JBAS011409: Starting Persistence Unit (phase 1 of 2) Service 'javaee7-1.0-SNAPSHOT.war#local-mysql' 23:01:15,010 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 59) HHH000204: Processing PersistenceUnitInfo [ name: local-mysql ...] 23:01:15,011 INFO [org.jboss.messaging] (MSC service thread 1-5) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor 23:01:15,011 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor 23:01:15,060 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live 23:01:15,060 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 124) [cf378181-c309-11e3-b9b0-2fe97add731c] 23:01:15,078 INFO [org.hibernate.Version] (ServerService Thread Pool -- 59) HHH000412: Hibernate Core {4.3.1.Final} 23:01:15,080 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 59) HHH000206: hibernate.properties not found 23:01:15,081 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 59) HHH000021: Bytecode provider name : javassist 23:01:15,086 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory 23:01:15,087 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 23:01:15,135 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-10) JBAS010406: Registered connection factory java:/JmsXA 23:01:15,168 INFO [org.hornetq.ra] (MSC service thread 1-10) HornetQ resource adaptor started 23:01:15,168 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-10) IJ020002: Deployed: file://RaActivatorhornetq-ra 23:01:15,170 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA] 23:01:15,170 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 23:01:15,200 INFO [org.jboss.weld.deployer] (MSC service thread 1-16) JBAS016002: Processing weld deployment javaee7-1.0-SNAPSHOT.war 23:01:15,245 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-16) HV000001: Hibernate Validator 5.0.3.Final 23:01:15,298 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named CollectionMappingService in deployment unit deployment "javaee7-1.0-SNAPSHOT.war" are as follows: java:global/javaee7-1.0-SNAPSHOT/CollectionMappingService!com.cos.javaee7.jpa.collectionmapping.service.CollectionMappingService java:app/javaee7-1.0-SNAPSHOT/CollectionMappingService!com.cos.javaee7.jpa.collectionmapping.service.CollectionMappingService java:module/CollectionMappingService!com.cos.javaee7.jpa.collectionmapping.service.CollectionMappingService java:global/javaee7-1.0-SNAPSHOT/CollectionMappingService java:app/javaee7-1.0-SNAPSHOT/CollectionMappingService java:module/CollectionMappingService 23:01:15,299 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named TrackService in deployment unit deployment "javaee7-1.0-SNAPSHOT.war" are as follows: java:global/javaee7-1.0-SNAPSHOT/TrackService!com.cos.javaee7.jpa.collectionmapping.service.TrackService java:app/javaee7-1.0-SNAPSHOT/TrackService!com.cos.javaee7.jpa.collectionmapping.service.TrackService java:module/TrackService!com.cos.javaee7.jpa.collectionmapping.service.TrackService java:global/javaee7-1.0-SNAPSHOT/TrackService java:app/javaee7-1.0-SNAPSHOT/TrackService java:module/TrackService 23:01:15,299 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named InheritanceTestService in deployment unit deployment "javaee7-1.0-SNAPSHOT.war" are as follows: java:global/javaee7-1.0-SNAPSHOT/InheritanceTestService!com.cos.javaee7.jpa.inheritance.service.InheritanceTestService java:app/javaee7-1.0-SNAPSHOT/InheritanceTestService!com.cos.javaee7.jpa.inheritance.service.InheritanceTestService java:module/InheritanceTestService!com.cos.javaee7.jpa.inheritance.service.InheritanceTestService java:global/javaee7-1.0-SNAPSHOT/InheritanceTestService java:app/javaee7-1.0-SNAPSHOT/InheritanceTestService java:module/InheritanceTestService 23:01:15,434 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: javaee7-1.0-SNAPSHOT.war 23:01:15,455 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 2.1.2 (Final) 23:01:15,481 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016008: Starting weld service for deployment javaee7-1.0-SNAPSHOT.war 23:01:15,580 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 59) JBAS011409: Starting Persistence Unit (phase 2 of 2) Service 'javaee7-1.0-SNAPSHOT.war#local-mysql' 23:01:15,634 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 59) HCANN000001: Hibernate Commons Annotations {4.0.4.Final} 23:01:15,811 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 59) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect 23:01:15,948 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 59) HHH000397: Using ASTQueryTranslatorFactory 23:01:16,084 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingDepartment] 23:01:16,087 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyDepartment] 23:01:16,087 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Employee] 23:01:16,088 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Company] 23:01:16,088 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyEmployee] 23:01:16,088 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Track] 23:01:16,089 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingEmployee] 23:01:16,247 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 59) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect 23:01:16,249 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingDepartment] 23:01:16,249 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyDepartment] 23:01:16,249 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Employee] 23:01:16,249 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Company] 23:01:16,250 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyEmployee] 23:01:16,250 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Track] 23:01:16,250 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingEmployee] 23:01:18,071 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingDepartment] 23:01:18,073 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyDepartment] 23:01:18,074 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Employee] 23:01:18,075 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Company] 23:01:18,075 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyEmployee] 23:01:18,076 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Track] 23:01:18,077 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingEmployee] 23:01:20,566 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingDepartment] 23:01:20,567 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyDepartment] 23:01:20,567 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Employee] 23:01:20,568 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Company] 23:01:20,569 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyEmployee] 23:01:20,569 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Track] 23:01:20,570 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingEmployee] 23:01:20,572 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingDepartment] 23:01:20,573 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyDepartment] 23:01:20,573 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Employee] 23:01:20,574 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Company] 23:01:20,575 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [EntityKeyEmployee] 23:01:20,575 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [Track] 23:01:20,576 INFO [org.hibernate.id.enhanced.TableGenerator] (ServerService Thread Pool -- 59) HHH000398: Explicit segment value for id generator [hibernate_sequences.sequence_name] suggested; using default [MapMappingEmployee] 23:01:21,738 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-14) Deploying javax.ws.rs.core.Application: class com.cos.javaee7.rest.RESTConfiguration$Proxy$_$$_WeldClientProxy 23:01:21,782 INFO [org.wildfly.extension.undertow] (MSC service thread 1-14) JBAS017534: Registered web context: /javaee7-1.0-SNAPSHOT 23:01:21,845 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "javaee7-1.0-SNAPSHOT.war" (runtime-name : "javaee7-1.0-SNAPSHOT.war") 23:01:22,001 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 23:01:22,001 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 23:01:22,001 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 9482ms - Started 364 of 415 services (99 services are lazy, passive or on-demand) And below is the log statements I see in NB: INFO [org.netbeans.modules.web.jsf.JSFConfigUtilities]: Total time spent = 19 ms INFO [org.netbeans.modules.web.jsf.JSFFrameworkProvider]: Total time spent=21 ms INFO [global]: JAVA_OPTS=-Xms1024m -Xmx2048m -XX:MaxPermSize=256m -server -Dhttp.nonProxyHosts=localhost,127.0.0.1,localhost.localdomain -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.base.dir=/home/savvas.andreas/Software/Work/ApplicationServers/WildFly/wildfly-8.0.0.Final/standalone INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment] java.lang.NullPointerException at org.netbeans.modules.javaee.wildfly.config.WildflyDatasource.<init>(WildflyDatasource.java:83) at org.netbeans.modules.javaee.wildfly.config.xml.ds.WildflyDatasourcesHandler.endElement(WildflyDatasourcesHandler.java:112) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:609) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1781) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2957) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333) at javax.xml.parsers.SAXParser.parse(SAXParser.java:195) at org.netbeans.modules.javaee.wildfly.config.xml.ConfigurationParser.listDatasources(ConfigurationParser.java:81) at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.getDatasources(WildflyDatasourceManager.java:105) at org.netbeans.modules.javaee.wildfly.config.WildflyDatasourceManager.deployDatasources(WildflyDatasourceManager.java:111) 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) There's a np somewhere..not really sure the above is helpful at all but... It's doesn't look like there is another app with the same name and, yep, am using the version you mention: Version: 1.0.16 Source: Plugin Portal Cheers, Savvas
Looks like you have an issue with your MySQL Datasource. Could you past the Wildfly configuration for it please ? Could it be the same issue as in https://netbeans.org/bugzilla/show_bug.cgi?id=243502 ?
hmmm...when I run the following on a command line: mvn clean install wildfly:deploy the build completes successfully and I can access my application ok. In terms of configuring the data source I have the following things in place: In ${WF_HOME}/modules/com/mysql/main/ dir I have a module.xml with the following content: <module xmlns="urn:jboss:module:1.1" name="com.mysql"> <resources> <resource-root path="mysql-connector-java-5.1.29-bin.jar"/> </resources> <dependencies> <module name="javax.api"/> <module name="javax.transaction.api"/> </dependencies> </module> and in ${WF_HOME}/standalone/configuration/standalone.xml I have the following snippet related to the data source: <datasource jta="false" jndi-name="java:/jboss/datasources/local-mysql" pool-name="MySqlDs" enabled="true" use-ccm="false"> <connection-url>jdbc:mysql://localhost/javaee7</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <driver>mysql</driver> <security> <user-name>XXXXX</user-name> <password>XXXXX</password> </security> <validation> <validate-on-match>false</validate-on-match> <background-validation>false</background-validation> </validation> <statement> <share-prepared-statements>false</share-prepared-statements> </statement> </datasource> <drivers> <driver name="mysql" module="com.mysql"> <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class> </driver> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> </drivers>
I have an error with your configuration on 8.0.0 but it is working properly with 8.1.0.
Integrated into 'main-silver', will be available in build *201406220001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/e54b5d428c0f User: Emmanuel Hugonnet <ehsavoie@netbeans.org> Log: Bug #243974 : Adding a warning message if configuration file is not in installation dir.
Brilliant, thanks very much! I assume this applies to all platforms?
Currently only to te nightly builds. i need to make a release