4 Replies Latest reply on Jun 6, 2019 12:15 PM by AndyH

    ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL

    AndyH
    AndyH Jun 6, 2019 12:19 PM

      We have an ORDS configuration using customURL.

       

      Upgraded ORDS from 18.4 to 19.1, all APEX access works without error but RESTful access fails with a 404 and a message referring to not finding the database and URLMapping.

       

      Returned to ORDS 18.4 and all works.

       

      I noticed a similar thread in July 2018 regarding an upgrade between 18.1 and 18.2 - at the time ossiossi was talking with thatJeffSmith-Oracle about raising a bug with Oracle, but I've not been able to find a reference to it and a workaround.

       

      Anyone else had this issue? Anyone resolved it?

       

      --

      Andy

       

      Message was edited by: AndyH Original ORDS version was 18.4, not 18.1

      • 1197 Views
      • Tags:
        • 1. Re: ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL
          thatJeffSmith-Oracle
          thatJeffSmith-Oracle Jun 5, 2019 3:55 PM (in response to AndyH)

          Would need more details on your scenario to provide any feedback or advice

          • 2. Re: ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL
            AndyH
            AndyH Jun 6, 2019 12:20 PM (in response to thatJeffSmith-Oracle)

            Jeff,

             

            We have an APEX (5 upgraded to 18) application and some REST interfaces (migrated from APEX to ORDS). We use customURL in the ORDS configuration. ORDS is running on Tomcat.

             

            When using ORDS 18.4 we have no issues running either APEX or the REST interfaces.

             

            When we use ORDS 19.1 APEX runs, but using the REST interfaces gets a 404 error returned from ORDS saying that the database cannot be found and inferring that it's a mapping error - we're not using database mapping.

             

            If we swap the 19.1 ords.war file with the 18.1 ords.war file everything works i.e. no configuration file changes.

             

            This sounded similar to the issue that ossiossi reported when he upgraded from ORDS 18.1 to ORDS 18.2, but I couldn't find any further details on his issue.

            • 3. Re: ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL
              thatJeffSmith-Oracle
              thatJeffSmith-Oracle Jun 5, 2019 5:35 PM (in response to AndyH)

              show us the route patterns, how your pools are defined, and turn debug on in ORDS and share the output (easier to print to screen, but also from console/catalina is fine)

              • 4. Re: ORDS 19.1 RESTFul-Service 404 not found Messages with db.customURL
                AndyH
                AndyH Jun 6, 2019 12:15 PM (in response to thatJeffSmith-Oracle)

                Jeff, our REST calls are of the form:

                 

                {{{

                BEGIN

                 

                  ORDS.ENABLE_SCHEMA(

                  p_enabled => TRUE,

                  p_schema => 'IDS',

                  p_url_mapping_type => 'BASE_PATH',

                  p_url_mapping_pattern => 'ids',

                  p_auto_rest_auth => FALSE);

                  

                  ORDS.DEFINE_MODULE(

                  p_module_name => 'IDS REST V1',

                  p_base_path => 'rest/v1/',

                  p_items_per_page => 25,

                  p_status => 'PUBLISHED',

                  p_comments => NULL);


                  ORDS.DEFINE_TEMPLATE(

                  p_module_name => 'IDS REST V1',

                  p_pattern => 'workspaces/{name}/nodes/{node_no}/{copo_id}/mprns/',

                  p_priority => 0,

                  p_etag_type => 'HASH',

                  p_etag_query => NULL,

                  p_comments => NULL);


                  ORDS.DEFINE_HANDLER(

                  p_module_name => 'IDS REST V1',

                  p_pattern => 'workspaces/{name}/nodes/{node_no}/{copo_id}/mprns/',

                  p_method => 'GET',

                  p_source_type => 'plsql/block',

                  p_mimes_allowed => '',

                  p_comments => NULL,

                  p_source =>

                }}}

                 

                The pools are as defined by running a standard ORDS setup and then the defaults.xml file was modified to use the customURL.

                 

                Screen dump:

                 

                ORDS_URL.png