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.
nb 7.3 fails to successfully start gfv301, nb712 does start gfv301. nb73 pops up dialog gfv301 start failed at about 70 second. I have many apps - around 26 apps and startup normally takes around 2 minutes to fully complete. works fine with nb712; nb712 is running jdk1.7.0_04 nb 7.3 is running jdk1.7.0_11. to attach log file of startup. Product Version: NetBeans IDE 7.1.2 (Build 201204101705) Java: 1.7.0_04; Java HotSpot(TM) 64-Bit Server VM 23.0-b21 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) User directory: C:\Users\emiddio\.netbeans\7.1.2 Cache directory: C:\Users\emiddio\.netbeans\7.1.2\var\cache Product Version: NetBeans IDE 7.3 (Build 201302132200) Java: 1.7.0_11; Java HotSpot(TM) 64-Bit Server VM 23.6-b04 Runtime: Java(TM) SE Runtime Environment 1.7.0_11-b21 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb) User directory: C:\Users\emiddio\AppData\Roaming\NetBeans\7.3 Cache directory: C:\Users\emiddio\AppData\Local\NetBeans\Cache\7.3
Created attachment 131804 [details] gfv301 startup log that fails with nb73
Created attachment 131805 [details] nb712 success gfv301 startup log
Created attachment 131818 [details] GlassFish 3.0.1 server log. For me it works with empty domain. Product Version: NetBeans IDE 7.3 (Build 201302132200) Java: 1.7.0_15; Java HotSpot(TM) 64-Bit Server VM 23.7-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_15-b03 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
If my domain did not have any applications to start up it would work for me also. It is some kind of timeout issue. Like i said - around 70 seconds it times out, it take around 2+minutes - 120+ seconds to start up all the applications.
But when it times out it also stops the glassfish startup.
OK, I can try to check what's going on. We can try to fix this in 7.3.1.
How can we cover this with automated tests to make sure this does not regress again?
Startup code was completely rewritten in 7.3 and we used 3.1.2 and 3.1.2.2 servers to test it. There is one check that can detect that 3.1 server is still starting up but looks like it does not work for 3.0.1. Unfortunately those things are hard to test. I had to modify glassfish sources to make it start a bit longer. Looks like we'll have to run Tooling SDK tests against more GlassFish versions and implement something on plugin level too. Now back to this issue. I need fine logs from NetBeans plugin. Please add "-J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0" into netbeans_default_options in netbeans.conf and send me netbeans logs related to GlassFish startup. It may show me enough to see what was going on.
why dont you just let me configure a timeout - in the server properties panel ? i know with my 26 current apps it takes around 2-3+ minutes to start and i can just set the timeout longer. it never hangs - the output window continues to show output during the startup - it just takes a long time. Thanks
Integrated into 'main-golden', will be available in build *201303112300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/11489e81b1fa User: Tomas Kraus <TomasKraus@netbeans.org> Log: #226610 - Startup timeout raised to 5 minutes #226301 - Shutdown timeout raised to 3 minutes
Please download http://bertram2.netbeans.org:8080/job/web-main-javaee7/149/artifact/nbbuild/NetBeans-dev-web-main-javaee7-149-on-20130311-full.zip and let me know it your problem is fixed now. I raised timeout to 5 minutes for 7.3.1 release. I can't do more now. In 8.0 there will be property in server properties.
I'm still missing fix test results. Unfortunately I can't reproduce this in my development environment.
Still have no response about testing an attempt to fix this issue. Please reopen this bug when you'll test it with latest build from http://bertram2.netbeans.org:8080/job/web-main-javaee7
i will test and update this issue when i get an opportunity - at my next server reboot.
I tested today - not a dev build, but the latest nb7.3patch1 version. Failed to start, timeout seems to be unchanged. If I have to test a dev build i will - inform if needed.
I may need FINEST logs from netbeans. Please add -J-Dglassfish.level=0 -J-Dorg.glassfish.tools.ide.level=0 into etc/netbeans.conf:netbeans_default_options and reproduce this issue with 7.3.1 build. attach NetBeans logs to this bug. Maybe it will show what's going wrong there.
Is there a chance to get those logs at the beginning of next week? We will have code freeze for 7.3.1 soon and I need to fix this issue ASAP.
i can do it this wkend. Need to know - is my 7.3 patch1 good enough or do i have tog use a dev build ? -Gary
You will need last dev build from http://bertram2.netbeans.org:8080/job/web-main-javaee7/ to be synchronized with my sources. But it's quite stable now.
data obtained, 4 logfiles to be uploaded. success logs using nb712/gfv301 fail logs using your nvdev/gfv301 -Gary
Created attachment 133636 [details] gfv301successfullStartup20130421log.txt
Created attachment 133637 [details] nb712Successfullgfv301startup20130421Log.txt
Created attachment 133638 [details] nbdevFail20130421log.txt
Created attachment 133639 [details] gfv301Faill20130421log.txt
This is interesting: Server gfv301 version response: V3 cannot process this command at this time, please wait FINEST [glassfish]: Server gfv301 locations response returned 3 records FINEST [glassfish]: Server gfv301 locations response message = V3 cannot process this command at this time, please wait%%%EOL%%% FINEST [glassfish]: Server gfv301 locations response Domain-Root_value = null FINEST [glassfish]: Server gfv301 locations response Base-Root_value = null INFO [glassfish]: gfv301 is not responding, killing the process. Looks like this 'please wait...' message is not the same as in gfv312 so it was not recognized properly.
Checked into GlassFish Tooling Library: --------------------------------------- changeset: 490:8dca4e51fca8 summary: Bug# 226610 - NB 7.3 fails to successfully start gfv301 changeset: 261:3ede71eb081e branch: 0.3-b036 summary: Bug# 226610 - NB 7.3 fails to successfully start gfv301 This should fix 'please wait...' message detection.
Checked into web-main: ---------------------- changeset: 250887:9c055fe62b71 branch: javaee7 summary: #226610 - NB 7.3 fails to successfully start gfv301 Unfortunately I have no chance to verify this locally. You will have to try it yourself.
Please try http://bertram2.netbeans.org:8080/job/web-main-javaee7/ build when build #251 is finished.
Fixed build is available on http://bertram2.netbeans.org:8080/job/web-main-javaee7/ I'm closing this bug. Please let me know if it's finally working for you.
tested; now works. -Gary
Integrated into 'releases', will be available in build *201304242201* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/9c055fe62b71 User: Tomas Kraus <TomasKraus@netbeans.org> Log: #226610 - NB 7.3 fails to successfully start gfv301
Integrated into 'main-golden', will be available in build *201304252301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/9c055fe62b71 User: Tomas Kraus <TomasKraus@netbeans.org> Log: #226610 - NB 7.3 fails to successfully start gfv301