"Session invalid" error caused by improper VM time zone settings

There should be documentation alerting the user to check the time zone settings on their virtual machine to make sure that it aligns with the time zone of the database.

When a user logs in, two timestamps are created in PM_USER_SESSION. The first time stamp called ENTRY_DATE is when the user logs in to the web client. The second time stamp, EXPIRED_DATE, is when that session is no longer valid. If the time zone of the virtual machine is far enough ahead, then the current time of the VM will always be after the EXPIRED_DATE, leading to a cryptic "Session invalid" error in Wildfly logs.

The fix is to run timedatectl (or some equivalent) to change the time zone of the VM.