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.
If GF V3 was installed with jdk1.5 and later change to 1.6, it will fail to start during the application deployment Steps To Reproduce: 1. Install NB 6.7 Trunk (build 03/15/2009) with JDK 1.5.0_17 2. Start IDE with GF V3 experimental option 3. Create a web project (use all default) - the runtime server should be GF V3 Prelude 4. Register V3 by downloading it 5. Change the project runtime to V3 6. Run the project Note: A JDK error information dialog comes up (correct) 7. Change the V3 server jdk to jdk1.6.0_12 8. Rerun step 6 BUG: An failed to start server dialog comes up (even I already changed the jdk version to 1.6) If I rerun the project again, the server was successfully started; however, there are some red severe error appears in the server.log file
Created attachment 78259 [details] JDK error version dialog
Created attachment 78260 [details] Server failed to start dialog
Created attachment 78261 [details] server.log file
how did you perform step 7?
I have seen this type of behavior, but it is random. I cannot get this to happen every time... added keyword.
Step 7, I right-click at GlassFish V3 > select Properties > Java tab This problem is a little tricky to reproduce since after the 1st time, the problem seems go away. To reproduce it I guess you should to cleanup your system and start from scratch
yes. i did start from scratch and was not able to reproduce the issue.
I don't know if the steps below will help you any better to reproduce the problem, but I see it happens more often. I created 2 web projects with having JSF components, one to run with GF 2.1 and the other run with GF V3 1. I run project 1. After the the project run successfully, I go to the Servers List to stop V2.1 server 2. Before the V2.1 completely stop, I go to Project node and run project 2 with V3
davisn: regarding your last comment... So, if the v2.1 server hasn't finished... it hasn't released the ports... the v3 Prelude server is very likely to not be able to start because the ports are in-use (and that is actually the correct behavior).
I didn't make myself clear here, but there is a case even the V2.1 completely stopped, the V3 still failed to start. So you can wait for the V2.1 completely stop to execute project 2 on V3 to see if that dialog comes up. Usually if V3 or V3 Prelude failed to start because of port conflicts, it will show the result in the server.log file. This case I believe it might relate to something else but I don't know what is it.
see entries with the time stamp 2009-03-16T11:01:12.875-0700 in the server log.
please update the platform and OS fields to provide accurate information.
Update the OS platform since it happens more often on winXP
Created attachment 78275 [details] messages.log
hmm. have you reproduced this on other platform/OS combinations?
I will try on other OS and update the bug
Try on Solaris x86 but couldn't reproduce it The problem seem does not happen on other platform except window
it looks like a server is running and the user is trying to start a different server over the same ports. I am closing this one as invalid. Please reopen with detailed steps if you can reproduce this with 6.8