Problem with tomcat stop

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

stefank2

Hello,

when I try to stop alfresco I get the following error message from tomcat:

Using CATALINA_BASE:   /opt/alfresco-4.0.d/tomcat
Using CATALINA_HOME:   /opt/alfresco-4.0.d/tomcat
Using CATALINA_TMPDIR: /opt/alfresco-4.0.d/tomcat/temp
Using JRE_HOME:        /opt/alfresco-4.0.d/java
Using CLASSPATH:       /opt/alfresco-4.0.d/tomcat/bin/bootstrap.jar
May 12, 2012 8:47:01 PM org.apache.catalina.startup.Catalina stopServer
SEVERE: Catalina.stop: 
java.net.ConnectException: Connection refused
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:529)
   at java.net.Socket.connect(Socket.java:478)
   at java.net.Socket.<init>(Socket.java:375)
   at java.net.Socket.<init>(Socket.java:189)
   at org.apache.catalina.startup.Catalina.stopServer(Catalina.java:408)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:338)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:416)
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I am using ArchLinux, does anyone have an idea what could cause this?
I could rule out most of the common reasons for this problem, like another program using port 8080 and tomcat not running.

Greetings,

Stefan

afaust

Hello,

this problem usually has nothing to do with some other program using the HTTP connector on port 8080, rather the port 8005 (default) which the Tomcat SHUTDOWN listener is using.
Another possibility could be a firewall issue - the shutdown command opens a TCP connection to the SHUTDOWN listener and this may fail either due to a firewall blocking the request or an IP-related connectivity issue (e.g. localhost mapping to an IPv6 address while the listener is bound to the IPv4 host address).

Regards
Axel