Recently the company projects often OOM, dump the stack information found in the User object accounted for 80% of memory,
Check the code inquiry found no place full amount of user information, the phenomenon occurs continuously for a week, are caused by the User object,
A closer look at the log found extremely frequent interface calls, combined with a code analysis found a blocker layer on the interface, which user session information verification,
Problems can be concluded here basically, the user interface information every request into a query session, and the session timeout is not set (default half hour),
When there will be access to large memory surge,
Rehabilitation program: Redis cache information into the next session, do share session