What is the lifecycle of a jsp PageContext object - is it threadsafe?

Question

Are jsp PageContext objects created and destroyed as part of the http request-response cycle or are they cached and reused between requests.

PageContext has life-cycle methods that suggest reuse between requests. ie initialize(), release().

If they are reused this could pose serious concurrency problems: if two http requests arrive, requesting the same jsp page, and each request is processed by its own thread, but sets attributes on a shared PageContext object, they will render each others' content.

Any help appreciated. By the way I am using the servlet container embedded in Apache Sling.

Peter Štibraný · Accepted Answer · 2012-03-06T10:09:11.140

4

PageContext are only available from your JSP page. If your request was first handled by the servlet, and then forwarded to JSP page (using RequestDispatcher.forward), pageContext is only available on this JSP page, but there is no way to access it from the servlet (because there was no pageContext yet at that time).

From JSP page point of view, it is getting new pageContext every time it is called. Page contexts may be pooled internally, but not shared by multiple JSP pages at the same time.

initialize and release methods have this comment: "This method should not be used by page or tag library authors." Just forget about them.

edited Mar 06 '12 at 10:09

answered Mar 06 '12 at 09:56

Peter Štibraný

32,463
16
90
116

That is good to know, but then why does PageContext have life-cycle methods at all, if it is not recycling them ???? – murungu Mar 06 '12 at 10:02
@murungu: container may use pool of page context objects. These methods are called by the container to indicate beginning and end of page context usage. Page context should do necessary initialization or cleanup. These methods are not meant to by called by JSP page author. – Peter Štibraný Mar 06 '12 at 10:07

score 3 · Answer 2 · edited May 23 '17 at 12:34

Peter is correct. The PageContext is provisioned for the scope of processing a page. Consumers should not keep a reference to these instances outside this scope which implicitly means instances shouldn't be accessible outside the current thread.

Example JSP processing code from the JSP 2.2 specification:

public class foo implements Servlet {
// ...
public void _jspService(HttpServletRequest request, HttpServletResponse response)
               throws IOException, ServletException {
  JspFactory factory = JspFactory.getDefaultFactory();
  PageContext pageContext = factory.getPageContext(
      this,
      request,
      response,
      null, // errorPageURL
      false, // needsSession
      JspWriter.DEFAULT_BUFFER,
      true // autoFlush
    );
  // initialize implicit variables for scripting env ...
  HttpSession session = pageContext.getSession();
  JspWriter out = pageContext.getOut();
  Object page = this;
  try {
    // body of translated JSP here ...
  } catch (Exception e) {
    out.clear();
    pageContext.handlePageException(e);
  } finally {
    out.close();
    factory.releasePageContext(pageContext);
  }
}

How the PageContext instance is provisioned (from pools or instance creation) is an implementation detail of the container.

What is the lifecycle of a jsp PageContext object - is it threadsafe?

2 Answers2

Linked