"bin/oodt stop" won't stop tomcat causing system to go out of memory

[chrismattmann]

Imported from apache/drat#128: apache/drat#128

Original author: @IMS94
Original state: closed
Created: 2018-05-16T06:24:07Z
Updated: 2020-10-04T18:45:49Z
Closed: 2020-10-04T18:45:49Z

---

I was testing OODT with DRAT and saw that the tomcat process created by the bin/oodt start command doesn't get killed/stopped on bin/oodt stop which causes the RAM to go out of memory if we run oodt start multiple times.

Below is an example in my machine where there were many tomcat processes running.

[chrismattmann]

Resolved by 9d559a7: refreshed the OODT start/stop scripts to avoid exec during stop/start handling and verified a staged run stops DRAT/OODT services cleanly with no listeners left on 8080/9000/9001/9002.

[chrismattmann]

Imported comments from apache/drat#128: apache/drat#128

Comment by @chrismattmann on 2018-05-24T22:57:38Z

hmmm this sounds like a big problem @IMS94 how should we fix it?

---

Comment by @IMS94 on 2018-05-25T01:02:22Z

@chrismattmann We can call "tomcat stop" like command in bin/oodt:158. But this depends on whether the Tomcat executable (or the command used to start Tomcat) also support stopping via a command.

---

Comment by @chrismattmann on 2018-05-26T18:45:40Z

got it. Well let's try and make this robust thanks @IMS94 i'm available to test

---