Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
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
The Administrative Console always responds slowly whenever a user selects certain panels such as node screen, Log and Trace screen, which takes the users 3-5 minutes to come back. We see the following queryNames is reading across a Soap Connection which is not completing in a timely manner per our analysis in some javacores: ---------------- "WebContainer : 3" J9VMThread:0x00000000321B2D00, j9thread_t:0x000002000537CDF0, java/lang/Thread:0x0000000004882F88, state:R (native thread ID:0x4E8C, native priority:0x5, native policy:UNKNOWN) (native stack address range from:0x000002000DE80000, to:0x000002000DEC0000, size:0x40000) Java callstack: at java/net/SocketInputStream.socketRead0(Native Method) at java/net/SocketInputStream.read(SocketInputStream.java:140 at com/ibm/jsse2/a.a(a.java:218(Compiled Code)) at com/ibm/jsse2/a.a(a.java:99(Compiled Code)) at com/ibm/jsse2/tc.a(tc.java:540(Compiled Code)) at com/ibm/jsse2/tc.a(tc.java:526(Compiled Code)) at com/ibm/jsse2/e.read(e.java:31(Compiled Code)) at java/io/BufferedInputStream.fill(BufferedInputStream.jav at java/io/BufferedInputStream.read(BufferedInputStream.jav at org/apache/soap/util/net/HTTPUtils.post(HTTPUtils.java at org/apache/soap/transport/http/SOAPHTTPConnection.send(SOAP at org/apache/soap/rpc/Call.WASinvoke(Call.java:451(Compile at com/ibm/ws/management/connector/soap/SOAPConnectorClient$8.run at com/ibm/ws/security/util/AccessController.doPrivileged(Acce at com/ibm/ws/management/connector/soap/SOAPConnectorClient.invokeT emplateO nce(SOAPConnectorClient.java:824) at com/ibm/ws/management/connector/soap/SOAPConnectorClient.invokeT emplate( SOAPConnectorClient.java:669) at com/ibm/ws/management/connector/soap/SOAPConnectorClient.invokeT emplate( SOAPConnectorClient.java:659) at com/ibm/ws/management/connector/soap/SOAPConnectorClient.queryNa mes(SOAP ConnectorClient.java:571) at com/ibm/ws/management/connector/soap/SOAPConnectorClient.invoke( SOAPConn ectorClient.java:496) at $Proxy28.queryNames(Bytecode PC:22) at com/ibm/ws/management/AdminClientImpl.queryNames(AdminClie at com/ibm/ws/management/AdminServiceImpl.queryNames(AdminServ ------------------ In the exception stack in the systemOut file, the setupCollectionForm is getting a string for queryNames from isServerMbeanRegisterd. The string is built from the following: StringBuffer name = new StringBuffer("WebSphere:type=Server,name ="); name.append(serverName); name.append(",node="); name.append(nodeName); name.append(",process="); name.append(serverName); name.append(",*"); return name.toString();
Local fix
Test Fix is provided
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using the administrative console to * * administer Nodes or Logs and Trace. * **************************************************************** * PROBLEM DESCRIPTION: In large topologies, loading the * * Nodes panel or the Logs and Trace * * panels can be slow. * **************************************************************** * RECOMMENDATION: * **************************************************************** Both these panels were getting the status of the nodes and servers in two different ways before loading the pages.
Problem conclusion
Each panel now only uses one mechanism to retrieve the status of nodes and servers. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.29, 8.0.0.6, and 8.5.0.1. 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
PM74096
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
2012-10-01
Closed date
2012-11-13
Last modified date
2012-11-13
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