PM82633: RESOLVE_COMPLETE_INFO NAMING REQUESTS ON CLUSTERS

Fixes are available

APAR status

Closed as program error.

Error description

resolve_complete_info requests for cluster resources

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WebSphere Application Server V8.0  *
*                  or V8.5 on z/OS with applications that      *
*                  look up cluster-hosted objects by           *
*                  bootstrapping to node agents.               *
****************************************************************
* PROBLEM DESCRIPTION: When applications obtain an initial     *
*                      JNDI context from a node agent to       *
*                      look up an object that resides on a     *
*                      cluster, lookups might fail as long     *
*                      as one single cluster member is not     *
*                      available.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When applications obtain an initial JNDI context from a node
agent to look up an object that resides on a cluster, lookups
might fail as long as one single cluster member is not
available.

Problem conclusion

JNDI clients running on z/OS often bootstrap to node agents
to look up objects on application servers and clusters. This
requires the name server running on the node agent to resolve
the lookup through a federated naming context binding that
resolves to the target server or cluster. In the case of
clusters, the node agent name server on z/OS caches a
federated naming context to a cluster that always resolves to
the same cluster member. To alleviate the problem, the name
server logic was changed to cycle through each cluster member
in round robin fashion when the cluster's federated naming
context binding is resolved. In the case of a running but
unresponsive cluster member, lookups might still hang, but
only when the unresponsive cluster member is chosen for the
lookup. Lookups that are routed to functional cluster members
should complete successfully.

Retry logic in JNDI client code should enable lookups to
succeed as long as at least one cluster member is available
when, without the name server change, those same lookups all
might fail as long as a single cluster member was unavailable.

To activate the round robin binding resolution policy, define
the following custom property setting in the cell, node, or
name server configuration:

    naming.urlbinding.resolution=cacheRoundRobin

Note: The property is not a JVM custom property. You must set
the property as a cell, node, or name server custom property.

All name servers within the configured scope will use the
specified binding resolution policy.

APAR PM82633 is currently targeted for inclusion in Fix Pack
8.0.0.7 of WebSphere Application Server V8.0 and a Fix Pack
8.5.5 of WebSphere Application Server V8.5.

Please refer to the Recommended Updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

In addition, please refer to URL:
http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack PTF information.

Temporary fix

Comments

APAR Information

APAR number
PM82633
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-12
Closed date
2013-04-16
Last modified date
2013-05-09

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022

Tips

PM82633: RESOLVE_COMPLETE_INFO NAMING REQUESTS ON CLUSTERS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?