I used your startup script as a test, there does seem to be some
differences between v13 and v14.  v13 starts OK but v14 fails, I can see
the temp/tomcat.pid being created but then disappears.


systemctl status -l tomcat
● tomcat.service - Apache Tomcat Web Application Container
   Loaded: loaded (/etc/systemd/system/tomcat.service; disabled; vendor
preset: disabled)
   Active: inactive (dead)

Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
java.net.Socket.<init>(Socket.java:211)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
org.apache.catalina.startup.Catalina.stopServer(Catalina.java:513)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Dec 29 16:50:52 dev.boxshutdown.sh[22941]: at
java.lang.reflect.Method.invoke(Method.java:498)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:403)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:497)
Dec 29 16:50:52 dev.box shutdown.sh[22941]: The stop command failed.
Attempting to signal the process to stop through OS signal.
Dec 29 16:50:53 dev.box shutdown.sh[22941]: Tomcat stopped.


It seems to work OK using jsvc however.  There are no error logs.

Cheers Greg



On Sat, 29 Dec 2018 at 03:27, Steve Demy <steve.d...@shaw.ca> wrote:

> Maybe there is a clue here:
>
> 1)  Eliminated systemd script and rebooted server.
> 2)  Manually started Tomcat using startup.sh run .  Tomcat starts normally.
> 3)  Manually stopped Tomcat using shutdown.sh.  Got stack trace:
>
> Using CATALINA_BASE:   /opt/tomcat
> Using CATALINA_HOME:   /opt/tomcat
> Using CATALINA_TMPDIR: /opt/tomcat/temp
> Using JRE_HOME:        /usr
> Using CLASSPATH:
>  /opt/tomcat/bin/bootstrap.jar:/opt/tomcat/bin/tomcat-juli.jar
> NOTE: Picked up JDK_JAVA_OPTIONS:
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
> Dec 28, 2018 9:57:32 PM org.apache.catalina.startup.Catalina stopServer
> SEVERE: Could not contact [localhost:8005] (base port [8005] and offset
> [0]). Tomcat may not be running.
> Dec 28, 2018 9:57:32 PM org.apache.catalina.startup.Catalina stopServer
> SEVERE: Error stopping Catalina
> java.net.ConnectException: Connection refused (Connection refused)
>         at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.base/java.net
> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
>         at java.base/java.net
> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
>         at java.base/java.net
> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
>         at java.base/java.net
> .SocksSocketImpl.connect(SocksSocketImpl.java:403)
>         at java.base/java.net.Socket.connect(Socket.java:591)
>         at java.base/java.net.Socket.connect(Socket.java:540)
>         at java.base/java.net.Socket.<init>(Socket.java:436)
>         at java.base/java.net.Socket.<init>(Socket.java:213)
>         at
> org.apache.catalina.startup.Catalina.stopServer(Catalina.java:513)
>         at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
>         at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>         at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>         at
> org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:403)
>         at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:497)
>
> Tomcat is shut down - it is absent from the process list.  I think 8005 is
> being contacted *after* Tomcat is shut down, leading to the error.
>
> With systemd involved, the failed shutdown triggers a restart timer, which
> evokes a shutdown command, which fails in the same manner leading to the
> start/stop loop.
>
> Is this a new bug in 9.0.14 or do I have a configuration problem that
> manifests in 9.0.14 for the first time?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to