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.
Install a build of NB6 (say, netbeans-6.0-nightly-200705220000-standard-macosx-x86.tgz), taking all the defaults. Install a build of glassfish (say, glassfish-installer-v2-b41.jar), taking all the defaults. Start the IDE. Register the new App Server, taking all the defaults (i.e., do not fill in a password). Start the App Server. Sometimes it works (i.e., tabs show up in output window for "Java DB Database Process" and "Sun Java System Application Server"). More commonly, the App Server tab never appears. Sometimes neither tab appears. At this point, the IDE is totally hung. Nothing to do but "Force Quit" or "kill". It turns out that the app server is running, confirmed by running "ps" or browning to localhost:4848. It's just that the IDE doesn't know it. Looking at the app server log, I see the following: Application server startup complete. ..... SEC5046: Audit: Authentication refused for [admin]. |Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin. Looks like an authentication issue. Obviously, the IDE should report the exception, not hang.
Hang=p1 Seems to be a regression.
the data from the IDE's message.log and the GF server.log would be helpful
Created attachment 42666 [details] a thread dump
was able to duplicate. both threads are locked by j2eeserver module code. Advise and reassign
has work-around ... enter the valid password
workaround is not acceptable by design for some people: if you do not enter a password it is because you want to be prompted and that the password will not be stored on disk. We need to understand why the IDE/plugin did not popup the credential ui... It might be an issue on our side as well, so collaboration and ideas are welcome. Vince, can you try to see why the popup dialog did not appear?
Ludo, based on the stack trace it looks like it is my regression in j2eeserver, I am going to fix it. Lets wait for the fix and then we will see whether the problem will still persist.
F. Checking in org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/impl/ServerInstance.java,v <-- ServerInstance.java new revision: 1.80; previous revision: 1.79 done