Fixes are available
APAR status
Closed as program error.
Error description
If email notification is enabled in portal for a lot of users, this can cause lock timouts on table LSW_BPD_INSTANCE because emails are send in a loop for each subscribed user. This can be improved by sending one email notification to a list of users.
Local fix
n/a
Problem summary
If email notification is enabled and a Task is created, BPM sends an email to each user that is assigned to the task and is registered for email notification. If many users apply and the mail server is slow, this can take a significant amount of time. Since the sending of the email happens synchronously within a process navigation transaction, this can cause lock timeouts on table LSW_BPD_INSTANCE.
Problem conclusion
The fix of the problem introduces 2 new properties in the <server> <email> configuration. The properties are <server> <email> <send-email-notifications-to-list>[true | false]</send-email-notifications-to-list> <send-email-notifications-async>[true | false]</send-email-notifications-async> <email> <server> They have the following effects: If <send-email-notifications-to-list> is set to false, BPM sends a separate email to each user that is assigned to the task and is registered for email notifications. This is identical to the behavior before the IFix. If <send-email-notifications-to-list> is set to true, the users that will receive a notification email are grouped by locale. For each locale, an email is sent to the list of all users with that locale. In order to keep privacy as previously, these emails are not sent to the "to:" destination but rather to "bcc:". This has the effect that no user can see the other users in the list. If <send-email-notifications-async> is set to false, sending of the emails happens synchronously within the navigation transaction of the BPD. This is identical to the behavior before the IFix. If <send-email-notifications-async> is set to true, sending of the emails happens asynchronously in a separate thread. Depending on the overall load, the navigation transaction that created and sent the task may finish before an email notification has been sent. Please note, that this modification introduces new failure possibilities. For example, if sending of an email to one user failed, this was reported in the past, an exception was thrown and the creation of the task failed. If <send-email-notifications-to-list> is set to true, BPM can no longer detect, which user caused the problem. It can only detect that the email could not be sent to the list. Similarly, if <send-email-notifications-async> is set to true, a task may be created even if sending of the emails may fail afterwards.
Temporary fix
Problem will be fixed with V8501
Comments
APAR Information
APAR number
JR46755
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-24
Closed date
2013-09-30
Last modified date
2013-09-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R850 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
08 January 2022