Can't install server update - service hangs on stopping in Windows 08 R2

[stackerman]

So we have had problems stopping the CF App Server service in Windows.  Admittedly, this fails from GUI, Command Line, etc even logged in as Local Administrator.  The service hangs on stopping and eventually after about 10 minutes you can "refresh" (in the GUI) and see that it has finally stopped.  It is taking so long, however, that the patching fails for the update so we don't know how to get the Server update applied.

Like I stated, this happens from GUI or command line whether patching or not - any simple attempt to stop/restart the CF App Server service will just hang and will eventually stop - just not very quickly.  (and not quick enough for the server update to successfully complete).

Any ideas?  Any help/workaround to get the server update applied would be appreciated....

[Priyank Shrivastava.]

Hi,

Can you please let me know if you have followed the Lockdown guide on your server?

Thanks,

Priyank

[stackerman]

portions of it - but I don't believe our dev guys have applied it all....

[Priyank Shrivastava.]

Please check if they followed this portion in lockdown guide.

4.3.4 Tomcat Shutdown Port

Tomcat listens on a TCP port (8007 by default, may differ if multiple instances) for a SHUTDOWN command.

When the command is received on the specified port the server will shutdown.

Edit the file

{cf.instance.home}/runtime/conf/server.xml

and locate the

line similar to:

<Server port="8007" shutdown="SHUTDOWN">

Change

8007

to

-

1 to disable this feature, or to random port number. Tomcat should only listen on 127.0.0.1

for this port, however you should also ensure that your firewall does not allow extern

al connections to this port.

Also consider changing the shutdown command, that is the value of the

shutdown

attribute of the

Server

tag. This string is essentially a password used to shut down the server locally when the port is enabled.

Next look in:

{

cf.instance.home}/bin/port.properties

and edit the following line to match

server.xml

port value:

SHUTDOWN=8007

Ensure that global read permission is denied for both these files

Please note:

Changing the port setting may cause the shutdown of the ColdF

usion Service on Windows

to fail, you may need to kill the process manually to stop ColdFusion. The Linux shutdown script

should still work properly when the port is changed.

Thanks,

Priyank

[stackerman]

That control doesn't appear to be applied, unfortunately.  Any other ideas?