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.
The NetBeans Plugin for JBoss EAP is not working when using an EAP instance that has patches applied. See https://access.redhat.com/solutions/1409903 and https://access.redhat.com/solutions/786133 The links refer to 6.3, but the same issue is with 6.4 and JDK 8.
Netbeans 8.1,Jdk 1.8 for Server and IDE.
There is no plugin for JBoss EAP. There is plugin for JBoss Application Server (which is not developed anymore, the last version was 7.1.1) and there is plugin for WildFly (which you might try for EAP). Which one do you use?
Awaiting user response.
I used the JBoss Application Server Plugin. In the meantime I was able to make good use of the JBoss Maven Plugin and NetBeans Custom Actions to start/stop and deploy from within NetBeans IDE. The Wildfly Plugin is not working at all with JBoss EAP 6. I will try it with JBoss EAP 7, which is based on Wildfly 10. So maybe this will work.
(In reply to t_m_w from comment #4) > I used the JBoss Application Server Plugin. It is plugin for "JBoss Application Server" which is a lot different from EAP. I would be surprised if this would work. > In the meantime I was able to make good use of the JBoss Maven Plugin and > NetBeans Custom Actions to start/stop and deploy from within NetBeans IDE. > The Wildfly Plugin is not working at all with JBoss EAP 6. Wildfly is much more similar to EAP. Please report what is actually not working. > I will try it with JBoss EAP 7, which is based on Wildfly 10. > So maybe this will work.
Could you be a little more descriptive of your issue ? Maybe the admin port is incorrectly set ? The plugin in the nightly build should work with EAP 6.x and 7
After registering the JBoss EAP 6.4.0 I start the Server via the plugin. It is starting up, but the plugin does not recognize it, when the server is up and running. NetBeans still says "Starting JBoss Application Server in Debug Mode" and the hourglass is displayed at the entry below the "Servers" Node. No restart, stop etc is possible via the NetBeans Plugin. I just tried it again with the current nightly NetBeans Build. After exactly 20 Minutes "Starting of server JBoss Application Server in debug mode has timed-out." appears. Here are the Java Options etc. used to start the JBoss EAP Server: Calling "D:\jboss\jboss-eap-6.4\bin\standalone.conf.bat" "JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djboss.server.default.config=standalone-full.xml -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n" Setting JAVA property to "C:\Program Files\Java\jdk1.8.0_60\bin\java" =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: "D:\jboss\jboss-eap-6.4" JAVA: "C:\Program Files\Java\jdk1.8.0_60\bin\java" JAVA_OPTS: "-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -Djboss.server.default.config=standalone-full.xml -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n" =============================================================================== And these are the Management Ports: <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
Attaching the standalone-full.xml is a better way as the ports opened depend also on the <management> part. Also which version of Netbeans are you using ? What admin port have you configured in Netbeans ?
Created attachment 159947 [details] Standalone Full as requested. Removed all sensitive lines.
Product Version: NetBeans IDE Dev (Build 201606020002) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb) Did not change the management port from within netbeans.
Netbeans JBoss Plugin JMX Port: 9999 HTTP Port: 8080
I'm waiting for a Windows VM so I could test the plugin. https://netbeans.org/bugzilla/show_bug.cgi?id=262252 seems related and I'm not sure if the patch was applied in last night build. I'll check tomorrow morning nightly too.
Reporter, can you test with the latest dev build?
Created attachment 160013 [details] Screenshot showing Plugin does not recognize already started server. Unfortunately the Bug is not fixed. A started JBoss EAP is still not recognized. NB run config: Product Version: NetBeans IDE Dev (Build 201606090002) Java: 1.8.0_60; Java HotSpot(TM) 64-Bit Server VM 25.60-b23 Runtime: Java(TM) SE Runtime Environment 1.8.0_60-b27 System: Windows 7 version 6.1 running on amd64; Cp1252; de_DE (nb) User directory: C:\Users\...\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\...\AppData\Local\NetBeans\Cache\dev
After test repopened.
Created attachment 160015 [details] After running (deploy on run) an ear file from within NetBeans One additional note: I have a project that produces an ear file. Under the netbeans run configuration there is "Deploy on save" checked and the registered server is selected. If I run this project, the ear file is deployed to the server, even though the plugin did not recognize it as started. After the deployment the plugin strangely recognizes that the server is started! Enclosed screenshot shows this. Only error in this case: in the netbeans main frame status line there is still the message "Starting JBoss Application Server in Debug Mode" visible and after the time out the message "Starting of server JBoss Application Server in debug mode has timed-out".
Yes I've just seen the behaviour on Windows. I'll try to debug on a VM
As reported earlier, Netbeans does not work with Patched EAP versions, because of corruption of original zip files during patch. Netbeans should therefore use patched jars instead, taken from the .overlays folder inside Jboss modules. Netbeans is not even able to add a new instance of Patched EAP due to the following error: Caused: org.openide.filesystems.FSException: Error in JAR file c:PATH_TO_JBOSS\jboss-eap-6.4\modules\system\layers\base\org\jboss\as\server\main\jboss-as-server-7.5.0.Final-redhat-21.jar: error in opening zip file at org.openide.filesystems.JarFileSystem.setJarFile(JarFileSystem.java:310) at org.openide.filesystems.JarFileSystem.setJarFile(JarFileSystem.java:259) [catch] at org.netbeans.modules.j2ee.jboss4.ide.ui.JBPluginUtils.getVersion(JBPluginUtils.java:812) at org.netbeans.modules.j2ee.jboss4.ide.ui.JBPluginUtils.getServerVersion(JBPluginUtils.java:779) at org.netbeans.modules.j2ee.jboss4.ide.ui.JBPluginUtils.isGoodJBServerLocation(JBPluginUtils.java:448) at org.netbeans.modules.j2ee.jboss4.ide.ui.JBPluginUtils.getRegisteredDomains(JBPluginUtils.java:313) at ....
This patching jars issue is not related, please open a new bug for it.
Sorry wrong windows
Confirmed vor Netbeans 8.2 RC (with EAP 6.3, 6.4, OSX, JDK7/8)
The issue is in the patching mechanism of EAP which disables jars that are overridden in the layers but the current plugin doesn't have an updated classpath.
Is this issue fixed? I face this issue with Netbeans 8.2, JBOSS EAP 6.4, JDK 1.7. Issue occurs even if ports mentioned while adding are same as ports inside standalone xml. Setting Tool -> Options -> Proxy Settings to 'No Proxy' doesn't help. Setting -> Right click on server -> Properties -> Platform -> 'Use IDE proxy settings' -> unchecked doesn't help
No there was no progress on this. Ports are not the issue, issue is the classpath because the jars are no longer located where the plugin looks for them.
@ehsavoie: I add my JBOSS EAP server as Wildfly server. Only issue I face is Netbeans does not recognize that server is started and times out after some time. But in fact server is running in the background. This is the same issue which is reported in second attachment (Screenshot showing Plugin does not recognize already started server)
In which case it is not linked to patches so please don't pollute this issue and create a new one. There is currently an issue with EAP 6 because we can't specify the protocol when connecting to it and it seems that there is a regression on this. But this is the WildFly plugin ;) so while I test against WF 8.2.1, 9.0.2, 10.1 and even 11 dev I can't also check all EAP releases (even if it works on EAP 7.0 and should also work on EAP 7.1). So please create a new bug entry, test with the nightly build with debug traces for the plugin and attach the log files (netbeans mostly) as they have more traces and I might take a look at it.