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.
Created attachment 113124 [details] Screenshot of error during running web project with GlassFish server. Product Version: NetBeans IDE Dev (Build 201111100600) Java: 1.6.0_26; Java HotSpot(TM) 64-Bit Server VM 20.1-b02-383 System: Mac OS X version 10.7.1 running on x86_64; MacRoman; en_US (nb) User directory: /Users/tester/.netbeans/dev Cache directory: /Users/tester/.netbeans/dev/var/cache Steps: 1. If GlassFish is already in Services view under Servers node, remove it by right click -> Remove In services view perform "Add Server..." action on Servers node 2. Select "GlassFish Server 3+", fill "GlassFish Default" name and click Next 3. Click "I have read and accept the license agreement...(click)" link and check that browser with GlassFish license is shown 4. Check the license check box 5. Click now enabled "Download Now..." button 6. Choose "GlassFish Server 3.1" in opened Select dialog and click OK 7. Wait until GlassFish is installed and click Next 8. Keep default values ("Register Local Domain", domain1, "Use default ports") and click Finish 9. Open "File|New Project" wizard 10. Choose "Java Web|Web Application" 11. Select "GlassFish Default" server as target server 12. Run project (F6) Error "GlassFish Server 3+ Default Start Failed /Users/tester/NetBeansProjects/WebApplication2/nbproject/build-impl.xml:721: Deployment error: GlassFish Server 3+ Default Start Failed See the server log for details." will appear.
It looks like you have another server running... GlassFish Non Default. What are the details about that server: install location, domain, ports, etc.
Please attach the server log for 'GlassFish Default'
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/4fba146ba82c User: vince kraemer <vkraemer@netbeans.org> Log: #204989 : error message for 'port occupied' case is pretty lame and doesn't point the user in the right direction.
Filer: I did find something worth adding a code change to address while I was trying to reproduce the issue. I am not sure that I reproduced your issue, though. Please provide answers to the questions that I raised, the logs I requested and take a more recent dev build for a spin to see if the change I made addresses the issue that you saw.
I tried reproduced this bug on the clean NetBeans but without succcess. Therefore I close this bug...