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 Bug
    • Status: Resolved
    • Priority: Major 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.

      1. TAP5-986.txt
        25 kB
        Christophe Cordenier

        Issue Links

          Activity

          Christophe Cordenier created issue -
          Christophe Cordenier made changes -
          Field Original Value New Value
          Attachment TAP5-986.txt [ 12430259 ]
          Christophe Cordenier made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Duplicate [ 3 ]
          Ulrich Stärk made changes -
          Link This issue is duplicated by TAP5-1017 [ TAP5-1017 ]
          Ulrich Stärk made changes -
          Resolution Duplicate [ 3 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          Kalle Korhonen made changes -
          Assignee Kalle Korhonen [ kaosko ]
          Kalle Korhonen made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Fix Version/s 5.3.6 [ 12322961 ]
          Fix Version/s 5.4 [ 12316401 ]
          Resolution Fixed [ 1 ]
          Howard M. Lewis Ship made changes -
          Summary sendError in onActivate / Tapestry error dispatching A request can fail with an NPE in some cases, when a Tapestry page is acting as the servlet container error page

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Development