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
APAR status
Closed as program error.
Error description
After running some requests that result in cache entries in the ESI caches on two IBM HTTP Server/PLG cluster fronted by a load balancer (LB) we go to the /cachemonitor/ESIStats.jsp page and look at the hosts in the drop-down list. This list contains the ip address of the LB when the IP addresses of the two IBM HTTP Server instances are expected. Clicking on the "content" button in CacheMonitor to look at what is currently in the cache the host column just contains the IP address of the loadbalancer but the process id ( PID:s ) of the IBM HTTP Server processes on the IBM HTTP Server machines.... This doesn't look like the correct information. Testing with the plugin determined that the remoteHost value of the LB ipaddress is being set because of the private $W headers being set by the plugin. For ESI connections with CacheMonitor the private headers should not be set. The connection between the plugin and the invalidator servlet is a private long running connection and it should not contain the private headers associated with the client request. This connection is completely independent from client requests. Plugin needs to remove the private headers from the request to the invalidator servlet.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using the CacheMonitor and using * * the WebSphere Plugin with the * * ESIInvalidationMonitor function active. * **************************************************************** * PROBLEM DESCRIPTION: The Cache Monitor displays the * * incorrect host ip address for the edge * * cache. * **************************************************************** * RECOMMENDATION: * **************************************************************** When the WebSphere plugin creates the ESIInvalidationMonitor request it was copying the original client request that was the trigger for the creation of the ESIInvalidationMonitor request. In doing this it was using the private headers $WSRA and $WSRH that contained the ip address of the client. The CacheMonitor was using this ip address for the host of the edge cache(plugin).
Problem conclusion
The plugin has been changed to remove the $WSRA and $WSRH private headers of the copied request. Without those headers the CacheMonitor will correctly use the ip address of the plugin as the host of the edge cache. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.33, 8.0.0.9, and 8.5.5.3. 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
PI10256
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-23
Closed date
2014-02-28
Last modified date
2014-05-20
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:
28 April 2022