1 Reply Latest reply on Jul 18, 2019 11:36 AM by nydn

    404 on some static files after ORDS upgrade

    nydn

      Hey there,

       

      We've upgraded our ORDS installation from 18.1.1 to 19.1.0 two days ago and one of the workspaces have some strange issue with not loading static files in APEX.

      There are 5 different workspaces each with their own database schemas. All working fine, except one, where every application (either old or newly created) have issues with loading static files,

      for example for the builtin app-icon.svg or app-icon.css we get a 404 and if try to load the url manually:

      "URLMappingNotFoundException [statusCode=404, reasons=[The request could not be mapped to any database. Check the request URL is correct, and that URL to database mappings have been correctly configured]]"

       

      Also the same with plugins, a bunch of errors like:

      The script from “http://server/ords/dev/<workspace>/r/20000/files/plugin/43780560160356328/v1/select2.full.min.js” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.

      Loading failed for the <script> with source “http://server/ords/dev/<workspace>/r/20000/files/plugin/43780560160356328/v1/select2.full.min.js”.

      The script from “http://server/ords/dev/<workspace>/r/20000/files/plugin/43780560160356328/v1/select2-apex.js” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type.

      Loading failed for the <script> with source “http://server/ords/dev/<workspace>/r/20000/files/plugin/43780560160356328/v1/select2-apex.js”.

      ... and so on.

       

      With every imported plugin. And again this is happening in only one of the workspaces/schemas, all the others are fine. Also this is a DEV system and the PROD system is still unupgraded and works fine, that's why I think it's related to the ORDS upgrade somehow however I'm not sure since it's an APEX issue.

       

      What we tried so far:

      - java -jar ords.validate (no errors, but does not solve the problem, we still have the logs from the upgrade and validate if needed)

      - recreate the workspace on the schema with the old apps imported

      - create a totally new workspace on the same schema

      - register/deregister the ORDS schema in APEX

       

      ORDS is deployed onto Tomcat8 and running behind an Apache reverse proxy, so nothing extreme.

      Any idea what could be wrong with that one database schema or workspace or anything?

       

      Thanks in advance!

        • 1. Re: 404 on some static files after ORDS upgrade
          nydn

          Okay, I did an ORDS setup

          java -jar ords.war setup --database <dbname>

          without an uninstall before or anything, redeployed the war and it fixed the issue with the problematic workspace/schema, files loading correctly again.

          Still don't know what went wrong and where and I'm curious if anyone have any idea.