• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Cannot stop Tomcat

M

MisterB

Guest
I've been having some memory shortages on my vps and found that Tomcat is gobbling up quite a lot of my precious K's. But the weird thing is that it should not be enabled at all (not part of the package) and it is greyed out in the plesk server services page.

So as I don't need it, I think I can do away with the 27 java processes running in the background. However, if I try to stop tomcat by doing either "/etc/init.d/tomcat4 stop" or just "tomcat4 stop" I get this:
Code:
Using CATALINA_BASE:   /usr/share/tomcat4
Using CATALINA_HOME:   /usr/share/tomcat4
Using CATALINA_TMPDIR: /usr/share/tomcat4/temp
Using JAVA_HOME:       /usr/lib/jvm/java
Error occurred during initialization of VM
Could not reserve enough space for object heap

Why can' t I stop Tomcat and is there a way to do this nicely? Also, what would be the best way to prevent it from starting up again.

Memory is stretched, but should still be enough to stop it I think (why do you need memory for that anyway). Current mem status is:
Code:
free -m
             total       used       free     shared    buffers     cached
Mem:          3533       3450         82          0        125       1354
-/+ buffers/cache:       1970       1562
Swap:         3498       2355       1142

Any help much appreciated.
 
Well, for now I just did a "killall java" (checked that there were only tomcat java processes running) and removed the file "/var/lock/subsys/tomcat4". That should do it for now, but I'm still interested in why I couldn't stop it and how to prevent it from starting again (or I'll end up with a cronjob killing java processes).
 
Back
Top