Jump to content
  • Jaspersever Scheduled Jobs Failed: Script failed: Uncaught exception


    Swapnil Pawar
    • Features: Scheduler Product: JasperReports® Server

    Error trace:

    ===
    2022-05-24T17:00:17,058 ERROR BrowserService,pool-46-thread-1:211 - Page error: Failed to load resource: net::ERR_FILE_NOT_FOUND
    2022-05-24T17:00:17,059 ERROR BrowserService,pool-46-thread-1:211 - Page error: Failed to load resource: net::ERR_FILE_NOT_FOUND
    2022-05-24T17:00:17,059 DEBUG WebSocketServiceImpl,Grizzly(1):136 - Received message {"method":"Page.domContentEventFired","params":{"timestamp":5115913.90769}} on ws://localhost:16462/devtools/page/F7B207747EBFC55266E406122541D49A
    2022-05-24T17:00:17,060 DEBUG WebSocketServiceImpl,Grizzly(1):136 - Received message {"method":"Log.entryAdded","params":{"entry":{"source":"network","level":"error","text":"Failed to load resource: net::ERR_FILE_NOT_FOUND","timestamp":1.65341161705619e+12,"url":"file:///F:/Vision/apache-tomcat-jasperserver/temp/jr_res_3172272945734714249_Calibri_-en.css","networkRequestId":"13896.4"}}} on ws://localhost:16462/devtools/page/F7B207747EBFC55266E406122541D49A
    2022-05-24T17:00:17,061 ERROR BrowserService,pool-46-thread-1:211 - Page error: Failed to load resource: net::ERR_FILE_NOT_FOUND
    ===

    Note: If you have the schedule to delete the temp folder from the Tomcat directory then below is the solution for your issue.

    Resolution:

    temp folder containing files are required for the server-side exporting. If the temp files are deleted by the scheduler script it will fail the rendering afterward.

    Please set the following property in the jasperreport.properties file (Path: apache-tomcatwebappsjasperserver-proWEB-INFclasses.jasperreport.properties file)

    net.sf.jasperreports.chrome.tempdir.path=C:\Program Files\Apache Software Foundation\apache-tomcat-8.5.77\chrometemp

    Note: create chrometemp folder at path: C:\Program Files\Apache Software Foundation\apache-tomcat-8.5.77\

    so, that the files used for chrome rendering are not deleted by their script because we were given a different path for this chrome temp property.

    Restart the Jasperserver to reflect the changes.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...