About every week or so, our Windows FileMaker Server memory spikes to 100%. It's so bad we can't disconnect users, close files, and sometimes we can't even log into the console or the databases using External Accounts (Active Directory), nor remote into the Windows Server—at which we sometimes need a VM admin to reboot the whole server.
The problem almost always visibly begins during one of our large nightly ODBC imports from Oracle, when it suddenly starts using much more memory than usual to import. It usually gets critical shortly after the nightly import begins (probably during verification). There have been a few critical spikes during the day, but these only seem to happen after an unusual memory increase during the night.
Here's a memory chart showing several of the strokes our server has suffered:
This is one of the more relevant system events that occur during the incident:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: fmserver.exe (2276) consumed 97847312384 bytes, java.exe (3592) consumed 2542219264 bytes, and java.exe (2504) consumed 411545600 bytes.
FileMaker Server Version 220.127.116.116
Runs on a VM with the following configuration:
Much more memory than needed was added in hope of avoiding the issue, but it didn't really help much, other than delaying the inevitable by minutes or hours.