11 Replies Latest reply on Jan 30, 2020 4:52 PM by thatJeffSmith-Oracle

    ORDS 19.4 with TOMCAT 9.0.30 problem

    tirone

      hi,

      i am working in the following environment and everything is ok.

      I mean that using the following URL http://localhost/apex I access the apex login page

       

      TomCat 9.0.19

      Windows server 2016,

      ORDS 19.4 used only for APEX 19.2 on

      Oracle Database 18c Standard Edition 2 Release 18.0.0.

      Version 18.3.0.0.0


      Now I have :

      - installed, on the same system (new folder), the new version of tomcat 9.0.30.

      - stopped ORDS and tomcat 9.0.19

      - copied the same apex.war and the same image folder i used in version 9.0.19 to the webapps folder of the of the new tomcat installation

      - restarted ords in the new tomcat

       

      but now using the same URL http://localhost/apex I get the following error

       

      The request could not be mapped to any database. Check that the request URL is valid and that the database mappings URL has been configured correctly..

       

      Stopping ords and the tomcat 9.0.30 service and restarting the tomcat 9.0.19 and ords service is all right again.

       

      what am I doing wrong or missing ?
      any help will be appreciated

      thank you

      saverio

       

      Catalina log_file;

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.30

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Dec 7 2019 16:42:04 UTC

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.30.0

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Windows Server 2016

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            10.0

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             C:\Program Files\Java\jre1.8.0_181

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_181-b13

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         C:\Program Files\Apache Software Foundation\Tomcat930

      08-Jan-2020 18:02:55.453 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         C:\Program Files\Apache Software Foundation\Tomcat930

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat930

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat930

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat930\temp

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat930\conf\logging.properties

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms128m

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx256m

      08-Jan-2020 18:02:55.484 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Apache Software Foundation\Tomcat930\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jre1.8.0_181\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;D:\app\oracle\base\oradba\product\18.0.3\dbhome_1\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\WindowsApps;.]

      08-Jan-2020 18:02:56.562 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]

      08-Jan-2020 18:02:56.750 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]

      08-Jan-2020 18:02:56.765 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [2,037] milliseconds

      08-Jan-2020 18:02:56.875 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]

      08-Jan-2020 18:02:56.875 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.30]

      08-Jan-2020 18:02:56.968 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\apex.war]

      08-Jan-2020 18:03:03.562 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

      08-Jan-2020 18:03:08.828 INFO [main] . No pools configured yet ?????????

      08-Jan-2020 18:03:08.906 INFO [main] . Oracle REST Data Services initialized

      Oracle REST Data Services version : 19.4.0.r3521226

      Oracle REST Data Services server info: Apache Tomcat/9.0.30

       

      08-Jan-2020 18:03:08.984 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\apex.war] has finished in [12,016] ms

      08-Jan-2020 18:03:09.000 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\docs]

      08-Jan-2020 18:03:09.031 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\docs] has finished in [31] ms

      08-Jan-2020 18:03:09.031 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\host-manager]

      08-Jan-2020 18:03:09.125 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\host-manager] has finished in [78] ms

      08-Jan-2020 18:03:09.125 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\i]

      08-Jan-2020 18:03:09.172 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\i] has finished in [47] ms

      08-Jan-2020 18:03:09.172 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\manager]

      08-Jan-2020 18:03:09.343 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\manager] has finished in [171] ms

      08-Jan-2020 18:03:09.343 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\ROOT]

      08-Jan-2020 18:03:09.390 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\Program Files\Apache Software Foundation\Tomcat930\webapps\ROOT] has finished in [47] ms

      08-Jan-2020 18:03:09.406 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-80"]

      08-Jan-2020 18:03:09.437 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]

      08-Jan-2020 18:03:09.437 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [12,683] milliseconds

       

      Added catalina log_file by tirone

        • 2. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
          tirone

          Thanks Pierre,

          yes, I have already validated ORDS: below you can see the log.

          The strange thing is that if I deploy the same apex.war with tomcat 9.0.19 everything is ok, if I do it with tomcat 9.0.30 I get the error that I reported.

          Both tomcats are installed on the same system, but, of course,  when i use tomcat 9.0.30 the tomcat 9.0.19 service is stopped.

           

          regards

          saverio

           

          ========================== VALIDATE LOG  ===========================

          [*** script: ords_alter_session_script.sql]

          Procedura PL/SQL completata correttamente.

          [*** script: ords_version.sql]

           

          Session modificato.

           

          Procedura PL/SQL completata correttamente.

          [*** script: ords_schema_mapping.sql]

          INFO: Configuring ORDS_PUBLIC_USER to map APEX Workspaces and ORDS schemas

           

          Session modificato.

           

          Configuring APEX and ORDS schemas for url mapping

          Made APEX_PUBLIC_USER proxiable from ORDS_PUBLIC_USER

          Made APEX_REST_PUBLIC_USER proxiable from ORDS_PUBLIC_USER

          APEX_POOL_CONFIG Synonym exists

          Created ORDS_METADATA.APEX_WWV_FLOW_POOL_CONFIG as view over

          APEX_190200.APEX_POOL_CONFIG

           

          Procedura PL/SQL completata correttamente.

          Procedura PL/SQL completata correttamente.

           

          Grant riuscito/a.

           

          Procedura PL/SQL completata correttamente.

          INFO: Completed configuring ORDS_PUBLIC_USER to map APEX Workspaces and ORDS Schemas

           

          Session modificato.

           

          [*** script: ords_repair_proxy_connect.sql]

          INFO: Checking ords enabled schemas and its proxy user

           

          Session modificato.

           

          Procedura PL/SQL completata correttamente.

          [*** script: ords_migrate_grant_priv.sql]

           

          Session modificato.

           

          INFO: Verify if Application Express exists to setup the migration privileges for

          ORDS.

          INFO: Completed setting up the APEX REST migration privileges for ORDS.

           

          Procedura PL/SQL completata correttamente.

          [*** script: ords_validate_objects.sql]

           

          Session modificato.

           

          INFO: 09:40:11 Validating objects for Oracle REST Data Services.

          VALIDATION: 09:40:11 Starting validation for schema: ORDS_METADATA

          VALIDATION: 09:40:11 Validating objects

          VALIDATION: 09:40:14 Validating ORDS Public Synonyms

          VALIDATION: 09:40:16 Total objects: 266, invalid objects: 0

          VALIDATION: 09:40:16     72  INDEX

          VALIDATION: 09:40:16      3  LOB

          VALIDATION: 09:40:16     12  PACKAGE

          VALIDATION: 09:40:16     12  PACKAGE BODY

          VALIDATION: 09:40:16      1  PROCEDURE

          VALIDATION: 09:40:16     44  PUBLIC SYNONYM

          VALIDATION: 09:40:16      1  SEQUENCE

          VALIDATION: 09:40:16     14  SYNONYM

          VALIDATION: 09:40:16     27  TABLE

          VALIDATION: 09:40:16     27  TRIGGER

          VALIDATION: 09:40:16     20  TYPE

          VALIDATION: 09:40:16      6  TYPE BODY

          VALIDATION: 09:40:16     27  VIEW

          VALIDATION: 09:40:16 Validation completed.

          INFO: 09:40:16 Completed validating objects for Oracle REST Data Services.

           

          Procedura PL/SQL completata correttamente.

           

          Session modificato.

           

          Commit completato.

          [*** script: ords_alter_session_script.sql]

          Procedura PL/SQL completata correttamente.

          [*** script: ords_version.sql]

           

          Session modificato.

           

          Procedura PL/SQL completata correttamente.

          • 3. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
            Pierre Yotti

            validate and restart tomcat 9.0.30.

             

            In which Port ist tomcat 9.0.30 accessible?

             

            Create a folder is not enough.

             

            You need to install tomcat 9.0.30 on Windows.

             

            In which port is running  tomcat 9.0.30?

             

             

            Can you access tomcat 9.0.30 like so?  http://localhost:port

            • 4. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
              Franck N

              Hi,

              try the following:

              • Create a new DB Connexion

              Java -jar ords.war setup

               

              • With the new database connection in place, you need to map a URL to point to it.
              java -jar ords.war map-url 

              Regards,

              Franck

              • 5. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                tirone

                Thanks Pierre, but all the steps you suggest I have already done.

                - stopped the tomcat 9.0.19 service (port 80)

                - installed, on the same system (new folder), the new version of tomcat 9.0.30. (port 80)

                - copied the same apex.war (validated) and the same image folder i used in version 9.0.19 to the webapps folder of the of the new tomcat installation

                - restarted  tomcat 9.0.30 service

                - access tomcat 9.0.30 using http://localhost  --> OK

                - checked if /apex  web application is running --> OK

                - tried  http://localhost/apex --> K.O.     got the error shown in my initial post

                 

                But ....

                Stopping ords and the tomcat 9.0.30 service and restarting the tomcat 9.0.19 and ords service is all right again !!!.

                 

                regards

                saverio

                • 6. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                  tirone

                  Thanks Franck,

                  I have already tried creating a new DB connection and mapped the URL to point to it

                  I ran the following commands:

                   

                  java -jar .\apex.war setup --database apex

                  .....

                  .....

                  java -jar .\apex.war map-url --type base-path  /apex apex

                   

                  but unfortunately I still have the same error when I deploy using tomcat 9.0.30  while everything is ok when i use tomcat 9.0.19 (on same system and port) :

                  The request could not be mapped to any database. Check that the request URL is valid and that the database mappings URL has been configured correctly..

                   

                  regards

                  saverio

                  • 7. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                    Franck N

                    hi,

                    did you specify the configuration directory correctly?

                    run this:

                    java -jar ords.war configdir

                    If the configuration folder has not yet been configured, the message: The config.dir setting is not set, is displayed. If it has been configured, the current value of the setting is displayed.

                    docs..

                     

                    regards,

                    Franck

                    • 8. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                      tirone

                      hi Franck,

                      as you can see below I ran the command on both apex.war files present in the two webapps directories of the two tomcats and I get the same config directory

                      PS C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps> java -jar .\apex.war configdir

                      2020-01-09T17:02:19.622Z INFO   The config.dir value is D:\app\oracle\base\oradba\ords19_4\config

                       

                       

                      PS C:\Program Files\Apache Software Foundation\Tomcat930\webapps> java -jar .\apex.war configdir

                      2020-01-09T17:04:56.481Z INFO   The config.dir value is D:\app\oracle\base\oradba\ords19_4\config

                       

                      however the ORDS configuration should be fine because if I use tomcat 9.0.19 everything is ok.

                      the problem is that if I deploy the same apex.war with the tomcat 9.0.30 I have the error

                       

                      thank you so much for your help

                      saverio

                      • 9. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                        tirone

                        An update on my post ...

                         

                        • The  ORDS 19.4 installation is OK if deployed with tomcat 9.0.19.
                        • The  same ORDS 19.4 installation is KO if deployed with tomcat 9.0.30
                        • The same ORDS 19.4 installation is KO if startd in standalone mode --> I get the same message "No pools configured yet" that I found in the  catalaina log file

                         

                        It seems like a problem related to the creation of the pool, but I don't understand why with tomcat 9.0.19 everything is ok.
                        And also the validation of ORDS is ok.

                         

                        When I start ORDS using

                        java -jar apex.war standalone I get :

                        Using existing ORDS configuration files located at D:\app\oracle\base\oradba\ords19_4\config\apex

                         

                        Verify ORDS schema in Database Configuration apex using connection url jdbc:oracle:thin:@//161.27.170.52:1521/ECMDB

                         

                        Retrieving information.

                        2020-01-13T11:26:49.023Z INFO   Oracle REST Data Services schema version 19.4.0.r3521226 is installed.

                        2020-01-13 12:26:49.164:INFO::main: Logging initialized @9606ms to org.eclipse.jetty.util.log.StdErrLog

                        2020-01-13 12:26:49.367:INFO:oeju.TypeUtil:main: JVM Runtime does not support Modules

                        2020-01-13T11:26:49.570Z INFO   HTTP and HTTP/2 cleartext listening on host: localhost port: 8080

                        2020-01-13T11:26:49.679Z INFO   Disabling document root because the specified folder does not exist: D:\app\oracle\base\oradba\o

                        rds19_4\config\apex\standalone\doc_root

                        2020-01-13 12:26:50.695:INFO:oejs.Server:main: jetty-9.4.24.v20191120; built: 2019-11-22T11:09:44.612Z; git: 8b8c80157294e38f81e

                        f8ea2358a0c49bf5db918; jvm 1.8.0_181-b13

                        2020-01-13 12:26:50.773:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0

                        2020-01-13 12:26:50.773:INFO:oejs.session:main: No SessionScavenger set, using defaults

                        2020-01-13 12:26:50.789:INFO:oejs.session:main: node0 Scavenging every 600000ms

                        2020-01-13T11:26:52.101Z INFO   No pools configured yet

                        2020-01-13T11:26:52.179Z INFO   Oracle REST Data Services initialized

                        Oracle REST Data Services version : 19.4.0.r3521226

                        Oracle REST Data Services server info: jetty/9.4.24.v20191120

                         

                        2020-01-13 12:26:53.710:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@436813f3{/ords,null,AVAILABLE}

                        2020-01-13 12:26:53.710:INFO:oejsh.ContextHandler:main: Started o.e.j.s.h.ContextHandler@4562e04d{/i,null,AVAILABLE}

                        2020-01-13 12:26:53.789:INFO:oejs.AbstractConnector:main: Started ServerConnector@7e057f43{HTTP/1.1,[http/1.1, h2c]}{0.0.0.0:808

                        0}

                        2020-01-13 12:26:53.789:INFO:oejs.Server:main: Started @14245ms

                         

                        New update :

                        now after installing the new  java version (1.8.0_231-b11) starting apex.war in standalone mode is OK. (pools are configurated)

                        ......

                        Configuration properties for: |apex|| 

                        ....

                        Configuration properties for: |apex|al|

                        ....

                        Configuration properties for: |apex|pu|

                        ....

                        Configuration properties for: |apex|rt|

                         

                        But if i deploy with tomcat 9.0.30  i still get the same error (in the catalina log i have "No pools configured yet")

                        regards

                        saverio

                        • 10. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                          tirone

                          Resolved
                          It was a permission issue on the ORDS config directory.
                          I didn't understand why this directory was accessed correctly by Tomcat 9.0.19 and not by Tomcat 9.0.30 both installed on the same server using the same windows user (admin)

                           

                           

                          • 11. Re: ORDS 19.4 with TOMCAT 9.0.30 problem
                            thatJeffSmith-Oracle

                            thanks for sharing the mystery solved details!