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 94625 - NPE when debugging BPEL processes
Summary: NPE when debugging BPEL processes
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Alexander Zgursky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-06 13:53 UTC by Mikhail Kondratyev
Modified: 2007-03-06 10:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kondratyev 2007-02-06 13:53:40 UTC 
Could observe this NPE several times when debugging BPEL processes
The exact steps to reproduce are unclear. After the NPE is reproduced once it
will be thrown for a lot of debugger actions (like stop/start debug session,
stop app server, etc...). User has to restart App Server to continue his work

Exception stack trace:
java.lang.NullPointerException
	at
org.netbeans.modules.bpel.debugger.ui.editor.BpelEditorContext.removeAnnotation(BpelEditorContext.java:114)
	at
org.netbeans.modules.bpel.debugger.api.EditorContextBridge.removeAnnotation(EditorContextBridge.java:170)
	at
org.netbeans.modules.bpel.debugger.ui.ExecutionAnnotationsListener$AnnotationsHolder.clearAll(ExecutionAnnotationsListener.java:225)
	at
org.netbeans.modules.bpel.debugger.ui.ExecutionAnnotationsListener$AnnotationsHolder.annotate(ExecutionAnnotationsListener.java:197)
	at
org.netbeans.modules.bpel.debugger.ui.ExecutionAnnotationsListener$AnnotationRunnable.run(ExecutionAnnotationsListener.java:180)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932)
Comment 1 Alexander Zgursky 2007-02-07 14:17:56 UTC 
I believe, user would have to restart an IDE, not appserver
Comment 2 Alexander Zgursky 2007-02-12 09:51:08 UTC 
As there is no scenario to reproduce the bug - the simple check for null has
been added. It needs further investigation to find out how is it possible at all
to have null there.
Comment 3 Mikhail Kondratyev 2007-03-06 10:07:15 UTC 
Could not reproduce any more
Marking as verified for now