- Upgrade
- Drive Space low
- Add more storage space (a SSD preferably) (can be done without service interruption if you are using a Logical Volume Manager)
- Out of RAM
- Add more Memory
- This warning is not yet supported for MSSQL or remote databases.
- Index Queue not empty
- Can be ignored if intermittent small numbers
- Contact support if large numbers persist
- HTTP pool too full
- in server.xml increase HTTP pools like to at least double the number of active users. (you may also have a connection per port HTTP and HTTPS)
- DB pool full
- Can be ignored if infrequent
- The default setting of 30 in noodle.properties for DatabaseManager.DB.intranet.Connection.MaxPoolSize is already fairly high so normally this is an indication that the SQL server getting slow.
- Maintenance: rebuild the indexes or upgrade the database
- If the index size is more RAM than the DB is configured to use, add more RAM
- replace spinning storage with SSD (LVMCache supports a mix).
- Increasing the number without ensuring the DB pool was filled because of volume (not latency) will likely cause out of memory or deadlock errors on the database instead of just slowness.
- Reduce load by disabling inactive users, the what's new emails, or backups during working hours.
- User limit
- Remove users from the imported Active Directory security group or contact us for a larger License.
- Additionally and optionally delete disabled users that will not be added back to the imported Active Directory security group.
