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 tried to start a JBoss 4.0.3RC1 from Netbeans. The server is successful started but in a server status window I can see error "timeout error". So server is running but I cannot stop it. My JDK is 1.5.0_04. In log file I can see next lines : Failed to initalize plugin: org.jboss.logging.Log4jLoggerPlugin@1b4434 jakub
The problem is with your JBoss 4.0.3RC1,it's only development version,not final.Try to use JBoss 4.0.1SP1,it works OK.
Upgrading to P2. It is important feature. Could engineers please check if it is NB bug or JBoss bug?
Today I try this new plugin with OS Fedora Core 4 with JDK 1.5.0_04. I cannot add new server in runtime panel because I get some exceptions (see log file).
Created attachment 23218 [details] message log from Fedora Core 4
Please file last problem in separate issue (with description starting from beginning without usage of information from this bug). Do not mix 2 problems together. Thanks! This issue will be only about original problem.
I need more infromation bcs I cannot reproduce this problem and it can be caused by a number of reasons. 1. I increased timeout from 5 to 15 minutes (see issue 59272). This may help to avoid the problem in the first place. 2. The IDE will not allow you to stop the server if it thinks it is stopped. Did you try to refresh the server status (you can do so by clicking "Refresh" in the popup menu of jboss node). If you tried this did it work? (note issue 61477, not 100% reproducible but some users cannot refresh status of running server). 3. Which config of jboss did you use? Minimal config cannot be stopped, it is already filed as issue 59766.
add 1) This issue is not problem for me, my startup time is lower than one minute add 2) I have a same problem but not always. Sometime I can see "stopped" but in output window I can see that server is running. add 3) I`m using ejb3 configuration - it is new possibility for version 4.0.3RC1
I just tested with 4.0.3 RC1 and also with the newer RC2. Both work for me, but I could not reproduce 61477 either. Anyway, from your description it sounds like a duplicate of 61477. Using ejb3 should not matter for start/stop. I fixed it over the weekend. Can you get a new build and verify that you problem is also fixed? If not please reopen this issue. Thanks. *** This issue has been marked as a duplicate of 61477 ***