This describes how to troubleshoot problems with the staff service
and the staff plug-ins.
Why and when to perform this task
One of the following situations might be caused by a problem with
the staff service or a staff plug-in:
- Stopped staff activities
- Changes to the staff repository that are not immediately reflected in
work-item assignments
- Error and warning messages when accessing an LDAP server
Use this overview task to help resolve the problem. You can also go
to the Technical support search page, to
look for additional information.
- Stopped staff activities
- You encountered one or more of the following problems:
- Work items resulting from staff activities cannot be claimed although
the business process started navigating successfully.
- The SystemOut.log file contains the following message: CWWB0057I:
Activity 'MyStaffActivity' of processes 'MyProcess' has been stopped because
of an unhandled failure...
This message indicates that WebSphere Application Server security might
not be enabled. Human tasks and processes that use people authorization require
that security is enabled and the user registry is configured. Take the following
steps:- Check that WebSphere security is enabled. In the administrative console,
go to and make sure the check box for Enable global security is
selected.
- Check that the user registry is configured. In the administrative console,
go to and check the Active user registry attribute.
- Changes to the staff repository that are not immediately
reflected in work-item assignments
To optimize the staff query resolution performance, the retrieved query
results are cached. The cache content is checked for currency when a new process
instance is created or the corresponding staff activity gets scheduled. By
default, the time after which the shared staff query results expire is one
hour.
To change how often the cache is refreshed,
perform ../../../com.ibm.wsps.adm.doc/doc/bpc/c5tuneproc_staff_query_refresh_time.html.
- Error and warning messages when accessing an LDAP server
- When tracing is enabled for the staff support service, that is when the
trace string includes: com.ibm.bpe.*=all: com.ibm.ws.staffsupport.ws.*=all,
the following typical erroneous cases are indicated by warning or error messages.
The following are examples:
- Could not connect to LDAP server in the trace.log file
indicates that the LDAP server cannot be connected to.
- javax.xml.transform.TransformerException: org.xml.sax.SAXParseException:
Element type "xsl:template" must be followed by either attribute specifications,
">" or "/>" in the System.out or System.err files indicates that
the LDAPTransformation.xsl file cannot be read.
- LDAP object not found. dn: uid=unknown,cn=users,dc=ibm,dc=com
[LDAP: error code 32 - No Such Object] in the trace.log file indicates
that an LDAP entry cannot be found.
- Requested attribute "quid" not found in: uid=test222,cn=users,dc=ibm,dc=com in
the trace.log file indicates that an attribute cannot be found in an LDAP
entry. .