PQ67353: ADMINSERVICE.EXE PROCESS GET STARTED SUCCESSFULL,BUT AFTER SOME TIME ADMINSERVICE.EXE PROCESS GET EXITED. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer scenarios: Every night there server get recycled, aroun d morning when customer walks into the office first thing they c heck there services panel in W2K to check the all serive is bein g running properly. They also notice some morning in services wi ndows on W2K for WAS service as showing as not started. WAS IBM WS AdminServer 4.0 to be startup type automatic. When services s how as not started in services panel then they check the PID on windows task manager. In task manager also reports as not runnin g. But there are some java process running, Console works fine.Local fix Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server users running * * on Win2k or WinNT platforms. * **************************************************************** * PROBLEM DESCRIPTION: Admin service terminates but admin * * server and app servers run without * * problems. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a hard-coded 8 minute timeout that admin service uses when it starts admin server. If admin server does not write back on admin service port within this period, then admin service will terminate with no explanation. The admin server does not send a "ready" message to admin service until it has received one from all the app servers that it needs to start and, in some cases this may take longer than 8 minutes.Problem conclusion This APAR corrects that problem by setting the default timeout for this period to be INFINITE (i.e., no timeout). This APAR also introduces two additional properties that the user can add to admin.config to modify some of the admin service behavior. For additional information on these properties, see below: This APAR exposes two new properties that can be added to admin.config to modify the behavior of the admin service for WebSphere on Windows platforms. These properties are: 1) com.ibm.ejs.sm.adminService.verboseLogging If this property is set to a non-zero value as in: com.ibm.ejs.sm.adminService.verboseLogging=1 then the admin service will produce additional entries in the Windows Application Event Log. 2) com.ibm.ejs.sm.adminServce.waitForTimeOut This property sets the number of seconds that the admin service will wait for the admin server to notify it that it (the admin server) and all app servers that it started have completed their startup. The default value for this property is 0 which means that the admin service will not timeout waiting for notification from the admin server. UNDER NORMAL CIRCUMSTANCES THE USER SHOULD NOT NEED TO SET THIS PROPERTY FROM ITS DEFAULT VALUE.Temporary fix Test Fix placed on: wasdoc0:/APARS/PQ67353/windows4.04/PQ67353_eFix.jar and readme placed on: wasdoc0:/APARS/PQ67353/windows4.04/README.txtComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67353
IBM Group: Software Group
Modified date: Nov 13, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.