APAR status
Closed as program error.
Error description
When using the ObjectMap.clear() API or agent calls from a client located in the same JVM as the container server, spurious timeouts might occur. The call can time out when the client should have automatically adjusted to partition movement or routing changes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere eXtreme Scale test or production * * environments where client applications are * * collocated in the same JVM as the container * * server. * **************************************************************** * PROBLEM DESCRIPTION: An agent call or the * * ObjectMap.clear() API results in the * * exception, ObjectGridRuntimeException: * * Timeout elapsed. * **************************************************************** * RECOMMENDATION: * **************************************************************** An optimization used for agent calls within the same JVM caused the agent response to be lost during certain situations.
Problem conclusion
The agent response is no longer lost.
Temporary fix
Comments
APAR Information
APAR number
PM78876
Reported component name
WS EXTREME SCAL
Reported component ID
5724X6702
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-12-10
Closed date
2013-03-27
Last modified date
2013-03-27
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
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":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 March 2013