Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
The current external behavior for WOLA to allow multiple batch address spaces to register with the same name. However, the logic that selects which registration will get requests currently always locates the last, or most recent registration and looks there for the target service only. If it does not find a match on the service name, it waits the amount of time specified for the wait for service timeout and if that expires, it times out the WAS application with a resource exception.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Allow multiple batch address spaces to * * receive WOLA requests using the same * * registration name. * **************************************************************** * **************************************************************** An application in batch can drive a WebSphere Optimized Local Adapter (WOLA) register API call (BBOA1REG) with a given registration name. The application can then drive the Host Service (BBOA1SRV) or RECEIVE REQUEST (BBOA1RCA) API and pass the name of a service it is listening under. When done from multiple address spaces using the same registration name, only the last address space which performed the registration will be eligible to receive requests.
Problem conclusion
Code has been modified to support an additional algorithm for routing requests where multiple address spaces have registered with the same registration name. The new algorithm will provide a roughly even distribution across the set of address spaces registered with the same registration name. A new environment variable was added to control the algorithm for selecting a target Host Service when multiple address spaces are registered and Hosting the same service. The new environment variable name is: ola_locate_service_search_algorithm Default: 1 Applicable to: AppServer Control regions. Description: When set to "1", the last address space to register will be the target to service locates. When set to "2", a roughly even distribution of requests will be spread across the set of address spaces with the same registration name and hosted services. APAR PM41826 is currently targeted for inclusion in Service Level (Fix Pack) 8.0.0.1 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM41826
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
2011-06-16
Closed date
2011-07-08
Last modified date
2012-08-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
Document Information
Modified date:
27 October 2021