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 84736 - Problem with BPEL debugger
Summary: Problem with BPEL debugger
Status: VERIFIED DUPLICATE of bug 84606
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: 2006-09-12 20:48 UTC by hemant_bedekar
Modified: 2006-09-19 01:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NB error log (23.62 KB, application/octet-stream)
2006-09-12 20:49 UTC, hemant_bedekar 		Details
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 hemant_bedekar 2006-09-12 20:48:45 UTC 
I have run into this problem with BPEL Debugger several times now – when I try
to attach the debugger, it fails. The small red error icon flashes in
bottom-right corner of NB and I see a Null Pointer Exception in the NB error log. 
Restarting NB, restarting machine, changing the debug port number does not seem
to help. I haven’t been able to work around this issue. I notice that once I ran
into this issue, I could never again use the BPEL Debugger for that NB
installation. I have run into this on my current install (0901). I have attached
the NB error log.
Comment 1 hemant_bedekar 2006-09-12 20:49:46 UTC 
Created attachment 33846 [details]
NB error log
Comment 2 Alexander Zgursky 2006-09-13 13:24:11 UTC 
Mei Wu wrote:
"It works fine for me. I think it probably isn't related to what project you are
debugging, because it happens at the attachment, please log an issue in IZ.
Try a workaround -- rename your userdir of NB and restart NB. This ensures NB
has a clean start, and try again.
I suspect there was a saved breakpoint but the project folder is removed."

Mei, is right, it's because of the broken breakpoints. Another workaround would
be to remove all the breakpoints using "Breakpoints View", but anyway, this bug
is already fixed. See bug 84606

*** This issue has been marked as a duplicate of 84606 ***
Comment 3 pchen 2006-09-19 01:24:49 UTC 
Verified in build 06.09.12 by mkhramov