iceScrum | jquery Not Found After Server Restart – iceScrum

iceScrum Forums Discutez d'iceScrum

4 sujets de 1 à 4 (sur un total de 4)

  • Auteur
    Messages
  • #10661

    Kagilum
    Maître des clés

    The server that are using to host IceScrum had an unexpected restart and since then any attempt to open IceScrum raised the following error:


    Grails Runtime Exception

    Error Details

    Error 500: null
    Servlet:
    URI:
    Exception Message: Module [jquery] depends on resource [/js/jquery/jquery-1.8.2.min.js] but the file cannot be found
    Caused by: Error executing tag : Module [jquery] depends on resource [/js/jquery/jquery-1.8.2.min.js] but the file cannot be found at /WEB-INF/grails-app/views/layouts/main.gsp:29
    Class: ResourceTagLib
    At Line: [29]
    Code Snippet:


    Stack Trace

    org.codehaus.groovy.grails.web.taglib.exceptions.GrailsTagException: Error executing tag
    : Module [jquery] depends on resource [/js/jquery/jquery-1.8.2.min.js] but the file cannot be found at /WEB-INF/grails-app/views/layouts/main.gsp:29

    at gsp_icescrum_layoutsmain_gsp$_run_closure1.doCall(gsp_icescrum_layoutsmain_gsp.groovy:46)

    at gsp_icescrum_layoutsmain_gsp$_run_closure1.doCall(gsp_icescrum_layoutsmain_gsp.groovy)

    at gsp_icescrum_layoutsmain_gsp.run(gsp_icescrum_layoutsmain_gsp.groovy:51)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:745)

    Caused by: java.lang.IllegalArgumentException: Module [jquery] depends on resource [/js/jquery/jquery-1.8.2.min.js] but the file cannot be found

    at org.grails.plugin.resource.ResourceTagLib$_closure8.doCall(ResourceTagLib.groovy:463)

    at org.grails.plugin.resource.ResourceTagLib.invokeMethod(ResourceTagLib.groovy)

    at org.grails.plugin.resource.ResourceTagLib$_closure6.doCall(ResourceTagLib.groovy:387)

    ... 6 more

    There is a js/jquery/jquery-1.8.2.min.js file and the tomcat user can read the contents of that file. We were able to use IceScrum without incident before this restart. We have no idea what might have changed that is causing this problem.

    We are running the latest version of IceScrum (6#13.1, I think) on Centos 6 using Tomcat 7.0.53 and openjdk 1.7.0.65.

    #10926

    Nicolas Noullet
    Maître des clés

    Hello,

    Could you try stopping iceScrum, removing the content of tomcat/work/ and the tomcat/webapps/icescrum/ folders, and then starting iceScrum again?

    #10910

    Kagilum
    Maître des clés

    Nicolas,

    Thanks for your quick reply. We removed the content of the tomcat/work directory and now iceScrum appears to be functioning normally.

    I’m curious about why this fixed the problem. Could you please explain how this works?

    #10911

    Nicolas Noullet
    Maître des clés

    Glad to know that it worked.

    iceScrum static resources such as .js and .css files are processed (concatenation, minification, compression) and stored under the tomcat work directory when iceScrum is started.

    I don’t know why but it seems that these files have been corrupted on your installation, so I suggested that you remove all of them to ensure a clean startup environment. Please note that the work directory must be emptied before any update of iceScrum, as described in the documentation.

4 sujets de 1 à 4 (sur un total de 4)

Le forum ‘Feedback, defects, evolutions’ est fermé à de nouveaux sujets et réponses.