File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Tomcat and the fly likes Invalid command 'SHUTDOW' received - Windows 7 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Invalid command Watch "Invalid command New topic
Author

Invalid command 'SHUTDOW' received - Windows 7

Fred Ouimet
Greenhorn

Joined: Jul 02, 2011
Posts: 2
Hi!

I'm having problems shutting down Tomcat on my Windows 7 Home Premium laptop. I tried Tomcat 6.0.29, 6.0.32, 7.0.14 and 7.0.16 and all give the same result. Basically, Tomcat starts fine, either from the DOS command line or from Eclipse. The problem is when I shutdown the server, I receive WARNING: StandardServer.await: Invalid command 'SHUTDOW' received. This happens from a default Tomcat installation (unzipped the package), no changes to the server.xml file or any other files. Seems that there is something trimming the last byte from the command. If I run the server in DOS, I can execute shutdown.bat over and over again until the server catches the command properly (See catalina log, the server responded on the 14th shutdown command). It's intermittent too. Sometimes, the server responds properly on the second or third command but never on the first one.

I tried the following:
- changed the admin port (8005) to something else, 55551 for example, but still gives the problem.
- I turned off my Avast resident shields and firewall to no avail.
- Using Putty telnet, if I connect to port 8005 (or whatever I changed it to) in raw mode and type SHUTDOWN, it works just fine.
- I used netstat -an | find "8005" and only see one process LISTENING
- Tried using JDK1.5.0_22 instead of JDK1.6.0_25 to no avail.
- Cleaned out event viewer and don't see any new entries appearing.

I tried the same tomcat releases on two different Windows XP desktops and a mac and there is no such problems. I'm thinking it has to do with Windows 7 or something else running on my laptop. Anyone else has this kind of problem or could someone provide me with some tips on how I could solve this? I've tried Geronimo-Jetty and Glassfish and don't seem to have any problems shutting those down.

Thanks for your help!

Fred.

--------------------------------------------------------------------------------
Catalina.log:

2-Jul-2011 9:41:10 PM org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.20.
2-Jul-2011 9:41:10 PM org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
2-Jul-2011 9:41:11 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-8080"]
2-Jul-2011 9:41:11 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-apr-8009"]
2-Jul-2011 9:41:11 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1588 ms
2-Jul-2011 9:41:11 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
2-Jul-2011 9:41:11 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.16
2-Jul-2011 9:41:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory docs
2-Jul-2011 9:41:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory examples
2-Jul-2011 9:41:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory host-manager
2-Jul-2011 9:41:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory manager
2-Jul-2011 9:41:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
2-Jul-2011 9:41:12 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
2-Jul-2011 9:41:12 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8009"]
2-Jul-2011 9:41:12 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 942 ms
2-Jul-2011 9:41:19 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:24 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:26 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:28 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:29 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:30 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:31 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:32 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:34 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:35 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:36 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:37 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:39 PM org.apache.catalina.core.StandardServer await
WARNING: StandardServer.await: Invalid command 'SHUTDOW' received
2-Jul-2011 9:41:40 PM org.apache.catalina.core.StandardServer await
INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance.
2-Jul-2011 9:41:40 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-apr-8080"]
2-Jul-2011 9:41:41 PM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-apr-8009"]
2-Jul-2011 9:41:42 PM org.apache.catalina.core.StandardService stopInternal
INFO: Stopping service Catalina
2-Jul-2011 9:41:42 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["http-apr-8080"]
2-Jul-2011 9:41:42 PM org.apache.coyote.AbstractProtocol stop
INFO: Stopping ProtocolHandler ["ajp-apr-8009"]
2-Jul-2011 9:41:42 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["http-apr-8080"]
2-Jul-2011 9:41:42 PM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler ["ajp-apr-8009"]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Invalid command 'SHUTDOW' received - Windows 7
 
Similar Threads
Why jdk6x is not compatiable with Tomcat7? why jdk7x compiled classes are not working in jdk6x
tomcat server Native library problem
Trouble restarting Tomcat 6.0.30 with Eclipse
The Request Resource is not available.
tomcat failed to initialize