Large number of alarms can cause the alarm service to crash the tomcat

When extracting alarms from the database backend, the result set can be very large. So large that it can exhaust the available memory of the tomcat.
This is due to the query and result set is not limited in any way, resulting in a potentially massive resultset, making the jvm garbage collect excessivly, which in turn results in a OutOfMemoryError due to GC overhead.