Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-986

A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.5
    • Fix Version/s: 5.3.6, 5.4
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      With this kind of configuration in web.xml :

      <filter-mapping>
      <filter-name>tapestryFilter</filter-name>
      <url-pattern>/*</url-pattern>
      <dispatcher>ERROR</dispatcher>
      <dispatcher>REQUEST</dispatcher>
      </filter-mapping>
      <error-page>
      <error-code>403</error-code>
      <location>/error/AccessDenied</location>
      </error-page>
      <error-page>
      <error-code>404</error-code>
      <location>/error/NotFound</location>
      </error-page>

      RestoreDirtySessionObjects is generating a NullPointerException with this line :

      Session session = request.getSession(false);

      It seems that the dispatching is done in one single thread, then the initial class to RestoreDirtySessionObjects is delay, and request object is lost.

        Attachments

        1. TAP5-986.txt
          25 kB
          Christophe Cordenier

          Issue Links

            Activity

              People

              • Assignee:
                kaosko Kalle Korhonen
                Reporter:
                ccordenier Christophe Cordenier
              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: