Troubleshooting the failed event manager

This topic discusses problems that you can encounter while using the failed event manager.

Note: This topic does not discuss how to use the failed event manager to find, modify, resubmit, or delete failed events on the system. For information about managing failed events, see Managing WebSphere Process Server failed events.
Select the problem you are experiencing from the table below:
Problem Refer to the following
I am having trouble with reduced performance during an advanced search Advanced search feature is not optimized
I am having trouble entering values in the Search page's By Date tab Values in the By Date tab automatically change to default if entered incorrectly
I am having trouble deleting expired events Executing the Delete Expired Events function appears to suspend the failed event manager

I am having trouble with failed events not being created

Failed events are not being created

Values in the By Date tab automatically change to default if entered incorrectly

The Search page's By Date tab contains two fields: From Date and By Date. Both fields are required. The values are locale-dependendent, and they must be formatted exactly as shown in the example above the field. Any inconsistency in the value's format (for example, including four digits in the year instead of 2, or omitting the time) will cause the failed event manager to issue the following warning and substitute a default value in the field:

CWMAN0017E: The date entered could not be parsed correctly: your_incorrectly_formatted_date. Date: default_date is being used.

The default value of the From Date field is defined as January 1, 1970, 00:00:00 GMT.
Important: The actual default value shown in your failed event manager implementation will vary depending on your locale and time zone. For example, the From Date field defaults to 12/31/69 7:00 PM for a machine with an en_US locale in the Eastern Standard Time (EST) time zone.
The default value for the By Date field is always the current date and time, formatted for your locale and time zone.

To avoid this problem, always enter your dates and times carefully, following the example provided above each field.

Executing the Delete Expired Events function appears to suspend the failed event manager

If you use the Delete Expired Events button in situations where there are many failed events in the current search results, or where those events contain a large amount of business data, the failed event manager can appear to be suspended indefinitely.

In this situation, the failed event manager is not actually suspended; it is working through the large data set, and will refresh the results set as soon as the command completes.

Failed events are not being created

If the Recovery subsystem is not creating failed events, go through the following checklist of potential causes:
  • Ensure that the wpsFEMgr application is running. If necessary, restart it.
  • Ensure that the failed event manager's database has been created, and that the connection has been tested.
  • Ensure that the necessary failed event destination has been created on the SCA system bus. There should be one failed event destination for each deployment target.
  • Ensure that the Quality of Service (QoS) Reliability qualifier has been set to Assured for any Service Component Architecture (SCA) implementation, interface, or partner reference that participates in events you want the Recovery service to handle.

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)