We recently experienced a rather unfortunate issue, which we were unable to resolve on our own.  This issue has caused confusion within the management regarding update to newest versions.  The problem we are experiencing is that the server occasionally stops responding, requiring a reboot of Tomcat.  This issue can be triggered by two main factors: the checkout of a developer at the stand or the transfer of a branch to the stand via an archive.  Regardless of the scenario, the server's behavior remains the same when certain pools are modified, such as sections or flows.  However, other rules do not typically present any issues. A single server is used instead of a cluster now.

There is an example of problem at 11:07-11:10 in attached logs.