PQ53166: IN AES, NO NT SERVICE CREATED TO STOP AND START WAS WITHOUT LEAVING SYSTEM LOGGED ON. NO AUTOMATIC RESTART ON REBOOT. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as program error. Error description Websphere AeS, 4.0.0 and 4.0.1 on Windows NT. Installation does not create a system service. If NT Tool, SRVANY.EXE is used as workaround to create service, then whenever someone interactivel y logs onto the system and then logs off, the JVM dies. This is reported in defect 105801. I have given customer workaround for starting the service remotely once interactive logon is quit. Then service still dies on exit, but it gives customer a way to restart without having to reboot the box. SRVANY WINDOWS NT SERVICE WAS WSASLocal fix Using SRVANY.EXE, which is part of Windows NT Resource Kit, you can create a service that starts the startServer.bat file. This will restart the service when the system reboots, if anyone has to interactively log onto the system, upon logging off, the java process will die. At that point, you will have to bring up Server Manager for Windows NT on ANOTHER system on the same network and then from the Services Panel stop/start the created service on the Websphere server. This may not work in all instances.Problem summary without having to logoff and logon to stop and start.Problem conclusion Temporary fix Comments to 4.0.1 AeS on Windows are located in this directory.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ53166
IBM Group: Software Group
Modified date: Oct 26, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.