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.

Bug 74126

Summary:	AbsentInformationException when debugging a servlet
Product:	debugger	Reporter:	Max Sauer <msauer>
Component:	Java	Assignee:	Daniel Prusa <dprusa>
Status:	RESOLVED FIXED
Severity:	blocker
Priority:	P4
Version:	6.x
Hardware:	Sun
OS:	Solaris
Issue Type:	DEFECT	Exception Reporter:
Attachments:	exception stack trace

Description Max Sauer 2006-03-29 08:25:39 UTC

An informational com.sun.jdi.AbsentInformationException is thrown when stepping
(F8) up to the end of a servlet:

com.sun.jdi.AbsentInformationException
        at
org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl.getCallStack(JPDAThreadImpl.java:256)
        at
org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl.getCallStack(JPDAThreadImpl.java:224)
[catch] at
org.netbeans.modules.debugger.jpda.ui.CurrentThreadAnnotationListener.annotate(CurrentThreadAnnotationListener.java:123)
        at
org.netbeans.modules.debugger.jpda.ui.CurrentThreadAnnotationListener.propertyChange(CurrentThreadAnnotationListener.java:73)
        at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:338)
        at
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:275)
...
(whole stack trace attached)

Steps to reproduce:
-------------------
1) Open/Create a WebApplication project
2) Open/Create a servlet
3) Place a BP inside
4) Run 'Debug File'
6) Use 'Step Over' (F8) to reach the end of the file
--> exception

-----------
NetBeans IDE Dev (Build 200603270859)
1.6.0-beta2; Java HotSpot(TM) Client VM 1.6.0-beta2-b76
SunOS version 5.10 running on sparc
en (nb); ISO646-US

Comment 1 Max Sauer 2006-03-29 08:28:35 UTC

Created attachment 29464 [details]
exception stack trace

Comment 2 Martin Entlicher 2006-04-07 09:25:22 UTC

Something has resumed the thread in between... It needs to be assured that all
thread resumes and access to methods that need to have the thread stopped is
synchronized.

Comment 3 Peter Pis 2008-04-10 22:54:08 UTC

Changing TM for open issues.

Comment 4 Daniel Prusa 2008-07-31 22:32:33 UTC

The exception is only informational, thrown on debugger finish and does not break any functionality -> decreasing to P4.

Comment 5 Martin Entlicher 2009-12-01 14:13:19 UTC

Should be fixed in NB 6.8. Please verify.