Bug 1133478

Created attachment 930388 [details]
server.log with exception (search for DefaulSignalManager)

Description of problem:
In BPMS 6.0.3 ER1 there is a bug in behavior of BPM Example app:
The example app defines single process (Mortgage application). This process contains a web service task which calls an example web service. In case there's an error calling web service (e.g. it is not deployed) the "Troubleshoot" human task should be created (that was the correct behavior in 6.0.2 GA).

In 6.0.3 ER1 there is the following buggy behavior: after filling in process start form with valid input data (see steps to reproduce) The modal dialog with the folowing error appears and process instance is NOT started:

"Process Instances failed to start: [com.redhat.bpms.examples.mortgage.MortgageApplication:2 - Validation:17] -- Unexpected exception executing action org.jbpm.process.instance.event.DefaultSignalManager$SignalAction@32954bd8"

There's also exception in server.log (attached)


Version-Release number of selected component (if applicable):
BPMS 6.0.3 ER1

How reproducible:
Always

Steps to Reproduce:
1. Setup BPM Example aplicaton (packaged in http://dev138.mw.lab.eng.bos.redhat.com/candidate/bpms-6.0.3-ER1/jboss-bpms-brms-6.0.2.GA-redhat-6-quickstarts.zip)
2. Do NOT deploy the example web service jboss-mortgage-demo-ws.war which is provided with the example
3. build and deploy the example project
4. Try starting the example process in UI with the following CORRECT input data:
Name: Jan
Address: 12300 Wilshire Blvd., Los Angele, CA
Social Security Number: 333224444
Annual Income: 200000
Sale Price: 1000000
Down Payment: 200000
Amortization: 30

Actual results:
Modal with eror is displayed (see description), exception in server.log (attached)

Expected results:
The "Troubleshoot" human task containing stack trace should be created and process should be able to continue normally (that's the way it worked in 6.0.2 GA)

Additional info:
When you create process with INCORRECT data (e.g. use 28 as value for Amortization) the process IS STARTED, but the same problem happens when you try to complete the Data Correction Human taks.