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.
Steps to reproduce: - open TRS sample project - set a breakpoint to ReceiveItinerary activity - deploy the project but do not deploy partner services application. If partner services are already deployed then disable or undeploy them - start BPEL debug session - open BPEL Process Instances debug window - run HasHotel test, when breakpoint is reached press continue. Test passes. - run HasNoReservation test - when breakpoint is reached press continue until ReserveAirline activity is reached. - press Continue to perform an invoke activity Result: Process instance becomes Completed but Test result window is still showing "Running..." until 30 sec. timeout expires.
There are some typos in description, do StepInto instead of Continue in following steps: - when breakpoint is reached press StepInto until ReserveAirline activity is reached. - press StepInto to perform an invoke activity
Test doesn't complete because it doesn't receive a response from the BPEL Engine. It turn, debugger receives a notification from a failed process instance through debugger proprietary transport, not HTTP-SOAP transport that is used by partners. That's why debugger can see that the process instance is completed but the test framework, which can be considered as a process's partner, doesn't. This issue should be filed against BPEL SE in BugTraq - closing it as INVALID.
Moved to bugtrack CR6472476