Does anyone recognize what I am doing wrong here?
I'm deploying WLS 10.3 on Windows Server 2003, and following instructions for setting up WLS as a Windows Service in "Managing Server Startup and Shutdown" guide for 10.3. I have the start/stop via Windows SCM working, but I'm having problems implementing graceful shutdown.
Here are the steps taken so far:
1) Installed WLS 10.3 into a new BEA Home (fresh server build, no prev. instances)
2) Created a new domain with one admin server and one managed server
3) Created a
Java class using JMX API to shutdown a server instance, deployed in a jar file to the server. (This was a bit tricky as the examples contain a lot of deprecated code that won't compile).
4) Added a Windows service for the domain admin server:
* included an appropriate delay for the Windows SCM
* appended the path to the stop class jar file in the CLASSPATH
* included the "-stopclass:package.StopClass" argument for the beasvc command
* changed the stdio path so I can capture all of the start/stop messages.
5) Set the "Graceful Shutdown Timeout" in the AdminServer -> Control -> "Start/Stop" tab.
On server startup I see in the log file my jar file (cleanshutdown103.jar) does get added to the classpath, and I also see other things that I am setting, like the stdio redirect and the SCM delay. But the log file also always shows "lpszStopClass = []".
I can independently confirm that the stop class is not loading and that it's stop() method is not invoked because I have included output to stdout, and it isn't happening. What did I miss?
Or as an alternative, is there a better way to have managed servers start automatically with Windows Server boot?
