PQ54306: IN AES, NO WINDOWS NT SERVICE IS CREATED WHEN INSTALLED. IF YOU LOGOFF THE SYSTEM, THE JAVA PROCESS DIES. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
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 interactive 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 WSAS PQ53116 will work for W2K. This is for NT 4.0.Local fix No successfully working workaround know for Windows NT 4.0Problem summary **************************************************************** * USERS AFFECTED: WebSphere Application Server 4.0 AEs Users. * **************************************************************** * PROBLEM DESCRIPTION: WASService.exe fixed in 105801.1 does * * not work on Windows NT. One can add * * Service, but on service start no * * running java process can be seen in * * the task manager. * **************************************************************** * RECOMMENDATION: * **************************************************************** Seen following errors on NT: 1) Calling CreateProcess and attempting to output the results of startServer.bat to a log file doesn't work on NT (since this is bug in cmd.exe which comes with NT). 2) The SERVICE_STATUS structure contains a dwCheckPoint variable that needs to be incremented every so often so that the Service Manager knows that something is still going on. Otherwise, it thinks the process is hung and pops up and error dialog.Problem conclusion Fixed: 1) Added a check to see if we are on NT 4 and if so we don't send the results to a file (this will take care of the bug in cmd.exe). 2) Fixed dwCheckPoint variable in the SERVICE_STATUS structure so that Service Manager is aware that process is going on.Temporary fix Comments
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 #: PQ54306
IBM Group: Software Group
Modified date: Nov 29, 2001
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.