Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-2085

When registering a bypass filter of class URIStartsWithVoter causes the server to die

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Critical
    • None
    • 3.5.4
    • core
    • None

    Description

      All I did was follow the instructions on the wiki exactly as they are written... After I created the nodeData for the class of the bypass filter - and before I could put any more information in it - the server died with this message:

      http://wiki.magnolia.info/display/WIKI/HowTo+Setup+Custom+404+Handler

      Mar 11, 2008 5:59:42 PM org.apache.catalina.core.StandardWrapperValve invoke
      SEVERE: Servlet.service() for servlet default threw exception
      java.lang.NullPointerException
      at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:97)
      at info.magnolia.cms.filters.MgnlMainFilter.doFilter(MgnlMainFilter.java:195)
      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
      at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:354)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
      at java.lang.Thread.run(Thread.java:619)

      I couldn't do anything to get it back at that point, and had to restore the app from a backup.

      It was as if the filter was being immediately put into effect, before it was even configured fully. Even if it were configured completely wrong, there is really no excuse for the server to completely die because of a bad user input.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              ryangardner Ryan Gardner
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD