[DIRECTMEMORY-84] Cache should not be a private DirectMemoryServlet field and initialized in init methods

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 0.1-incubating
• Component/s: REST Server
• Labels: REST memory_leak
• Assignee: Olivier Lamy
• Reporter: Jeff Maury
• Created: 25/May/12 12:34
• Updated: 26/May/12 21:14
• Resolved: 26/May/12 21:14

Description

The cache should not be a private DirectMemoryServlet field as there is nothing per the Servlet spec that prevents the Servlet container to hold several instances of the same servlet class. This may lead to memory consumption (as the cache may be created several times) and unexpected behaviour (as one instance may put the object in ITS cache and another one try to retrieve it and either no finding it or returning another object !!!!).
It should be a Servlet context attribute and managed through the ServletContextListener pattern.
As soon as I have completed the work i'm doing on the Closeable stuff, I'm will submit the fix