On 28.12.2018 10:59, Steve Demy wrote:
Another fresh install of 9.0.14 using the longer "TimeoutStopSec=180”.
Rebooted the system: sudo systemctl status tomcat
● tomcat.service - Apache Tomcat Web Application Container
Loaded: loaded (/etc/systemd/system/tomcat.service; enabled; vendor preset:
enabled)
Active: active (running) since Fri 2018-12-28 04:30:23 EST; 41s ago
Process: 938 ExecStart=/opt/tomcat/bin/startup.sh (code=exited,
status=0/SUCCESS)
Main PID: 969 (java)
Tasks: 100 (limit: 2262)
CGroup: /system.slice/tomcat.service
└─969 /usr/lib/jvm/jdk-11.0.1/bin/java
-Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom
-Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handle
Dec 28 04:30:23 vps169399 systemd[1]: Starting Apache Tomcat Web Application
Container...
Dec 28 04:30:23 vps169399 startup.sh[938]: Tomcat started.
Dec 28 04:30:23 vps169399 systemd[1]: Started Apache Tomcat Web Application
Container.
That looks good. Let’s try stopping it: sudo systemctl stop tomcat
-- Unit tomcat.service has begun shutting down.
Dec 28 04:31:35 vps169399 shutdown.sh[1619]: 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 04:31:37 vps169399 shutdown.sh[1619]: Tomcat stopped.
Dec 28 04:31:37 vps169399 systemd[1]: Stopped Apache Tomcat Web Application
Container.
-- Subject: Unit tomcat.service has finished shutting down
No trouble yet. Let’s try another start: sudo systemctl start tomcat
-- The start-up result is RESULT.
Dec 28 04:32:29 vps169399 shutdown.sh[1683]: 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 04:32:31 vps169399 shutdown.sh[1683]: Dec 28, 2018 4:32:31 AM
org.apache.catalina.startup.Catalina stopServer
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: SEVERE: Could not contact
[localhost:8005] (base port [8005] and offset [0]). Tomcat may not be running.
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: Dec 28, 2018 4:32:31 AM
org.apache.catalina.startup.Catalina stopServer
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: SEVERE: Error stopping Catalina
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: java.net.ConnectException:
Connection refused (Connection refused)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:403)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.Socket.connect(Socket.java:591)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.Socket.connect(Socket.java:540)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.Socket.<init>(Socket.java:436)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.net.Socket.<init>(Socket.java:213)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
org.apache.catalina.startup.Catalina.stopServer(Catalina.java:513)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
java.base/java.lang.reflect.Method.invoke(Method.java:566)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
org.apache.catalina.startup.Bootstrap.stopServer(Bootstrap.java:403)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:497)
Dec 28 04:32:31 vps169399 shutdown.sh[1683]: The stop command failed.
Attempting to signal the process to stop through OS signal.
Dec 28 04:32:32 vps169399 shutdown.sh[1683]: Tomcat stopped.
That didn’t go so well. The " systemctl start tomcat" encountered a Catalina
stopServer command and it seems unable to use port 8005. Is 8005 not being released
after the previous stop?
I may be seeing this wrong, but why does "sudo systemctl start tomcat" invoke
"shutdown.sh" ?
The tomcat was previously stopped. So of course when "shutdown.sh" is run, and it starts a
new temporary tomcat instance just to send a shutdown command to port 8005, this new
instance finds no-one listening on that port, and complains, which all looks correct.
But why /is/ shutdown.sh being run at all here ?
Again returned to 9.0.13, everything else identical - it works perfectly.
On Dec 27, 2018, at 8:41 PM, Roy Lust <roy.l...@gmail.com> wrote:
The default TimeoutStopSec is 90s ( `cat /etc/systemd/system.conf | grep
Default` ), add "TimeoutStopSec=180" to your systemd script and give it a
try.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
