APAR status
Closed as program error.
Error description
When an index is configured to use shards or an extension index, there is not warm start for the extension indexes. This can cause timeouts and other errors while search requests are waiting for the index to be added into memory
Local fix
Problem summary
USERS AFFECTED: Users who are using either an extension index, or sharding on their Websphere Commerce Search Server. PROBLEM ABSTRACT: Enable autowarming for extension indexes BUSINESS IMPACT: After an index re-build, there may be a period where the storefront stops functioning correctly. RECOMMENDATION:
Problem conclusion
A warm start function is added to the WC Search query component when configured to use an extension index. The warm start query can be added to the solrconfig.xml file of the CatalogEntry index, within the wc_query search component section.
Temporary fix
Comments
APAR Information
APAR number
JR53241
Reported component name
WC BUS EDITION
Reported component ID
5724I3800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function
Submitted date
2015-04-30
Closed date
2015-06-18
Last modified date
2015-06-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WC BUS EDITION
Fixed component ID
5724I3800
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSYL","label":"WebSphere Commerce Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]
Document Information
Modified date:
11 December 2021