Uploaded image for project: 'Groovy'
  1. Groovy
  2. GROOVY-5747

First call to Groovlet succeeds but subsequent calls return 404

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.5
    • Fix Version/s: 2.0.6, 1.8.9
    • Component/s: GroovyScriptEngine
    • Labels:
      None
    • Environment:
      Groovy 2.0.5
      Tomcat 6.0.35
      Java 1.6.0_35
      Windows 7 64-bit
      Also same error running in Google App Engine (GAE) 1.7.2-1

      Description

      .groovy extension mapped in web.xml and .groovy script located in WEB-INF/groovy

      First call to test.groovy works
      http://localhost:8080/test/test.groovy

      INFO: Groovy servlet initialized on groovy.util.GroovyScriptEngine@6f03de90.
      Oct 8, 2012 1:52:39 PM org.apache.catalina.core.ApplicationContext log

      All subsequent calls return 404
      http://localhost:8080/test/test.groovy

      INFO: Server startup in 773 ms
      GroovyServlet Error: script: '/test.groovy': Script not found, sending 404.

      Note the .groovy mapping works corrected in Groovy 1.8.4 through 2.0.1 but appears to have broken as 2.0.2 through 2.0.5.

      Attached sample WAR removed the groovy jar which was originally packed as "WEB-INF/lib/groovy-all-2.0.5.jar"

      Related discussion can be found here:
      http://stackoverflow.com/questions/8228873/groovyservlet-returning-404-on-all-requests-after-successfully-loading-once

        Attachments

        1. groovy-5747-testcase.zip
          2 kB
          Ryan Baumann
        2. test.war
          2 kB
          jason mathews

          Activity

            People

            • Assignee:
              blackdrag Jochen Theodorou
              Reporter:
              gjmathews1 jason mathews
            • Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: