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.
Your FAQ on Web Applications describes a known problem with running applets. I have been very frustrated with this bug. I am able to run and debug applets for a while and then it just stops. When i try to run an applet, the process shows up in the Execution window but no applet viewer shows up. After 3sec the process goes away. I am able to run my applets in an external browser but i cannot debug there so this is not acceptable. I have found that if i create a new applet with a different name, i am able to run correctly for a while. I have found that if i change the applet name, it starts to work correctly again for a while. But the name must be a new name and not the name of an applet that stoped working before. eg. Puzzle becomes Puzzle2 but Puzzle2 cannot become Puzzle again. Does this behaviour suggest something stored in the registry or elsewhere? Good luck fixing this. It is very annoying.
Can you send your ide.log to track it better?
This is the only line in my ide.log file: Version = NetBeans 3.2 Not very helpful i fear....
The ide.log is located under the system directory of your IDE settings. It is not in your IDE instalation. There has to be more information otherwise your IDE is corrupted somehow.
Couple of comments: Applets can be debugged even if they run in browser. You need to attach the debugger to JVM running in your browser. The ide writes log. This log contains some information about execution of external proceses. I am not able to reproduce the problem. Also it is not clear what JDK you have used.
Created attachment 2588 [details] NetBeans generated log file
I am experiencing this exact issue, except I attached a log file generated by NetBeans. The issue does not seem to be OS dependant, because I am running on: Linux version 2.4.2-2 (Red Hat Linux 7.1 2.96-79)) #1 Sun Apr 8 20:41:30 EDT 2001 (Information in my /proc/version file) Where as keith seems to be using a Windows OS. I was also using netbeans on Windows 2K and I experienced this same issue, however it seemed to resolve itself when I restart the IDE, or closed and re- opened the project. However, this does not seem to be the case on my Linux machine. The only thing that I did different today out of any other day, was build my javadoc directory from my (project) api. After that, the applets won't run in the appletviewer (when executed from netbeans). Same issue, it loads the execution window, says the process is running, 3 seconds later, process terminates and nothing happens. (No output in output window and no appletviewer window appears).
I have discovered the fault present in this bug... It isn't really a bug, it is more like a request for enhancement. When you build your JavaDoc from you own api, the java doc utility will create a directory sturcture that matches exactly the package structure of your API. Netbeans sets the default javadoc directory to $HOME/nbuser32/system/javadoc which then automatically gets added to the project's javadoc search path (see javadoc tab in explorer window). Netbeans also, by default will run applets in the appletviewer using an HTML file that has the exact name as the applet itself (equivalent to running the command: %>appletviewer http://localhost:8082/classpath/package/Applet.html) HOWEVER if the javadoc directory is located in default javadoc directory ($HOME/nbuser32/system/javadoc), then the internal webserver (running on port 8082) will locate and return the javadoc html document for that applet. The appletviewer will not find an applet tag in the file and will quietly exit without producing any output and the process will terminate and netbeans will not know that anything wrong happened (no error will be generated in the IDE.log file). To test to see if this is your problem, open a web browser and type the exact URL of the HTML file of your applet as produced by netbeans (check ide.log file for exact URL -- the line should look something like: [IDE-Exec] Executing: 0 .= C:\JDK1.3.0_02\JRE\..\bin\appletviewer 1 .= http://localhost:8082/classpath/package/Applet.html ) If this is your issue, then instead of the applet.html file containing the applet tag, the javadoc for that class should come up in the browser. HOW TO RESOLVE THIS ISSUE: Move your javadoc directory to somewhere else other than to the nbuser32/system directory and remount the new path in your javadoc search path (javadoc tab in explorer window). Make sure you change the destination directory of future javadoc builds. To do this, 1) select Project->Settings... from the pull down menu 2) Expand the "Doclet" node. 3) Select the "Standard Doclet" leaf 4) Type, or browse to the new location of you javadoc files by selecting the "Destination" option.
Verified in NB3.3 beta 6.