Registering Worklist Connections Using WLST

Managing the Worklist Service 22-15

22.5 Troubleshooting Issues with Worklists

The Worklist service relies on several middleware components to display worklist items to logged-in users and therefore, several factors may cause the Worklist service to fail. The issues and solutions discussed in this section relate to some common problems you may encounter. This section includes the following subsections: ■ Section 22.5.1, Unavailability of the Worklist Service Due to Application Configuration Issues ■ Section 22.5.2, Unavailability of the Worklist Service Due to Server Failure

22.5.1 Unavailability of the Worklist Service Due to Application Configuration Issues

Issues described in this section pertain to the unavailability of the Worklist service—Worklist task flows display the message The Worklist service is unavailable with the following warning: Either no BPEL connections are configured, or there is an issue with the existing connection configuration. Verify that at least one BPEL Worklist connection is configured for this application, and that no unresolved ConfigurationExceptions exceptions are logged. This section includes the following subsections: ■ Section 22.5.1.1, adf-config.xml Refers to a Non-Existent BPEL Connection ■ Section 22.5.1.2, adf-config.xml Has No Reference to a BPEL Connection ■ Section 22.5.1.3, No Rows Yet Message Displays

22.5.1.1 adf-config.xml Refers to a Non-Existent BPEL Connection

Problem The connection listed in the adf-config.xml file does not exist in the applications connections.xml file. The following entries exist in the diagnostic log file for the managed server on which the application is running: [2009-03-22T13:33:54.140+00:00] [DefaultServer] [WARNING] [WCS-32008] [oracle.webcenter.worklist.config][tid: [ACTIVE].ExecuteThread: 12 for queue: weblogic.kernel.Default self-tuning] userId: user][ ecid: 0000I0iOmdTFk3FLN2o2ye19kTB0000V,0][APP: WorklistV2.0 arg: Human Resources The BPEL Connection named connection_name was not present in the connections.xml file. This will prevent the Worklist service from being able to interact with the required this BPEL connection. Note: To identify causes of failures, examine log files on the managed servers hosting Worklist service processes and the managed servers for any SOA BPEL servers you have configured.