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.
When I have an application deployed into my Glassfish V3 which was installed by NetBeans 6.8 and the Glassfish is not running I go into Services tab and right click on Glassfish V3 and select Start, the glassfish start to run and I can see in the output that the server start loading and then start loading my deployed application but after about 1.5 minutes I get a message box from the IDE saying "Glassfish V3 Domain Start Failed". The thing is it has not failed, I think it's just a timeout expire.
I want to add that the Glassfish V3 domain did load perfectly fine, the application is working even when NetBeans IDE show the failed dialog. To repo this problem either use exist EJB project which take at least 1 minute to load or create a new one and add about 20 EJB entities and 20 session beans it should do the trick.
Are there any other apps deployed onto the instance that is having trouble starting? Please attache the log file for the server that is having a problem starting.
The point is there is no problem for the server to startup. It start perfectly and everything is working. The only problem (I think) is that when I start the server from within NetBean 6.8 it has a timeout to the server startup process and if the timeout expire NetBeans show a message "Glassfish V3 Domain Start Failed" but the glassfish domain start just fine. To work around the issue I undeploy my application, start the server again (which now start very quickly because no application is deployed) and then deploy my application.
What happens if you... 1. deploy your app from inside NB, then 2. stop the server from NB, then 3. start the server from the command-line using asadmin? Again: please attach the server log... It should not take minutes for a server to start when there is only a single app deployed... That is what I would consider to be the 'real issue' in this situation. Resolving that problem will eliminate the timeout problem.
Created attachment 99590 [details] Log files collected from NetBeans as well as Glassfish V3 The zip file contain 4 log files: netbeans_output-start_server_then_deploy.txt - contain log output from netbeans output panel. It show the log of starting Glassfish V3 without applications then deploy my application to the running server netbeans_output-start_already_deployed.txt - contain log output from netbeans output panel. It show the log of starting Glassfish V3 with already deployed application. This log cuts in the middle when NetBeans show the "Glassfish V3 Domain Start Failed" message. server.log and jvm.log - contain logs of Glassfish V3 (from domains/domain1/logs folder). Is show the log of starting the Glassfish V3 with already deployed application. It contain the same log as netbeans_output-start_already_deployed.txt but continue with the full load of the application which show that Glassfish load the application just fine, it was NetBeans who decide the domain start failed.
Created attachment 99591 [details] Glassfish Log of starting from asadmin This is the server.log of Glassfish with deployed application starting up from asadmin command line.
Please see the details of the files for info about each file in the archive. I've start the domain with the deployed application from asadmin in command line and it start just fine. The wired thing is that from command line it take 20 seconds to start the domain with the deployed app and from within NetBeans it take 72 seconds to start the deployed app. It is exactly the same app in the same domain. The "Glassfish V3 Domain Start Failed" message show up after minute and ten seconds (70 seconds). Ido.
Thanks for the attachments. I am glad to see that starting GF from the command-line is ok. This may be related to bug 180801.
Hi, Now that you show me bug 180801 it really look like the issue. I was trying to understand if hibernate is issuing "bad" SQLs to the database so I turn the hibernate log on and call that used to take 2-3 seconds (which was consider long) took 2 minutes. I'm not kidding, 2 minutes. It took a while but in the end I understand that it was the log that do the problem, not hibernate. I does see any resolution to the other bug, what do you suggest to do now?
(In reply to comment #9) > > I does see any resolution to the other bug, what do you suggest to do now? I just got actionable data from the filer of that other issue today. I will be testing NB 6.9 to see if this issue exists in that environment. If the issue still happens in that environmnet, I will start to dig up a fix. If the issue doesn't exist in a 6.9/GlassFish 3.0.1/Windows environment, I will update these issues with my findings so others can validate that changing to NetBeans 6.9 and GlassFish Server 3.0.1 is effective for them. I may know later today... otherwise expect to hear something by Tuesday afternoon (Pacific Daylight Time)
Just like to close this issue by saying thank you and that I use the Dev build which include the fix and now things work a lot faster (20 seconds instead of 80). Thank you, Ido
Netbeans 7 RC2 Glassfish 3.1 Glassfish start is killed by start_timeout after 120 sec. Netbeans 6.9.1 dont kill glassfish after Start_Timeout. but Netbeans 7 RC2 kill the start of Glassfish. Make please this configurable.
Please try a recent dev build of NB... See issue 197375 for details. The behavior that you describe sounds like it might be addressed by the changes integrated to resolve that issue. (In reply to comment #12) > Netbeans 7 RC2 > Glassfish 3.1 > > Glassfish start is killed by start_timeout after 120 sec. > Netbeans 6.9.1 dont kill glassfish after Start_Timeout. but Netbeans 7 RC2 kill > the start of Glassfish. > > Make please this configurable.
*** This bug has been marked as a duplicate of bug 197375 ***