Fixes are available
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.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.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
APAR status
Closed as program error.
Error description
In this case, a START command is not used to start the server, rather a command used by an automation product that the server is starting through automation so the product correctly reports the server up or down state. When this happens, the node agent is not able to monitor that the server has actually started and report this status to the dmgr to then report this via the admin console. The server does start ok. The node agent will show this message: ADMN1000I: An attempt is made to launch AppServer on node Shortly followed by this FFDC: FFDC Exception:com.ibm.ws.process.exception.ProcessOpException SourceId:com.ibm.ws.process.WS390ProcessImpl.id ProbeId:186 Reporter:com.ibm.ws.process.WS390ProcessImpl@777b36b9 com.ibm.ws.process.exception.ProcessOpException: Invalid process object. nativeHandle (mvsToken) is 'null' at com.ibm.ws.process.WS390ProcessImpl. checkNativeHandle(WS390Proce ssImpl.java:742) at com.ibm.ws.process.WS390ProcessImpl. id(WS390ProcessImpl.java:499 ) at com.ibm.ws.management.nodeagent.NodeAgent. launchProcessPrivate(N odeAgent.java:1376) Then about 10 minutes later, this FFDC: FFDC Exception:java.net.SocketTimeoutException SourceId:com.ibm.ws.management.nodeagent.NodeAgent.waitForServer Init ProbeId:368 Reporter:com.ibm.ws.management.nodeagent.NodeAgent@38608807 java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:480) at java.net.ServerSocket.implAccept(ServerSocket.java:479) at java.net.ServerSocket.accept(ServerSocket.java:447) at com.ibm.ws.management.nodeagent.NodeAgent. waitForServerInit(Node Agent.java:1811) And this error message: ADML0040E: The process timed out waiting for server "AppServer" initialization: 600 seconds
Local fix
use the START command to start the server from the admin console
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0, and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * will hang when starting an application * * server from the Administrative Console * * with a custom START command that does * * not begin with "START". * **************************************************************** * RECOMMENDATION: * **************************************************************** The Admin Console allows a user to specify a custom START command. If this custom START command does not begin with "START", when an attempt is made to start an application server from the Administative Console, instead of the starting, the server will hang and a message like this may be issued in the node agent job log: BBOO0221W: ADML0040E: The process timed out waiting for server "<server name>" initialization: 600 seconds
Problem conclusion
The code has been updated to allow custom START commands in the Administrative Console that do not begin with "START". APAR PI44409 is currently targeted for inclusion in Fix Packs 8.0.0.12, and 8.5.5.8 of WebSphere Application Server. In addition, sysroute APAR PI46371 will resolve the issue for WebSphere Application Server V7.0 in Fix Pack 7.0.0.41. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI44409
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-07-06
Closed date
2015-08-05
Last modified date
2015-11-03
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
R850 PSY
UP
Document Information
Modified date:
11 January 2022