APAR status
Closed as program error.
Error description
The OSGi container does not shut down correctly when it is disconnected from the catalog server.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of eXtreme Scale who use an OSGi * * Framework to manage their catalog and * * container servers. * **************************************************************** * PROBLEM DESCRIPTION: When restarting the eXtreme Scale * * server runtime the stop was slow * * because we were waiting for placement * * events. * **************************************************************** * RECOMMENDATION: * **************************************************************** Similar changes that were made in APAR PM95822 were needed in the OSGi logic as well. Those similar changes were made so that we do not wait for shards to be completely removed from a container that we are stopping due to it being disconnected from the catalog server and/or its peer containers.
Problem conclusion
An interim fix is available for this problem in the V8.5 and V8.6 service stream.
Temporary fix
Comments
APAR Information
APAR number
PI11197
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-02-06
Closed date
2014-03-12
Last modified date
2014-03-12
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
WS EXTREME SCAL
Fixed component ID
5724X6702
Applicable component levels
R850 PSY
UP
R860 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 March 2014