In this article we're going to talk about the change in how error messages are displayed after applying IBM BPM 856 Cumulative Fix 01 (IBM BPM 856 CF01). We will be targeting the following situations:
- If you have already applied CF01 in your IBM BPM 8.5.6 environment, then this article will help to explain the unexpected behavior you will see when debugging processes/services in IBM BPM.
- If you are planning to install CF01 in your IBM BPM 8.5.6 environment, then this article will help you with better planning and set your expectations accordingly.
Once you install CF01, you will no longer see any errors in the browser when running or debugging services in any environment including DEV.
The following is an example of what you will see in place of the actual runtime error:
You can imagine the impact this might have on your development team. Basically BPM developers will have to look at the logs on BPM server each time a process/service/task fails to get an understanding why it failed, e.g. what was the "actual" error.
Now let's imagine 15 developers working on a process application running processes/services in DEV environment, getting errors and trying to identify which error is theirs because they all are recorded in the same log file - SystemOut.log. It would be a rather challenging task.
This generic error message was introduced with the fix for APAR JR52721 (http://www.ibm.com/support/docview.wss?uid=swg1JR52721
) but unfortunately there were no backward compatibility flags added. It was introduced to eliminate a security vulnerability. But for BPM developers, this generic message is unacceptable and slows down development processes in BPM.
In 8.5.6 all the stack traces were taken out already. But with the addition of this APAR, even the error itself was taken away.
This issue was addressed by IBM in IBM BPM 856 Cumulative Fix 02 (IBM BPM 856 CF02).
(APAR in question is - JR54753)