APAR status
Closed as program error.
Error description
If all catalog server endpoints result in a timeout during a client connect, the overall timeout before the client receives a connection is longer in WebSphere eXtreme Scale Server V8.6.0.6 and later than it was in WebSphere eXtreme Scale Server 8.6.0.5. For example, when the defaults are used for JVM arguments, com.ibm.websphere.xs.determine.transport.timeout and com.ibm.websphere.xs.determine.transport.attempts, then the time that an exception occurs can go to 90 seconds instead of 30 seconds. See the following example messages when the timeout takes 90 or more seconds, where the CWOBJ0210W lists "Probe returned null" instead of a communication exception. CWOBJ0204I: The transport type of this Client JVM is being determined by contacting the catalog service domain with the catalog service endpoints of: myHost:2809. CWOBJ0210W: The transport type of the remote server on myHost:2809 cannot be determined. The following exception occurred while determining the transport type: Probe returned null CWOBJ7851W: Received a timeout while waiting for a response to a com.ibm.ws.xs.xio.protobuf.XIOMessage$XIORefLookupRequest/reqID= 0 message from endpoint IP_ADDR:2809. The current timeout is 30 seconds. When the message was added, the queue size was 0.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere eXtreme Scale users who * * experience timeouts against all listed * * catalog server endpoints. * **************************************************************** * PROBLEM DESCRIPTION: A long timeout can occur when * * connections to all catalog server * * endpoints time out on a client * * connect. * **************************************************************** * RECOMMENDATION: * **************************************************************** If all catalog server endpoints result in a timeout during a client connect, the overall timeout before the client receives a connection is longer in WebSphere eXtreme Scale Server 8.6.0.6 and later than it was in WebSphere eXtreme Scale Server 8.6.0.5. For example, when the defaults are used for JVM arguments, com.ibm.websphere.xs.determine.transport.timeout and com.ibm.websphere.xs.determine.transport.attempts, then the time to exception can go to 90 seconds instead of 30 seconds. See the following example messages when the timeout takes 90 or more seconds, where the CWOBJ0210W lists "Probe returned null" instead of a communication exception. CWOBJ0204I: The transport type of this Client JVM is being determined by contacting the catalog service domain with the catalog service endpoints of: myHost:2809. CWOBJ0210W: The transport type of the remote server on myHost:2809 cannot be determined. The following exception occurred while determining the transport type: Probe returned null CWOBJ7851W: Received a timeout while waiting for a response to a com.ibm.ws.xs.xio.protobuf.XIOMessage$XIORefLookupRequest/reqID= 0 message from endpoint IP_ADDR:2809. The current timeout is 30 seconds. When the message was added, the queue size was 0.
Problem conclusion
A timing window was fixed and when all catalog server endpoints provided in the client connection request time out, an exception is returned to the client instead of trying an XIO and ORB connection.
Temporary fix
Comments
APAR Information
APAR number
PI44121
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
2015-07-01
Closed date
2015-07-02
Last modified date
2015-07-02
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:
02 July 2015