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 downloaded 5.5 RC1. Added a new JBoss 4.0.4 server to Runtime -> Servers. I can start JBoss from NB, but once started NB seems totally unaware of it. It only enables the "Start" and "Start in Debug Mode" options (even though the server is already running, there should be a "Stop" option instead). I can easily check the server is running since View Admin Console works and opens the JBoss console. Working with any web app fails, since upon running it continously tries to start up JBoss (even though it's already running), which results in a startup error, since the port is already in use. In short, current state of JBoss support is very broken and you can't do any sort of meaningful work using JBoss as a target. I'm on NB 5.5 RC1, JDK 6.0, Win XP. Steps to reproduce: a) add a JBoss 4.0.4 instance b) start it c) create a brand new web app of any type, set JBoss as the deployment server d) press F6 to run, fails right away with error "Port <your JBOSS port #> is already in use", unable to deploy or run any app.
Created attachment 34864 [details] NB log
Stepane, can you look at this, please?
Do you use firewall? And if you do can you try to disable it and check whether you can still reproduce it? I have tried to enable my firewall and then it behaved the same way as you described.
I work at a corporation, I do not have control over my firewall or proxy. Everyone has to go through a proxy/firewall. As such, I cannot disable it. I have no such issues with Glassfish, which works perfectly fine with my corporate proxy/firewall settings.
I think Stepan was asking about a personal firewall on your machine, not the corporate proxy/firewall. Do you have a personal firewall such as Norton/Symantec or Windows firewall on your machine?
No. Even my Windows XP firewall is disabled. If I try to access Control Panel -> Windows Firewall I get a msg box saying Windows Firewall settings cannot be displayed because the associated service is not running. Do you want to start the Windows/Firewall/Internet Connection Sharing (ICS) service? which implies it is totally switched off by our IS team for our PCs.
Also, I just quickly checked my Proxy settings in NB and explicitly removes localhost from the list of domains (the "No Proxy for:" field in Options -> Proxy) localhost, 127.0.0.1
*** Issue 86419 has been marked as a duplicate of this issue. ***
Yeah, I meant the personal firewall. Well, now we know that firewall is not the problem. It seems that problem with the network connection could be the cause of this issue. For example if you start JBoss when you are connected to the network and if you then disconnect the JBoss will behave exactly the way you described. BTW, the same networking problems might be also caused by the DHCP server which uses dynamic IP allocation. Can you please check whether you will still be able to reproduce this issue when you are working without the network? I mean, disconnet your computer from the network, start the JBoss server and see whether it works or not.
Sorry, I just tried that, logged into my PC as Administrator, no network. Run NB directly from the /bin folder, everything behaved exactly the same. NB seemed totally unaware of when JBoss was up and running. I will attach the log.
Created attachment 34926 [details] Log when logged in without any network
I Did not mean to offend. I am glad the firewall was eliminated. Can we please remove the INCOMPLETE keyword from this now that you have a log?
I've added the INCOMPLETE keyword, because we still do not know what is the problem and the log file didn't help us so far. This, however, does not mean that it is not an issue. BTW, do you have a default JBoss intallation? Didn't you exclude the jmx-console during installation? You can check it by accessing http://localhost:8080/jmx-console when the JBoss is running?
Oh. I'm afraid I don't know much about your processes. When I click the link I get the JBoss JMX Management Console Page with this title JMX Agent View sun-ypsn00u7t2v
here's some other info, in case is helps. 1. I work remotely via vpn connection 2. I have jbos 4.0.4-GA 3. I can start jBoss from the IDE (when I first try to do it, the node is not enabled, but when I click away and back it enables). When I deploy the first time its like the ide looses its connection to jBoss so after than I can no longer work with the serverManager.
Same thing for me, I can access the JMX-Console without any issues while the server is running.
Oh, two more things. 1. Correction on #3. After I successfully start jBoss from server manager, the servermanager jboss node menu immediately does not recognize that it is started. The menu always has the Start option available, even after doing a refresh. 2. I am using jdk 1.6.0 and jBoss starts up with that. =============================================================================== . JBoss Bootstrap Environment . JBOSS_HOME: C:\Sun\jboss-4.0.4.GA\bin\\.. . JAVA: C:\Program Files\Java\jdk1.6.0\bin\java . JAVA_OPTS: -Dhttp.proxyHost=webcache.sfbay -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts="localhost*| 127.0.0.1*| *.central| *.sfbay| *.east| .sfbay.sun.com*| suntea.central.sun.com*|<local>*|localhost|127.0.0.1|sun-ypsn00u7t2v|192.168.0.11" -Dhttps.proxyHost=webcache.sfbay -Dhttps.proxyPort=8080 -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 . CLASSPATH: C:\Program Files\Java\jdk1.6.0\lib\tools.jar;C:\Sun\jboss-4.0.4.GA\bin\\run.jar . ===============================================================================
I tried on the exact same environment, and it works fine for me. I am running out of ideas. Two more questions: - is this 100% reproducible on your system, or does deployment sometimes succeed? - can you tried with the latest build of Java 6, i.e. build 100? Thanks, Petr.
Yes, this is 100% reproducible. The first deploy (or start) always works, but after that, it fails. I will try tomorrow with build 100 and let you know.
Same thing for me, fails 100% of the time. Maybe the only difference I can think of is that when I installed JBoss I did NOT choose the default installation options, but instead I installed it with the full "ejb3" profile (I think that's what it's called) since I wanted to start researching the JBoss Seam JSF/EJB3 integration framework. Maybe that type of JBoss installation is causing this?
To give you more info, here's it direct from the JBoss Seam installation docs: http://labs.jboss.com/portal/jbossseam/gettingstarted --------------------------------------------------------------------------- Getting Started with JBoss Seam Day 1: Install and try the examples * Ensure that you have JDK 5.0 or above and Ant 1.6 or above properly installed. * Download the JEMS installer for JBoss AS 4.0.4 and install it with the EJB 3.0 profile selected. Note: do not install any other version of JBoss, and do not try to install JBoss using the normal JBoss AS installer - Seam requires EJB 3.0 RC8 which is only currently available in the special JEMS Installer! --------------------------------------------------------------------------- This is how I installed it.
I guess, the full jboss installation (with ejb3) should work as well. I have patched the jboss module so that it provides some more info that could hopefully help us a bit. Please download the attached jar and replace the old one: <NB_INSTALLATION_DIR>/enterprise3/modules/org-netbeans-modules-j2ee-jboss4.jar The patch should add a new "Test" context menu action to the JBoss server node. Start the server and once the server is running, execute this action and then attach the IDE message log (<NB_USER_DIR>/var/log/messages.log) to this issue. The Test action should print some logging messages to that log. Please make sure (in the browser) that the server is really running before executing the Test action. BTW, can you also attach the full JBoss server output after starting the server? There is a Save As action in the output window. It would also help a lot if you could test the JBoss default installation, just to be sure that this issue is really not connected with the ejb3 extension somehow. Thank you
Created attachment 34943 [details] patch jboss module jar
Also, does this happen only on JDK 1.6, or also on 1.5? Can you please try? Thanks.
Created attachment 34980 [details] Log with updated JAR after running 'Test'
Created attachment 34982 [details] JBoss log after when starting up the server
Some good news (for a change). I downloaded the regular JBoss 4.0.4 installer (not the JEMS one they require for JBoss Seam) and installed a second instance on my PC using the 'default' profile. Registered it as a second JBoss server in NB, everything works fine with it as expected. So, it looks like something has changed in JBoss due to installing the EJB3 profile and now the integration between the two is broken. I am guessing you guys might need to get in touch with the JBoss team to figure out where the issue is, maybe it's a bug on their end, maybe it's something different NB has to do when running an ejb3 JBoss instance. Either way, it would be really great to figure this out, I am guessing many people will want to try the new EJB3.0 features of JBoss from NB and won't be able to do so.
To be precide, the exact version of JBoss I downloaded (the one that works) is: jboss-4.0.4.GA-Patch1-installer.jar from sourceforge
That's it. That's exactly what I installed though I did not realize it was special other than being a patch.
Lark, do be clear, you see the problem with jboss-4.0.4.GA-Patch1-installer.jar and the default setup?? Or does that work? Thanks, -- Marco
Sorry, that was very badly done. I still see this issue: 1. jboss-4.0.4.GA-Patch1-installer.jar (default setup) taken from the 4.0.4 release here: http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=16942&release_id=416591 2. If I install NB5.5 beta with the bundled jBoss, uninstall NB (leaving jBoss), and install NB Rc with VWP, it still failes. There are others in my group who do NOT see the issue with #2 (same jdk), so i will try again and get back to you.
Ok. I now have this working. I had to remove jdk 1.6.0-rc-b98 and install 1.5.0_06. Now, when I re-deploy it is successfull though the browser opens before deployment is complete. Refreshing the browser shows my app. I checked the promoted jdk 1.6 builds an the only one more recent than what I have is b99. I do not see a build100.
Ok. I have upgraded to jdk 1.6.0 build rc-101 and I can no longer reproduce this issue. Also, this time I did not see the browser lag (though my testing was not extensive).
Not the case for me. I upgraded to JDK 6.0 b101 as well and the behavior is exactly as it was. The initial JBoss 4.0.4 EJB3 installation (via their JEMS installer) still fails to integrate properly with NB, exact same issues as before. The second JBOss 4.0.4 Default installation (via their regular installeter) works fine, just as it did on the previous build of JDK 6.0. So, upgrading JDK 6.0 had zero effect on the issue for me.
jfurmankiewicz, are you sure that you really executed the 'Test' action or that you attached the correct messages.log file, I mean from the correct NetBeans user directory? The log should contain the following messages '------------- test started' ... '------------- test finished: failed' after executing the 'Test' action, but the one attached does not contain it. Unfortunately, I still cannot reproduce this issue. I've tried JDK 1.6.0-rc-b98, JBoss 4.0.4 EJB3 installation via the JEMS installer, JBoss from the JBoss NetBeans IDE but with no luck. Anyway, according to the attached JBoss log, it looks like this issue is most likely caused by some bug in your JBoss installation, see 08:03:34,964 INFO [[/web-console]] JSR77 J2EE Apps: Failed to init plugin, null 08:03:34,964 INFO [[/web-console]] JMS Message: Failed to init plugin, null 08:03:34,980 INFO [[/web-console]] SystemFolder: Failed to init plugin, null 08:03:34,980 INFO [[/web-console]] JSR77 EJBModules and EJBs: Failed to init plugin, null 08:03:34,980 INFO [[/web-console]] MonitorsFolder: Failed to init plugin, null 08:03:35,011 INFO [[/web-console]] JSR77 WebModule: Failed to init plugin, null 08:03:35,011 INFO [[/web-console]] JSR77 Domains and Servers: Failed to init plugin, null 08:03:35,292 INFO [[/web-console]] J2EEFolder: Failed to init plugin, null 08:03:35,292 INFO [[/web-console]] UCLs: Failed to init plugin, null 08:03:35,308 INFO [[/web-console]] MBeans: Failed to init plugin, null 08:03:35,308 INFO [[/web-console]] AOPFolder: Failed to init plugin, null When I start JBoss, I do not see these failures. Can you see these failures also when you start JBoss without the IDE - from the command line? Can you please try to following? 1) browse to http://localhost:8080/jmx-console/ 2) enter 'jboss.system:type=ServerConfig,*' to the ObjectName Filter text field and press the 'ApplyFilter' button 3) the response should look like this: jboss.system * type=ServerConfig 4) click the 'type=ServerConfig' link and check whether you can find 'ServerName' and 'ServerHomeDir' attribute names in the 'List of MBean attributes:' table Adding the INCOMPLETE keyword back, since it is still not clear whether it is really a NetBeans issue.
Created attachment 35077 [details] New log, reapplied JAR to 5.5 RC1, run 'Test'
Can you please check whether you can still see those 'INFO [[/web-console]]' failures even if you start JBoss without the IDE and also whether you can find 'ServerName' and 'ServerHomeDir' attribute names in the 'List of MBean attributes:' table as described in my last post? Thanks
Well, I deleted my old instance of the JBOSS JEMS install and installed it from scratch again. After re-registering it with NB, same exact thing happens. When I run "run.bat" directly from commandline outside of NB, I believe I see those errors as well (i.e. "INFO [[/web-console]]"). Not sure where that leaves us at this point. Maybe the issue is related to that "JEMS" install of JBoss? Does anyone know how the JEMS install of JBoss differs from their regular installer?
I was experiencing what may be the same problem. I compared the two installers and found that the old installer leaves all four checkboxes on the JMX Security screen unchecked by default. The new web installer checks them all by default. A little experimentation revealed that the magic checkbox is "Secure jmx-invoker-service". I installed JBoss 4.0.5 using the web installer and I unchecked just this one box. Now NetBeans 5.0 can start and stop JBoss. I hope this helps.
Mark, thanks for figuring out the issue. JBoss recommends that you use their JEMS installer, and with their latest, BETA2, NetBeans starts the server but then does not recognize it is running, unless it is installed with the "Secure jmx-invoker-service" unchecked (which most will not do by default). I would suggest we produce a hotfix for this if possible. /Brian
Unfortunately, I still cannot reproduce this issue. I've used the JEMS installer with all the JMX Security checkboxes selected and NetBeans do recognize that the server is running without any problem. Can someone who is still experiencing the issue try the following? > 1) browse to http://localhost:8080/jmx-console/ > 2) enter 'jboss.system:type=ServerConfig,*' to the ObjectName Filter text > field and press the 'ApplyFilter' button > 3) the response should look like this: > > jboss.system > > * type=ServerConfig > > 4) click the 'type=ServerConfig' link and check whether you can find > 'ServerName' and 'ServerHomeDir' attribute names in the 'List of MBean > attributes:' table > > Adding the INCOMPLETE keyword back, since it is still not clear whether it is > really a NetBeans issue.
I installed another instance of JBoss with the security boxes checked. I verified that the issue is reproducible with this instance. ServerName = default ServerHomeDir = C:\jboss\jboss-4.0.5.GA_test\server\default
Stephan, My values: ServerHomeDir C:\Program Files\jboss-4.0.4.GA-Beta2\server\default ServerName default I'm in Prague this week if you'd like to look at my system. /Brian
Thanks to Brian, I was finally able to reproduce the issue. After fixing the problem with recognition whether the server is running I had to fix also the problem that it was not possible to stop secured jboss installation from the IDE. F. Checking in src/org/netbeans/modules/j2ee/jboss4/JBDeploymentManager.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/JBDeploymentManager.java,v <-- JBDeploymentManager.java new revision: 1.15; previous revision: 1.14 done Checking in src/org/netbeans/modules/j2ee/jboss4/ide/JBStopRunnable.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/JBStopRunnable.java,v <-- JBStopRunnable.java new revision: 1.3; previous revision: 1.2 done Checking in src/org/netbeans/modules/j2ee/jboss4/util/JBProperties.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/util/JBProperties.java,v <-- JBProperties.java new revision: 1.3; previous revision: 1.2 done
Verified
The issue has been ported into the release551 branch. Checking in ide/JBStopRunnable.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/JBStopRunnable.java,v <-- JBStopRunnable.java new revision: 1.1.2.7.6.1; previous revision: 1.1.2.7 done Checking in util/JBProperties.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/util/JBProperties.java,v <-- JBProperties.java new revision: 1.1.2.4.20.1; previous revision: 1.1.2.4 done Checking in JBDeploymentManager.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/JBDeploymentManager.java,v <-- JBDeploymentManager.java new revision: 1.6.8.4.2.10.14.1; previous revision: 1.6.8.4.2.10 done