Basis Errors and Solutions

Symptom

The start of a process or the instantiation of a human task fails with the following exception:
java.lang.IllegalArgumentException: parameter RoleUserMap must not be null!
at com.sap.bpem.tm.notification.RecipientsManager.getRecipients(RecipientsManager.java:89)
at com.sap.bpem.tm.notification.RecipientsManager.getSubstitutingRecipients(RecipientsManager.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Other terms

Galaxy, SAP NW BPM, Business Process Management, IllegalArgumentException, Notification, RoleUserMap, RecipientsManager, getSubstitutingRecipients

Reason and Prerequisites

NetWeaver 7.11 with running BPM
prerequisites:
- notifcation was turned on
- a process has been started containing a task without
-Actual owner
-Potential owner
-and Administrator
The notification component, which is responsible for sending reminder mails, fails if all these three groups are empty.

Solution

short-term workarounds:

between two different workarounds can be chosen:
a) remodel process
b) deactivate problematic component
a)
The process can be remodeled in such a way that all tasks have minimum one user in one of the groups. One way to achieve this is to lay a role lane under all tasks.
b)
Deactivate notification in CTC / application configuration.
One way to do this is to stop the server, start the config-tool and set the two properties
“notification.assigned”
“notification.newtasks”
under
cluster-data -> template -> applications -> tc-bpem-base-ear
to “false” or click “Restore default”.
Save, close config-tool and start server.

Long-term solution:

To correct this problem, apply the patch matching your support package version as listed in the patch table below as per the instructions in the NetWeaver Support Package Stack Guide.