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.
On first starting, a Java.lang.classCast exception occurs.
Created attachment 3052 [details] ide.log as requested in the message box
extbrowser and jsp are seen in stack trace
I see a lot of exceptions. Couple of them are really from extbrowser and web module. The extbrowser has some problems on Win98 platform, please fill a separate issue if you are encountering some of these. Exceptions from jsp are mostly from parsing of JSP. Maybe they should be logged as it often means that the JSP page is not parseable at the moment (not an unusal thing during editing). Most of exceptions appeared as a result of switch FFJ3.0 -> NB3.2.1 (many missing modules). In fact reported error is classCastException coming from editor: *********** Exception occurred ************ Wed Oct 17 17:46:04 BST 2001: java.lang.ClassCastException: org.netbeans.modules.editor.java.JavaIndentEngine java.lang.ClassCastException: org.netbeans.modules.editor.java.JavaIndentEngine
IMO, the editor is not the bad guy, the JavaIndentEngine itself is not a problem. Please, read last two exceptions. Line 127 from autoupdate/src/org/netbeans/modules/autoupdate/Settings.java: return (AutoupdateType)handle.getServiceType(); This is line from which the exception is thrown. I think that handle.getServiceType() returns instance of JavaIndentEngine, but I do not understand how editor could achieve it. The problem is probably first exception thrown in this session (second from bottom). I am not sure whether problem is in autoupdate module or in core, so I will assign it to core reassign it if I am wrong.
Passing to Ales, according to the last stacktrace in the log.
This exception appears after upgrade from Forte 3.0 to NB 3.2.1 and then invoking autoupdate automatic check within next startup. Workaround: You should go Tools -> Options -> Update Center and set property Update Server to NetBeans Update Center. This problem doesn't occur when you upgrade from Forte 3.0 (or Forte - development version) to NB 3.3, so I'm closing it as fixed.
*** Issue 17810 has been marked as a duplicate of this issue. ***
Resolved for 3.3.x or earlier, no new info since then -> closing.