JR47915: SWITCH TO DECISION SERVICE TAKES TOO LONG
Fixes are available
Closed as program error.
If the BPD engine navigates to a service task (like the decision service), it sends a notification to the service engine and informs the TaskLoader to immediately look for the notification. Sometimes, the database transaction for the notification has not yet committed, so the TaskLoader does not see it. It waits a bit (per default: 2 seconds), and looks again. Those 2 seconds slows down the execution of a BPD with services.
RUN TR Perf prob when executing a Decision Table PROBLEM DETAILED DESCRIPTION: The communication between BPD engine and Service engine is sometimes delayed.
The kick-on-schedule now occurs within a transaction synchronization callback, and the task loader sees the notification immediately in the database, and can act on it. FIX AVAILABILITY: iFix for 184.108.40.206 is available on Fix Central, search for APAR JR47915 at http://www.ibm.com/support/fixcentral/ Fix is also targetted for inclusion in next fixpack for BPM 8.0.1, BPM 8.5.0 When obtaining any of the above fixes, be sure to download the accompanying readme, for itself, and any prerequisite fixes, and review them thorougly.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
Translate this page: