WMS - Tomcat services often down

The memory leak is from a query and that query was originally customization but was further changed by CLI. Therefore CLI inform that they will change the query to optimize it.

For this error, we need to get the error log that will be logged in the java_pidxxxx_hprof. This file can sit in the frontend or backend server, depends on where is the leakage that cause the tomcat to go down. Once get the file, send it to Flux to investigate. Then delete the file from server.