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 108096 - debugging a simple async demo leads to endless exceptions in server.log
Summary: debugging a simple async demo leads to endless exceptions in server.log
Status: VERIFIED WORKSFORME
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Alexander Zgursky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-26 01:28 UTC by pchen
Modified: 2007-07-24 12:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
appserver log showing endless exceptions when using BPEL Debugger (306.41 KB, application/octet-stream)
2007-06-26 01:31 UTC, pchen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pchen 2007-06-26 01:28:32 UTC
how to reproduce:
1. New Project -> Samples->SOA->Asynchronous BPEL Process
2. Enable, attach BPEL debugger and set a breakpoint
3. Run test which will trigger BPEL debugger

I ran a couple of times and the appserver log window started to have endless exceptions and errors.
It looked like an infinite loop or some sort.  Please see attached appserver log for a sample
Comment 1 pchen 2007-06-26 01:31:08 UTC
Created attachment 44386 [details]
appserver log showing endless exceptions when using BPEL Debugger
Comment 2 pchen 2007-06-27 22:32:23 UTC
I found this can surely trigger the endless loop of exceptions in server.log

1. Set a breakpoint, run it so that the bpel process is stopped at that point.
2. Wait for the test to timeout, and start another bpel process.
3. Repeat #1 and #2 just a few times and you will run into an infinite loop of exceptions in appserver, which you will
have no other choice but to shut down.
Comment 3 pchen 2007-06-27 23:45:59 UTC
Reproduced with NetBeans M10 build 200706242201 (full) on Windows XP

Upgraded to P1 because this bug leaves users no choice but to shut down Sun's Appserver.
Comment 4 Peter Pis 2007-06-28 08:43:58 UTC
This issue is marked as a stopper for M10. Could you please integrate the fix into the trunk and "release60-m10" branch?
Thanks.
Comment 5 Sergey Lunegov 2007-06-28 08:49:02 UTC
Peter, Alexander is actively working on it.
Comment 6 Alexander Zgursky 2007-06-28 12:39:21 UTC
Reproduced. Although, the bug is obviously not on the IDE side but on the runtime side, so I filed an issue at
open-jbi-components.dev.java.net:
https://open-jbi-components.dev.java.net/issues/show_bug.cgi?id=128
Comment 7 Sergey Lunegov 2007-06-28 13:12:48 UTC
This is a seirous issue indeed. But taking into account that root cause is in opene esb runtimes
I don't consider it like showstopper for M10.
Comment 8 Sergey Lunegov 2007-07-19 13:16:48 UTC
Appropriate runtime bug was closed as not reproducible. Close
this one as works for me.
Comment 9 Ivan Sidorkin 2007-07-24 12:18:04 UTC
not reproducible in Build 200707210000