Fixes are available
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
In a clustered environment a list of possible servers is returned from the naming service for construction of the resolve initial reference value. Adding logic to check for a local reference in the list and using that local reference gives preference that the ejb will be dispatched locally.
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of z/OS IBM WebSphere * * Application Server V7.0, V8.0, and V8.5. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * does not prefer to resolve object * * URLs, such as those used for naming * * lookups, to a local server, if one * * exists. * **************************************************************** * RECOMMENDATION: * **************************************************************** If one WebSphere Application Server for z/OS server is looking up a JNDI name in a cluster, the naming code uses an object URL to locate a member of the cluster to resolve the lookup to. When resolving the object URL, the intent is to resolve it to a local server if possible, but the current code does not do this. Instead, the object URL is resolved in sequential order, such that resolution to the first address in the URL is tried first, regardless of whether that address is local or remote.
Problem conclusion
The code that resolves object URLs was changed to prefer to resolve the URL locally, if possible. Resolution is attempted first to all local address. If the local address cannot be reached (for example, if the target server isn't started on the local machine), remote addresses in the URL are then tried. APAR PI13281 requires a change to documention. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/library The following changes to the WebSphere Application Server Version 7.0 Information Center will be made available inr June, 2014. The topic "Application server custom properties for z/OS" will be updated to include the following description of the new custom property: protocol_iiop_resolve_object_url_local Specifies whether or not the application server should resolve object URLs to a server that is local to the LPAR, if possible. By default, the object URL is processed in order and the first server that can be reached is chosen. When this property is set to 1, any servers local to the LPAR are checked first and only if none of those servers are reachable will resolution be attempted to a remote server. Data Type Integer Default 0 Acceptable values 0 or 1 APAR PI13281 is currently targeted for inclusion in Service Level 7.0.0.33, 8.0.0.9, 8.5.5.3 of WebSphere Application Server. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PI13281
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-07
Closed date
2014-05-27
Last modified date
2014-07-01
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
R700 PSY UI18561
UP14/06/21 P F406
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
28 April 2022