Fixes are available
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 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
APAR status
Closed as program error.
Error description
When upgrading from an earlier WebSphere Application Server fix pack level to V7.0.0.27, V8.0.0.5, or V8.5.0.1, a performance delay might be observed when performing administrative tasks when global security is enabled with a LDAP repository. This is due to a regression introduced by APAR PM66913. The delay will occur for each "queryNames" call, which could come from a wsadmin script or an action taken in the administrative console. The delay will be more noticeable in large topologies that include many nodes, as the queryNames call will be sent to each node agent. The delay will only occur the first time that a queryNames call establishes a connection to a node agent when it has to authenticate. On subsequent calls, the login data is found in the security cache, and the authentication will not need to be done again, which prevents the problem. In a trace of the System Management and Security components, delays between queryNames calls will be seen: [2/23/13 17:18:01:254 EST] 00000d0c AdminServiceI 3 remote queryNames against: [2/23/13 17:18:01:676 EST] 00000d0c AdminServiceI 3 remote queryNames against: [2/23/13 17:18:02:089 EST] 00000d0c AdminServiceI 3 remote queryNames against: [2/23/13 17:18:02:513 EST] 00000d0c AdminServiceI 3 remote queryNames against: [2/23/13 17:18:02:954 EST] 00000d0c AdminServiceI 3 remote queryNames against: This is due to a delay in the tokenBasedAuth method in the Security component: [2/23/13 17:18:02:091 EST] 00000062 CallRouter > route Entry opName=queryNames, objName=WebSphere:type=ListenerPort,name=FN.Router.Priority1QLis tener,* secDataFilled=true, authByToken=true, token length=276, map={} [2/23/13 17:18:02:091 EST] 00000062 CallRouter > tokenBasedAuth Entry [2/23/13 17:18:02:092 EST] 00000062 CallRouter 3 Attemping to extract subject from a V6+ token. <----------THIS RUNS FOR HALF A SECOND [2/23/13 17:18:02:510 EST] 00000062 CallRouter < tokenBasedAuth Exit
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: A delay may be noticed for Large * * Topologies using Global Security * * and LDAP repositories. * **************************************************************** * RECOMMENDATION: * **************************************************************** When upgrading to WebSphere Application Server 7.0.0.27, 8.0.0.5 or 8.5.0.1 there may be a delay when doing LDAP requests. The delay may happen with large topologies with LDAP queries or logging into the Administration Console.
Problem conclusion
Our code was changed in order to prevent this delay. The cause for this issue was that everytime an LDAP query was run a schema check that took extra time was run. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.29, 8.0.0.6 and the fixpack that follows 8.5.0.2. 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
PM83482
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-02-24
Closed date
2013-04-08
Last modified date
2013-04-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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021