addressed an issue where the counter service caused the connection pool to run out of connections. This fix works well for the most part, but there is a side effect where the database terminates the jdbc connection on deployments that have long periods of inactivity (mysql default is 8 hours).

The most generic solution for this is to create a Job that will sent heartbeats (a simple query) to let the database know that this connection is still alive at a default interval of 60 minutes. This is configurable via portal-ext.properties:

#

1. Set the interval in minutes for the ConnectionHearbeatJob.
   # This will determine how often the database is polled for long running
   # connections and will prevent the database from disconnecting the socket
   # prematurely.
   #
   counter.connection.heartbeat.job.interval=60