Out-of-memory conditions can be difficult to troubleshoot, but you can start by ensuring that sufficient memory was initialized at start up and by checking that Waveset is tracing memory usage levels and alerts.
If you are debugging problems with the admin cache, tracing com.waveset.server.InitAdminCacheThread at level 4 can show the following information:
What were the start-up timings
How long did it take to load the admin and auth caches
What data was loaded
What happened when you added or edited a user from the Waveset Administrator interface