5 Replies Latest reply on Sep 19, 2019 1:21 PM by Chris_Gooch

    ORDS 19.1 db.customURL functionality

    user4716747

      I'm getting this error when I'm using db.customURL functionality in ORDS 19.1 (ords-19.1.0.092.1545.zip):

      404 Not Found

      • 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

       

      I am not getting the above error when I'm using ORDS 18.4 (ords-18.4.0.354.1002.zip).

       

      I wonder if this is a known issue in ORDS 19.1 (ords-19.1.0.092.1545.zip).

       

       

      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]]

      at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:125)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.auth.external.ExternalSessionFilter.doFilter(ExternalSessionFilter.java:59)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.rt.authentication.apex.ApexSessionQueryRewriteFilter.doFilter(ApexSessionQueryRewriteFilter.java:58)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.cors.CORSResponseFilter.doFilter(CORSResponseFilter.java:88)

      at oracle.dbtools.http.filters.HttpResponseFilter.doFilter(HttpResponseFilter.java:45)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.filters.AbsoluteLocationFilter.doFilter(AbsoluteLocationFilter.java:65)

      at oracle.dbtools.http.filters.HttpResponseFilter.doFilter(HttpResponseFilter.java:45)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.errors.ErrorPageFilter.doFilter(ErrorPageFilter.java:85)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.secure.ForceHttpsFilter.doFilter(ForceHttpsFilter.java:74)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.auth.ForceAuthFilter.doFilter(ForceAuthFilter.java:44)

      at oracle.dbtools.http.filters.HttpFilter.doFilter(HttpFilter.java:47)

      at oracle.dbtools.http.filters.FilterChainImpl.doFilter(FilterChainImpl.java:64)

      at oracle.dbtools.http.filters.Filters.filter(Filters.java:67)

      at oracle.dbtools.http.entrypoint.EntryPoint.service(EntryPoint.java:82)

      at oracle.dbtools.http.entrypoint.EntryPointServlet.service(EntryPointServlet.java:102)

      at oracle.dbtools.entrypoint.WebApplicationRequestEntryPoint.service(WebApplicationRequestEntryPoint.java:50)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

      at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)

      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:202)

      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)

      at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490)

      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)

      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)

      at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:678)

      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)

      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)

      at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:408)

      at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)

      at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:853)

      at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1587)

      at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

      at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

      at java.base/java.lang.Thread.run(Thread.java:835)

       

      Thanks!

        • 1. Re: ORDS 19.1 db.customURL functionality
          Kiran Pawar

          Hi user4716747,

          user4716747 wrote:

           

          I'm getting this error when I'm using db.customURL functionality in ORDS 19.1 (ords-19.1.0.092.1545.zip):

          404 Not Found

          • 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

           

          I am not getting the above error when I'm using ORDS 18.4 (ords-18.4.0.354.1002.zip).

          I wonder if this is a known issue in ORDS 19.1 (ords-19.1.0.092.1545.zip).

          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]]

          How do you know that this issue is related to db.customURL? While configuring ORDS with database have you used db.customURL?

          db.customURL is the ORDS configuration parameter which is related to database configuration:

           

          db.customURL

          string

          Specifies the JDBC URL connection to connect to the database.

          jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP) (HOST=myhost)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ora111.example.com)))

          Pool specific

           

          Refer: https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/19.1/aelig/about-REST-configuration-files.html#GUID…

           

          The error 404 is about request URL (URL which you are entering in browser) which ORDS is not able to map to URI resource.

           

          Regards,

          Kiran

          • 2. Re: ORDS 19.1 db.customURL functionality
            user4716747

            I know it's related to db.customURL because the same config files (xxxxx.xml, xxxxx_al.xml, xxxxx_rt.xml, xxxxx_pu.xml) work fine in ORDS 18.4:

            <entry key="db.connectionType">customurl</entry>

            <entry key="db.customURL">jdbc:oracle:thin:@ldap://ldap-ldprd:5000/XXXXX,cn=OracleContext,dc=....,dc=com</entry>

             

            Furthermore, it works fine in ORDS 19.1 only when I switch to db.hostname, db.port, db.servicename:

            <entry key="db.hostname">yyyyy</entry>

            <entry key="db.port">dddd</entry>

            <entry key="db.servicename">XXXXX</entry>

             

            Thanks!

            • 3. Re: ORDS 19.1 db.customURL functionality
              Ajax_ords

              It could be that there not mapped correctly in 19.1. basically your config files and 19.1 war

              • 4. Re: ORDS 19.1 db.customURL functionality
                User531384-Oracle

                please add the following line in the defaults.xml and test the behavior after restating the ORDS

                 

                <entry key="jdbc.connectionFactory">default</entry>

                • 5. Re: ORDS 19.1 db.customURL functionality
                  Chris_Gooch

                  I had the same issue and adding the below resolved the issue:

                   

                  <entry key="jdbc.connectionFactory">default</entry>