Performance apar marked Hiper - authentication cache failure
 Flash (Alert)
 
Abstract
Due to authentication cache failures, the users need to be re-authenticated even though the entry in the cache does exist. This causes performance degradation.

See below or apar text for local fix.
 
Content
The following apars were marked hiper:
PK06997 - V5.0 (scheduled to ship in service level W502033)
PK06996 - V5.1 (scheduled to ship in service level W510218)
PK03351 - V6.0 (shipped as PK08729 in 6.0.2 - Build Level o0527.07)

This apar can be a match if you specify the value for the following variable in lower case (see JESMSGLG part of the job output):
protocol_iiop_daemon_listenIPAddress

You should verify if you satisfy the following 3 conditions which make this problem visible:
1. The value of the protocol_iiop_daemon_listenIPAddress is lower case in the was.env file on the endpoint. This includes the daemon was.env and possibly the application server was.env file. You can also verify the setting in JESMSGLG part of the job output.

2. Global security is enabled in WebSphere® for z/OS.

3. Local OS is the user registry being used.

This problem may cause higher CPU usage due to the fact cache is not utilized.

Local Fix
Modify the 'Host Name' field to specify UPPER case IP Name in the admin console under: System Administration > z/OS Location Service
Save the configuration and recycle WebSphere (including Daemon).

Once servers are restarted, you should see the following variable in the JESMSGLG part of the job output. Make sure the value is in upper case.
protocol_iiop_daemon_listenIPAddress=SOME.IP.ADDRESS.COM
 
 
 


Document Information


Current web document: swg21212317.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Hangs/Performance Degradation
Operating system(s): z/OS
Software version: 6.0.1
Software edition:
Reference #: 1212317
IBM Group: Software Group
Modified date: Jul 20, 2005