4 Replies Latest reply on Aug 22, 2013 2:10 PM by Cristian Baser

    SEVERE: The pool named: apex is not correctly configured, error: IO Error:

    user480768
    user480768 Feb 16, 2013 12:16 PM
      My APEX Listener 2.0 gives me SEVERE: The pool named: apex is not correctly configured, error: IO Error: The Network Adapter could not establish the connection when I visit http://apexserver:8080/apex/apex_admin, the local browser gives me 404 - Not Found error. Any help will be appreciated.

      Kevin




      Feb 16, 2013 7:03:01 AM com.sun.grizzly.Controller logVersion
      INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 2/16/13 7:03 AM
      Feb 16, 2013 7:03:01 AM oracle.dbtools.standalone.Standalone execute
      INFO: http://localhost:8080/apex started.
      Feb 16, 2013 7:03:36 AM oracle.dbtools.rt.web.HttpEndpointBase modApex
      SEVERE: The pool named: apex is not correctly configured, error: IO Error: The Network Adapter could not establish the connection
      oracle.dbtools.common.jdbc.ConnectionPoolException: The pool named: apex is not correctly configured, error: IO Error: The Network Adapter could not establish the connect
      at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(ConnectionPoolException.java:65)
      at oracle.dbtools.common.config.db.DatabaseConfig.badConfiguration(DatabaseConfig.java:153)
      at oracle.dbtools.common.config.db.DatabaseConfig.createPool(DatabaseConfig.java:174)
      at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:70)
      at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.java:69)
      at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:331)
      at oracle.dbtools.apex.Procedure.getProcedure(Procedure.java:167)
      at oracle.dbtools.apex.OWA.validateProcedure(OWA.java:392)
      at oracle.dbtools.apex.security.Security.isValidRequest(Security.java:225)
      at oracle.dbtools.apex.ModApex.validateRequest(ModApex.java:277)
      at oracle.dbtools.apex.ModApex.doGet(ModApex.java:95)
      at oracle.dbtools.apex.ModApex.service(ModApex.java:316)
      at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:260)
      at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:110)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.doFilter(ServletAdapter.java:1059)
      at com.sun.grizzly.http.servlet.ServletAdapter$FilterChainImpl.invokeFilterChain(ServletAdapter.java:999)
      at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:434)
      at oracle.dbtools.standalone.SecureServletAdapter.doService(SecureServletAdapter.java:65)
      at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:379)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.service(GrizzlyAdapterChain.java:196)
      at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
      at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
      at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
      at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
      at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
      at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
      at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
      at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
      at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
      at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
      at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
      at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
      at java.lang.Thread.run(Unknown Source)
      • 14171 Views
      • Tags:
        • 1. Re: SEVERE: The pool named: apex is not correctly configured, error: IO Error:
          user480768
          user480768 Feb 16, 2013 12:29 PM (in response to user480768)
          When I start Apex Listener, I got Default Database connection not configured properly, See following message when I launch java -jar apex.war to start listener.




          D:\app\administrator\apex_listener.2.0.0.354.17.05>java -jar apex.war
          Feb 16, 2013 7:22:17 AM oracle.dbtools.standalone.Standalone execute
          INFO: NOTE:

          Standalone mode is designed for use in development and test environments. It is not supported for use in production environments.

          Feb 16, 2013 7:22:17 AM oracle.dbtools.standalone.Standalone execute
          INFO: Starting standalone Web Container in: D:\app\administrator\apex_listener.2.0.0.354.17.05\apex
          Feb 16, 2013 7:22:17 AM oracle.dbtools.standalone.Deployer deploy
          INFO: Will deploy application path = D:\app\administrator\apex_listener.2.0.0.354.17.05\apex\apex\WEB-INF\web.xml
          Feb 16, 2013 7:22:17 AM oracle.dbtools.standalone.Deployer deploy
          INFO: Deployed application path = D:\app\administrator\apex_listener.2.0.0.354.17.05\apex\apex\WEB-INF\web.xml
          Feb 16, 2013 7:22:17 AM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
          INFO: Using configuration folder: D:\app\administrator\apex_listener.2.0.0.354.17.05\apex
          Default Database connection not configured properly
          Feb 16, 2013 7:22:21 AM oracle.dbtools.rt.web.SCListener contextInitialized
          INFO: Oracle Application Express Listener initialized
          Application Express Listener version : 2.0.0.354.17.06
          Application Express Listener server info: Grizzly/1.9.49

          Feb 16, 2013 7:22:21 AM com.sun.grizzly.Controller logVersion
          INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 2/16/13 7:22 AM
          Feb 16, 2013 7:22:21 AM oracle.dbtools.standalone.Standalone execute
          INFO: http://localhost:8080/apex started.
          • 2. Re: SEVERE: The pool named: apex is not correctly configured, error: IO Error:
            Udo
            Udo Feb 16, 2013 12:48 PM (in response to user480768)
            Hello Kevin,

            the error message seems pretty clear: You've not configured your database connection for APEX Listener properly.
            What did you do so far to configure your APEX Listener?

            -Udo
            • 3. Re: SEVERE: The pool named: apex is not correctly configured, error: IO Error:
              user480768
              user480768 Feb 18, 2013 12:11 PM (in response to Udo)
              I have Oracle 11g R2 RAC One Node as database server, there are two Windows 2008 R2 servers running in the cluster. Here are the default.xml file

              <?xml version="1.0" encoding="UTF-8" standalone="no"?>
              <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
              <properties>
              <comment>Saved on Sat Feb 16 06:57:37 EST 2013</comment>
              <entry key="db.servicename">******</entry>
              <entry key="debug.printDebugToScreen">false</entry>
              <entry key="security.disableDefaultExclusionList">false</entry>
              <entry key="db.password">******</entry>
              <entry key="cache.maxEntries">500</entry>
              <entry key="error.maxEntries">50</entry>
              <entry key="security.maxEntries">2000</entry>
              <entry key="cache.directory">/tmp/apex/cache</entry>
              <entry key="jdbc.DriverType">thin</entry>
              <entry key="log.maxEntries">50</entry>
              <entry key="db.hostname">localhost</entry>
              <entry key="jdbc.MaxConnectionReuseCount">1000</entry>
              <entry key="log.logging">false</entry>
              <entry key="jdbc.InitialLimit">3</entry>
              <entry key="jdbc.MaxLimit">10</entry>
              <entry key="cache.monitorInterval">60</entry>
              <entry key="cache.expiration">7</entry>
              <entry key="jdbc.statementTimeout">900</entry>
              <entry key="jdbc.MaxStatementsLimit">10</entry>
              <entry key="misc.defaultPage">apex</entry>
              <entry key="misc.compress"/>
              <entry key="jdbc.MinLimit">1</entry>
              <entry key="cache.type">lru</entry>
              <entry key="cache.caching">false</entry>
              <entry key="db.port">1521</entry>
              <entry key="error.keepErrorMessages">true</entry>
              <entry key="cache.procedureNameList"/>
              <entry key="cache.duration">days</entry>
              <entry key="jdbc.InactivityTimeout">1800</entry>
              <entry key="debug.debugger">false</entry>
              </properties>


              <entry key="db.hostname">localhost</entry>, it connects to local which is the node running RAC instance. Thanks for your comments.

              Kevin
              • 4. Re: SEVERE: The pool named: apex is not correctly configured, error: IO Error:
                Cristian Baser
                Cristian Baser Aug 22, 2013 2:10 PM (in response to Udo)

                To change configuration edit

                /var/apex_listener/config_lsnr/apex/defaults.xml

                 

                otherwise, delete directory config_lsnr and re-run configuration...

                 

                Regards,