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 79278 - BPEL process control is not going to next break point( Wait activity Type = until)
Summary: BPEL process control is not going to next break point( Wait activity Type = u...
Status: VERIFIED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Mei Wu
URL:
Keywords:
: 79279 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-27 23:11 UTC by bugbridge
Modified: 2006-09-14 19:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-06-27 23:11:30 UTC
Original status: 4-Defer; Suggested Status: RESOLVED (Resolution:REMIND)

These items should be added to the Status Whiteboard: MONROVIA
Description:
Note : 1. Enable to BPEL debugger before creating the project.
       2. Attach the BPEL debugger using the port 3343,host=localhost
Steps to reproduce :

1.  Created an echo project (included echo.bpel and echo.wsdl file)
2.  Copy and pasted .wsdl text into the .wsdl created (see attached)
3.  In the BPEL, copy and paste the attached bpel code.
4.  Created Composite Application 
5.  Right click on CompApp1 and select properties from right click menu
6.  select Build -> Packaging Project, click on Update button and click on OK 
button
7.  Add JBI Module to CompApp1 and repeat the steps from 5 to 6
8.  Build and deploy the project
9.  Click on Step Into command until cursor reach the <wait> activity. ( Put 
the break        points before and after the wait activity)  
10. Create the test case under CompApp1 and set the test-timeout property to 
more than 3 
    mins, ex -200 sec) 

Actual Result   : Control is not coming to next break point after wait time 
reaches to expected time
Expected result : Control should be placed to next break point and continue 
the execution after wait time.

Description (Entry 2):
Renuka,

Should step 9 and step 10 be swapped.
Also, when the cursor reaches an activity, that mean the engine is *about* to 
execute that step, so you  will need to  'Step into' first on the Wait.

There is a bug that I fixed in Alaska and didn't make it into EESDK, if 
you "Step into" wait, it will enter into the wait state. In EESDK, you should 
see the breakpoint on wait again enabled after the wait time expires, and you 
have to "Step into" again to move the cursor to the next, do you see the same?

The above 2 times entering the same activity is fixed. But I wish to make sure 
it is the case you are seeing.

Thanks
Mei
Comment 1 Mei Wu 2006-07-18 20:37:23 UTC
*** Issue 79279 has been marked as a duplicate of this issue. ***
Comment 2 Mei Wu 2006-07-18 21:08:52 UTC
I believe the timezone offset should be added for until:

instead of 

<until>'2006-06-22T19:45:00'</until>

You need to specify how the local timezone offset from UTC, for example:

<until>'2006-06-22T19:45:00+1:00'</until>, otherwise it is taken as UTC time
value instead of local time value and so the wait will never complete
Comment 3 pchen 2006-09-14 19:31:13 UTC
Verified Mei's statement:
> <until>'2006-06-22T19:45:00'</until>
> You need to specify how the local timezone offset from UTC, for example:
> <until>'2006-06-22T19:45:00+1:00'</until>, otherwise it is taken as UTC time
> value instead of local time value and so the wait will never complete

on 2006-09-13 by pchen