IntroductionI was trying to solve an issue in our code where the
@ViewScopebeans were not being garbage collected. I spoke a number of times with Manfred Riem at Oracle about the weirdness of this issue. The issue simply put was that we were facing a memory leak where the instances of
@ViewScopeobjects were not being removed from the view map. As a result, the pages were being kept in memory. The view map is limited to 32 views which helped to hide the issue. In most cases, it would not appear to normal users of our application. The issue was suddenly evident when the view contained tens of thousands of objects. 32 x 10k is REALLY BIG! It really never made it to 32, the system would stall and crash at about 6 instances.
The CulpritWe had implemented our own custom
NavigationHandler. This was working quite well on JSF 2.0.x, but a couple of things happened. The JSF implementation was changed to handle another view scope issue, and our implementation of the
NavigationHandlerwas changed from my original code. The new handler did not handle cleaning up the
@ViewScopeobject view map which is stored in the session. Oh, yeah, the view map in the session was the change to the API too.
The SolutionThe solution turned out to be something simple, re-implement the same mechanism in the default
NavigationHandlerto clear the
@ViewScopeobjects from the view map in the session.
Interesting ObservationsI was trying to come up with a mechanism to clear the view map data from the session, and came up with a
SystemEventListenerto test out some ideas. I thought I would share the code for people to see how the map is cleared. This is an approach to the issue, but as I noted, it was actually something missed in our
NavigationHandler. I thought I should post the code for anyone who was looking for ideas on how to manipulate the map, or clear data in it. So without further hesitation. Here is the code.
To implement the listener, you need to add an entry to the faces-config.xml file as shown below.