This topic discusses problems that you can encounter while using the failed event manager.
Problem | Refer to the following |
---|---|
I am having trouble with reduced performance during an advanced search | Advanced search feature 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 |
The failed event manager's advanced search feature is not optimized. Therefore, you may experience reduced performance when using the Advanced search tab with a large set of failed events.
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.
To avoid this problem, always enter your dates and times carefully, following the example provided above each field.
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.
Last updated: Thu Apr 27 15:07:56 2006
(c) Copyright IBM Corporation 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)