You need to run WASServices.exe to remove the service which is located under WASHOME/bin directory or go to Windows Services and change it to manual so that it doesn't start automatically.
This is a discussion on Websphere 6.1 Windows service - Websphere ; I installed WebSphere 6.1 on Windows XP. Server1 is running as a Windows Service by default and everytime the server is started, it starts correctly but returns an exit code 0. The logs show the following: [6/6/07 14:35:25:015 IST] 00000016 ...
I installed WebSphere 6.1 on Windows XP. Server1 is running as a Windows Service by default and everytime the server is started, it starts correctly but returns an exit code 0. The logs show the following:
[6/6/07 14:35:25:015 IST] 00000016 WindowsServic 3 inputRec == Successfully started service.
[6/6/07 14:35:25:015 IST] 0000000a WindowsServic 1 retCode from childProcess.waitFor() is 0
[6/6/07 14:35:25:015 IST] 0000000a WindowsServic 3 -- interrupt the thread that is collecting stdout
[6/6/07 14:35:26:062 IST] 00000014 WindowsServic 3 readAndDisplayServiceLogFile(), caught InterruptedException
[6/6/07 14:35:26:078 IST] 0000000a WindowsServic 3 exitCode = 0
Similarly, when the server is stopped, the server stops successfully but returns exit code 0. Is this a problem?
Also, how can I configure server1 so that it does not run as a Windows service?
You need to run WASServices.exe to remove the service which is located under WASHOME/bin directory or go to Windows Services and change it to manual so that it doesn't start automatically.