Apex Listener config recommendations

Our DBA is installing Apex Listener 1.1.2.131.15.23 for the first time, and had a question regarding some setup. Right now it's just a stand alone copy. In the JDBC Settings, what are your recommendations for the following settings?
Initial Pool Size: 3
Maximum Statements: 10
Minimum Connections: 1
Inactivity Timeout: 1800 seconds
Maximum Connections: 10
Abandoned Connection Timeout: 900 seconds
If there is some recommended reading on how to determine the best way to set this up, that would be great.

Hello Rick,
it's hard to give you actual values. These settings concern, more or less, your load expectations. The numbers you need are
- average number of concurrent sessions (work load)
- maximum number of concurrent sessions (peek load)
Some settings might as well depend on your applications.
Recommended reading would be the Table A-1 of the Installation and Developers Guide, where the parameters you picked are described among other configuration parameters.
Just some thoughts on connection handling:
The APEX Listener uses a pool of connections to the database that is shared among all users. Usually it would be a waste of resources to have a dedicated connection for each application session, as there are usually times when there's no user activity, e.g. when a user is reading a report. So you want to make the pool size as small as possible without negative impact on your user experience. To achieve this, you may initialize your pool to be able to serve your average work load and allow it to grow to the expected peek. You may want to set the minimum number of connections below that value, so resource consumption is reduced in times of low charge.
The timeouts concern the reduction of the pool size due to reduced load (inactivity timeout - a connection isn't needed any more) or failures or unexpected long database reaction times (abandoned connection).
Statements caching can reduce database load and response times, but increases resource consumption of the Listener and may result in inacurate results if cached values are outdated.
If you have more practical questions on that topic, don't hesitate to ask.
-Udo

Similar Messages

  • Can a single Weblogic server host more than one Apex Listener?

    Hi All:
    Is it possible to deploy more than one APEX listener on a Weblogic server to service multiple APEX installations on different Database hosts?
    I suspect it is just a matter of port configuration and deployment naming but has anyone experience with this?
    Regards,
    David

    Hi David,
    it is possible to have multiple instances of the APEX Listener deployed on the same JEE container. I didn't actually do this with WLS, but I don't know any reason why this should be different on WLS than it would be on other JEE containers.
    You should start by preparing the apex.war to have the parameter config.dir set in the web.xml . We chose to let it point to a base directory for all config files having one subdirectory for each deployed instance, so we have to do this only once with every new release that comes in. By the way, this is the first location of the sequence to be checked by the APEX Listener upon startup.
    Then you can deploy this war file multiple times giving each instance a different application name/context root. We chose +<apex_dbname>+ as pattern for this, but that's up to you.
    Note that you may have to provide the static files ("images") for APEX multiple times as well if you don't have the same APEX version on each instance or if you use different custom files that shall not be the present on each instance or in different versions for at least some instances.
    In that case, you'll have to configure your WLS to provide multiple "images-applications" as well. We chose to have one for each instance and use +</i_<dbname>/+ as pattern here. If you used the default image prefix +/i/+ so far, you can reset it using the corresponding script provided in the APEX installation package. I'd recommend to use the script version of the package that corresponds to the APEX version of the instance you want to configure.
    That might sound complicated, but actually it's not. It's just a few things to keep in mind before starting and once you've set it up, it's really easy to handle.
    -Udo

  • APEX LISTENER Install troubleshooting

    Hi, I need help.. :-)
    Default Database connection not configured properly
    What I have done:
         ALTER USER APEX_LISTENER ACCOUNT UNLOCK;
         ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK;
         ALTER USER APEX_REST_PUBLIC_USER ACCOUNT UNLOCK;
         connect APEX_LISTENER/mypasswd1
         connect APEX_PUBLIC_USER/mypasswd2
         connect APEX_REST_PUBLIC_USER/mypasswd1
    Check default.xml
    password: replaced encrypted one with clear text one for APEX_PUBLIC_USER to ensure it is correct
    even tried APEX_LISTENER password just incase
    Is there a simple JDBC test to see if it connects? it is APEX_PUBLIC_USER who is connecting isn't it?
    ======================================================================
    java -jar apex.war
    Feb 22, 2013 12:44:40 PM 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 22, 2013 12:44:40 PM oracle.dbtools.standalone.Standalone execute
    INFO: Starting standalone Web Container in: /data/oracle/orawd/product/11.2.0/dbhome_1/apex_listener/apex
    Feb 22, 2013 12:44:41 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Will deploy application path = /data/oracle/orawd/product/11.2.0/dbhome_1/apex_listener/apex/apex/WEB-INF/web.xml
    Feb 22, 2013 12:44:41 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Deployed application path = /data/oracle/orawd/product/11.2.0/dbhome_1/apex_listener/apex/apex/WEB-INF/web.xml
    Feb 22, 2013 12:44:41 PM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
    INFO: Using configuration folder: /data/oracle/orawd/product/11.2.0/dbhome_1/apex_listener/apex
    Default Database connection not configured properly
    Feb 22, 2013 12:44:42 PM 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 22, 2013 12:44:42 PM com.sun.grizzly.Controller logVersion
    INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 2/22/13 12:44 PM
    Feb 22, 2013 12:44:42 PM oracle.dbtools.standalone.Standalone execute
    INFO: http://localhost:8888/apex started.

    That could be a problem.
    I was answering the question:
    BillC wrote:
    Is there a simple JDBC test to see if it connects? it is APEX_PUBLIC_USER who is connecting isn't it?Yes - APEX_PUBLIC_USER is the connecting user.
    You can use SQLPLUS to make sure you have the correct password.
    After that, it is the SERVER, PORT, SID/SERVICE in the APEX listener you need to confirm.
    You can TNSPING to confirm you have the correct selections for those.
    You can always re-run the java -jar apex.war setup command to all of the basic settings.
    The reason I mention that is because if you modify the settings manually - we need to ask "which file?" because there is the default and the database specific one too.
    Try making a request to the service in standalone mode and you should get a terminal output (the window stays open) with a more detailed error. I would guess there will be an ORA-12514, TNS listener does not currently know of service requested in descriptor or something similar that will give you the "debug" information you are looking for.
    Regards,
    --Tim St.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • APEX Listener with APEX 3.0 on 11gR2

    Yes, I am crazy.
    We have many many APEX applications in APEX 3.0 running on a 10.2.0.4 database that needs desperately to be upgraded. As a test, I've set up a clean 11gR2 database and copied the production APEX database into it via datapump. I set up APEX Listener, as I don't have any OAS sitting around and the EPG doesn't seem to be supported for APEX 3.0... the Listener doesn't say one way or the other.
    When trying to log in, I get the login page, but it tries to reference files such as apex_get_3_1.js while I only have files such as htmldb_get.js in my images directory in production. I noticed it is looking for what appears to be 3.1 files instead of 3.0 files... which concerns me.
    The APEX listener appears to be more than just a Java PL/SQL gateway.
    Is there a minimum version of APEX the APEX Listener supports?
    Interested in pointers!
    Rob

    Hi Rob,
    Yes, I am crazy.Why would that be? ;)
    We have many many APEX applications in APEX 3.0 running on a 10.2.0.4 database that needs desperately to be upgraded. As a test, I've set up a clean 11gR2 database and copied the production APEX database into it via datapump. I set up APEX Listener, as I don't have any OAS sitting around and the EPG doesn't seem to be supported for APEX 3.0... the Listener doesn't say one way or the other.APEX 3.0 is supprted by EPG. See the [url http://docs.oracle.com/cd/B32472_01/doc/install.300/b32468/post_inst.htm#CHDBEJDA]APEX 3.0 Installation Guide for details.
    APEX Listener is capable of hosting APEX 3.0 as well, though APEX 3.0 wasn't supported anymore when APEX Listener was initially released. The current APEX release at that time was 4.0, so this would be the first version to be known as really stable, whereas you won't get any support for older releases anymore. From personal experience I know that there are now issues with APEX 3.1 and APEX Listener, so it'll probably also work with 3.0.
    Concerning your database release, the minimum for APEX Listener is 10.2.0.3, so you're definetly safe on that part, though I'd recommend to upgrade as regular support for 10.2 databases ended.
    When trying to log in, I get the login page, but it tries to reference files such as apex_get_3_1.js while I only have files such as htmldb_get.js in my images directory in production. I noticed it is looking for what appears to be 3.1 files instead of 3.0 files... which concerns me.This indicates that your APEX would actually be a 3.1 and you should update you images directory.
    The APEX listener appears to be more than just a Java PL/SQL gateway.It is, but this has nothing to do with your 3.1 JS files, if this is why you stated this.
    Is there a minimum version of APEX the APEX Listener supports?As mentioned above, 4.0 would be a safe approach, but 3.1 will definetly work, 3.0 probably will as well. I'd recommend you find out which APEX version is actually installed on your database before you consider any upgrade operations. Run the following query as privileged user:
    SELECT comp_name, version, status
      FROM dba_registry
    WHERE comp_id = 'APEX';-Udo

  • APEX listener - empty page ??

    Hi,
    I have installed tomcat / APEX listener on Oracle Enterprise Linux 5 (with 11gR2 database)
    The configuration seems to be done ... but the page: http://oel52server:8080/apex/apex give me an empty page ?
    do you know what's wrong ?
    Cyryl

    Thanks for the answers.
    I have a similar problem-- but I believe it may not be because of JDK ver. (becaue I already use ver. 6.0).
    Although I am able to see the Apex login page. http://localhost:8888/apex/, but no images are displayed. Moreover it asks for Workspace, Username, Password which I am unaware of (it did not ask for any such information while installing apex). It looks like none of the buttons/links are active. Did I do anything wrong while installing apex?
    This is how I installed Apex.
    1. Downloaded and installed tomcat application server and Apex Listener as per the instructions given in the link:
    http://www.oracle.com/technology/products/database/application_express/html/apex_listener_install_web.html
    (section B. Installing with Apache Tomcat in the installation )
    2. The images are copied to the following location (as given in the instruction):
    C:\apache-tomcat-6.0.24\webapps\ROOT\images
    3. Started both oracle db server and tomcat app. server
    4. Opened the page http://localhost:8888/apex/Config
    at this point I get the login page with no images and inactive links/buttons.
    Appreciate any help.
    Thank you,
    Pravy

  • APEX LIstener administration via SQLDeveloper 3.2.2 error

    Hi,
    I configured the APEX Listener 2 on my server and everything works fine.
    I also configured the Restful webservices that also works fine in APEX.
    Now , I would like to be able to configure the APEX Listener via SQLDeveloper 3.2.2
    I changed the defaults.xml file to allow a non HTTPS connection and configured the adminlistener password.
    When I try to connect to the APEX Listener via SQLDeveloper to retrieve the configuration, I get the following error :
    Error occured retrieving Administration Settings from Listener.
    Unexpected Content-Type:application/json; charset=UTF-8
    APEX Listener is installed on Windows (french version).
    Thanks
    Francis.

    Hi Francis, I'm getting the same error.
    (I do note however that SQLDev does make the connection - and even though I get the UTF8 error, I can upload/download config files. This would appear to be a warning/info message. But still annoying.)
    I am using CentOS 5.8 Linux, Glassfish 3.1.2, SQLDev 3.2.20.09, ApEx 4.2. DB is 11.2.0.3, AL32UTF8. So this problem is not unique to Windows or French.
    Wayne
    Edited by: cawli2 on Nov 6, 2012 10:54 AM
    Edited by: cawli2 on Nov 6, 2012 12:36 PM

  • APEX Listener EA2 Standalone CLOB error

    I'm testing the APEX Listener EA2 release in Standalone mode on CentOS against Oracle XE.
    My RESTful service calls use the Media Resource type to return a CLOB that I format myself inside a function:
    select 'application/json', my_function_that_returns_json_in_a_clob from dual
    In the EA2 release, this is generating an error if the function returns more than 4000 bytes (works with 4000, fails with 4001). It is as though the function is getting cast as a varchar2 somewhere. I verified that the function will correctly return a large result to other sources (dbms_output, for instance).
    The APEX Listener Log reports the error as:
    oracle.dbtools.rt.web.HttpEndpointBase restfulServices
    SEVERE: ORA-22922: nonexistent LOB value
    Here's a Test Case:
    create or replace function test_size(p_cnt in integer) return clob
    is
    l_clob clob;
    begin
    for i in 1..p_cnt loop
    l_clob:=l_clob||'a';
    end loop;
    return l_clob;
    end;
    Then create a RESTful service call:
    Method: "GET"
    Source Type: "Media Resource"
    Source: select 'application/json', test_size(4001) from dual
    Thanks,
    Tim

    Thanks for your thorough reply!
    Unfortunately, your workaround doesn't fix the problem with EA2. It encounters the 4000 character limit as well.
    I understand your advice regarding using the QUERY type. I chose the Media Resource strategy for two main reasons:
    1. These services calls are for our mobile developers. Because they use some predefined frameworks for managing data that comes to the mobile app, they wanted the json to distinguish between data sets (rather than every data set being called "items"). I am able to format the json in such a way that it doesn't confuse their code. Is there another way to customize the format of the default json created by the QUERY type?
    2. I need to conduct some other business as part of the call. For instance, the service passes in a user's credentials which I use to authenticate and then retrieve the appropriate results based on who they are. Currently, I have stored procedures that authenticate APEX users or LDAP users.
    Perhaps old habits die hard, but I find that if I just do all of this myself in a stored function, I have all of the control I need. If you have other recommended strategies, I'm all ears.
    Thanks!
    _Tim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Apex Listener return blank pages with no configuration errors!

    - I set up an Apex Listener "Version:1.1.3.243.11.40" at "10.0.114.11" in standalone mode.
    - I configured Apex Listener via http://10.0.114.11:8585/apex/listenerConfigure and return with no errors.
    - I get http://10.0.114.11:8585/apex/listenerStatus, it returned this:
    Current Time:     Tue Dec 13 17:06:32 ICT 2011
    Server Uptime:     0 Days 01:10:14.101
    Total Accesses:     38.0
    Total Traffic:     161.34K
    Total Errors:     0
    Total File Downloads:     0
    Total Processing Time:     0 Days 00:00:09.354
    Processing Time in milliseconds:     Minimum: 20 Average: 246 Median: 64 Maximum: 3062
    Database Time in milliseconds:     Minimum: 14 Average: 61 Median: 50 Maximum: 204
    Active Requests:     0
    Connections in the pool apex:
    Active: 0 Available: 1
    But when I go to "http://10.0.114.11:8585/apex" or "http://10.0.114.11:8585/apex/apex_admin", I got blank pages.
    The page displays "Application Express Login" or "Application Express Administration Services" in the tab at the top of IE, but nothing else. Anyone have any ideas what could be happening here ?
    thanks so much,

    Hi Udo!
    I run apex_listener with this below command and the output is that:
    java -Dapex.home=/tmp/apex -Dapex.images=/tmp/apex/apex/images -Dapex.port=8585 -Dapex.erase -jar /source_install/apex_listener.1.1.3.243.11.40/apex.war
    INFO: Starting: /source_install/apex_listener.1.1.3.243.11.40/apex.war
    See: 'java -jar apex.war --help' for full range of configuration options
    INFO: Extracting to: /tmp/apex
    INFO: Using classpath: file:/tmp/apex/apex/____embedded/start.jar:file:/tmp/apex/apex/WEB-INF/lib/poi-3.6-20091214.jar:file:/tmp/apex/apex/WEB-INF/lib/commons-fileupload-1.2.1.jar:file:/tmp/apex/apex/WEB-INF/lib/je-4.0.103.jar:file:/tmp/apex/apex/WEB-INF/lib/apex.jar:file:/tmp/apex/apex/WEB-INF/lib/ojmisc.jar:file:/tmp/apex/apex/WEB-INF/lib/ucp.jar:file:/tmp/apex/apex/WEB-INF/lib/xdb-11.2.0.jar:file:/tmp/apex/apex/WEB-INF/lib/xmlparserv2-11.2.0.jar:file:/tmp/apex/apex/WEB-INF/lib/ojdbc6.jar:
    INFO: Starting Embedded Web Container in: /tmp/apex
    Dec 13, 2011 6:40:22 PM ____bootstrap.Deployer deploy
    INFO: Will deploy application path=/tmp/apex/apex/WEB-INF/web.xml
    Dec 13, 2011 6:40:22 PM ____bootstrap.Deployer deploy
    INFO: deployed application path=/tmp/apex/apex/WEB-INF/web.xml
    Using config file: /tmp/apex/apex-config.xml
    -- listing properties --
    PropertyCheckInterval=60
    ValidateConnection=true
    MinLimit=1
    MaxLimit=10
    InitialLimit=3
    AbandonedConnectionTimeout=900
    MaxStatementsLimit=10
    InactivityTimeout=1800
    MaxConnectionReuseCount=1000
    APEX Listener version : 1.1.3.243.11.40
    APEX Listener server info: Grizzly/1.9.18-o
    Dec 13, 2011 6:40:23 PM com.sun.grizzly.Controller logVersion
    INFO: Starting Grizzly Framework 1.9.18-o - Tue Dec 13 18:40:23 ICT 2011
    INFO: http://localhost:8585/apex started.
    Using JDBC driver: Oracle JDBC driver version: 11.2.0.2.0
    I don't know how to "could you please check if you configured the directory for the static contents ("images") correctly"
    because the Installation Guide of Oracle about Install Apex in standalone mode do not tell me to configure images any more. I just run apex listener with above command "java -Dapex.home=/tmp/apex -Dapex.images=/tmp/apex/apex/images -Dapex.port=8585 -Dapex.erase -jar /source_install/apex_listener.1.1.3.243.11.40/apex.war".
    Thank you for your reply,Udo!

  • Apex Listener in standalone mode, how to set/reset db connection.

    Sometime ago I installed Apex Listener for testing, then I removed it.
    Now I downloaded last version, installed it in standalone mode and try to set the DB connection.
    However when I try to edit in listenerAdmin page the db connection parameters I can't : they are greyed and report the connection informations I gave in my first test installation.
    How can I change them ?
    How can I avoid all fields in listenerAdmin greyed ?
    Tks
    Tullio

    Hello Tullio,
    you can run /listenerConfigure/ only as long as there is no configuration available. The database parameters can only be setup when the APEX Listener is not connected due to the state of its connection pool. Once it is established, you can only configure it offline by editing the apex-config.xml . That's why the parameters are greyed out in /listenerAdmin/.
    You probably only removed the war file of your test installation, but not the apex.home including the apex-config.xml that is stored in there. So your new installation found the old home and reused the connection.
    You could either edit the apex-config.xml or delete the apex.home and rerun /listenerConfigure/
    If you run on a windows system, you'll find the apex.home in your users TEMP, usually located in the temp folder underneath the local settings of your user profile. The directory to locate is now called "apex".
    -Udo

  • Apex listener images deployement

    Hi
    I installed the APEX listener recently. I have a question. Can I deploy the images in a different way other than jar them and then deploy to WLS. I have a lot of custom images/javascripts reside under the /i/ virtual path (e.g. /i/extjs). The images and javascripts change frequently. I guess that every time this happens I have to create a new i.war and redeploy which is not so convenient. Is there any other way to do that (e.g. copy them directly to a directory as I was doing with OHS/modplsql)
    Thanx
    George

    Hi George,
    you could do this by locating the directory where the WLS has unpacked the deployment to. But the more I think about this, the more I think you shouldn't do that, because staging etc. makes this very complex again.
    Instead of deploying the images as war file, you could add a virutal directory mapping, which is far easier.
    It should be possible to do that in the weblogic.xml of the apex.war (unpack the war, edit the file, repack the war, similar to what you'll do if you edit the web.xml, e.g. to change to config.dir parameter). See the [url http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/weblogic_xml.html#1039396]corresponding part of the WLS documentation for details on that parmaeter. The result could be a weblogic.xml as follows
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
    <container-descriptor>
      <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    <virtual-directory-mapping>
      <local-path>/opt/oracle/apex/images</local-path>
      <url-pattern>/i/*</url-pattern>
    </virtual-directory-mapping>
    </weblogic-web-app>if your images are stored in */opt/oracle/apex/images* .
    Not that this can cause node specific dependencies if you have a clustered WLS, and that you'll have to undeploy the i-application before you can redeploy the apex.war.
    -Udo

  • Apex listener / Weblogic server currently unavailable

    I installed the latest apex listener with weblogic server. Worked fine til I rebooted. The weblogic server is running and the weblogic console shows that apex is running, but when I go the URL I get "Requested url http://haora01:7001/apex/apex_admin is currently unavailable". Same URL worked fine before the reboot. I was using the EPG gateway and wanted to try the apex listener instead. I can't find any logs that help. Anybody have any suggestions?

    RFancher wrote:
    I installed the latest apex listener with weblogic server. Worked fine til I rebooted. The weblogic server is running and the weblogic console shows that apex is running, but when I go the URL I get "Requested url http://haora01:7001/apex/apex_admin is currently unavailable". Same URL worked fine before the reboot. I was using the EPG gateway and wanted to try the apex listener instead. I can't find any logs that help. Anybody have any suggestions?
    The 'config' file might have gone missing - the installation/configuration process (for Tomcat, at least) has a habit of storing the configuration xml file in 'tmp'... which then goes once you reboot! There are some posts on how to change the directory in which the configuration file is stored.

  • Apex listener 503 - Service Unavailable

    Hi,
    I installed APEX LIstener 2.0.5.
    This ist my file defaults.XML:
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
    <properties>
    <comment>Saved on Thu Jan 02 13:26:45 CET 2014</comment>
    <entry key="db.password">!apex_public_user</entry>
    <entry key="debug.printDebugToScreen">false</entry>
    <entry key="security.disableDefaultExclusionList">false</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="db.sid">ORPC3</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>
    I startet the listener with java -jar apex.war
    When I startet with http://localhost:8080/apex/f?p=4550:1:2983093393191825
    I got ORACLE APPLICATION EXPRESS LISTENER 503 - Service Unavailable
    Please help  me!
    Regards
    Siegwin

    Hi Jari,
    when I start  APEX Listener there are the answers:
    C:\>java -jar C:\app\Administrator\product\11.2.0\dbhome_2\apex_listener_2_0_5\a
    pex.war
    Jan 04, 2014 9:04:06 AM oracle.dbtools.standalone.Standalone execute
    INFO: HINWEIS:
    Der Standalone-Modus ist zur Verwendung in Entwicklungs- und Testumgebungen entw
    ickelt worden. Er wird bei Verwendung in Produktionsumgebungen nicht unterst³tzt
    Jan 04, 2014 9:04:06 AM oracle.dbtools.standalone.Standalone execute
    INFO: Standalone-Webcontainer in C:\app\Administrator\product\11.2.0\dbhome_2\ap
    ex_listener_2_0_5\config\apex wird gestartet
    Jan 04, 2014 9:04:06 AM oracle.dbtools.standalone.Deployer deploy
    INFO: Anwendung wird bereitgestellt, Pfad = C:\app\Administrator\product\11.2.0\
    dbhome_2\apex_listener_2_0_5\config\apex\apex\WEB-INF\web.xml
    Jan 04, 2014 9:04:07 AM oracle.dbtools.standalone.Deployer deploy
    INFO: Anwendung bereitgestellt, Pfad = C:\app\Administrator\product\11.2.0\dbhom
    e_2\apex_listener_2_0_5\config\apex\apex\WEB-INF\web.xml
    Jan 04, 2014 9:04:12 AM oracle.dbtools.common.config.file.ConfigurationFolder lo
    gConfigFolder
    INFO: Using configuration folder: C:\app\Administrator\product\11.2.0\dbhome_2\a
    pex_listener_2_0_5\config\apex
    Default Database connection not configured properly
    Jan 04, 2014 9:04:13 AM oracle.dbtools.rt.web.SCListener contextInitialized
    INFO: Oracle Application Express Listener initialized
    Application Express Listener version : 2.0.5.287.04.27
    Application Express Listener server info: Grizzly/1.9.49
    Jan 04, 2014 9:04:13 AM com.sun.grizzly.Controller logVersion
    INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 04.01.14 09:04
    Jan 04, 2014 9:04:13 AM oracle.dbtools.standalone.Standalone execute
    INFO: http://localhost:8080/apex gestartet.
    Jan 04, 2014 9:05:05 AM oracle.dbtools.rt.web.HttpEndpointBase modApex
    SEVERE: The pool named: apex is not correctly configured, error: ORA-01017: inva
    lid username/password; logon denied
    oracle.dbtools.common.jdbc.ConnectionPoolException: The pool named: apex is not
    correctly configured, error: ORA-01017: invalid username/password; logon denied
            at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(C
    onnectionPoolException.java:65)
            at oracle.dbtools.common.config.db.DatabaseConfig.badConfiguration(Datab
    aseConfig.java:207)
            at oracle.dbtools.common.config.db.DatabaseConfig.getPool(DatabaseConfig
    .java:346)
            at oracle.dbtools.common.config.db.DatabaseConfig.getPool(DatabaseConfig
    .java:326)
            at oracle.dbtools.common.config.db.DatabaseConfig.access$200(DatabaseCon
    fig.java:42)
            at oracle.dbtools.common.config.db.DatabaseConfig$DatabaseFactory.apply(
    DatabaseConfig.java:380)
            at oracle.dbtools.common.config.db.PerThreadConnectionCache$DisposableCo
    nnectionFactory.apply(PerThreadConnectionCache.java:233)
            at oracle.dbtools.common.config.db.PerThreadConnectionCache$DisposableCo
    nnectionFactory.apply(PerThreadConnectionCache.java:217)
            at oracle.dbtools.common.util.PerThreadCache.get(PerThreadCache.java:60)
            at oracle.dbtools.common.config.db.PerThreadConnectionCache.get(PerThrea
    dConnectionCache.java:49)
            at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(Database
    Config.java:78)
            at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.j
    ava:69)
            at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:
    372)
            at oracle.dbtools.apex.Procedure.getProcedure(Procedure.java:167)
            at oracle.dbtools.apex.OWA.validateProcedure(OWA.java:386)
            at oracle.dbtools.apex.security.Security.isValidRequest(Security.java:22
    0)
            at oracle.dbtools.apex.ModApex.validateRequest(ModApex.java:264)
            at oracle.dbtools.apex.ModApex.doGet(ModApex.java:93)
            at oracle.dbtools.apex.ModApex.service(ModApex.java:300)
            at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:
    350)
            at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:
    132)
            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.invokeFil
    terChain(ServletAdapter.java:999)
            at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.
    java:434)
            at oracle.dbtools.standalone.SecureServletAdapter.doService(SecureServle
    tAdapter.java:91)
            at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.ja
    va:379)
            at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java
    :179)
            at com.sun.grizzly.tcp.http11.GrizzlyAdapterChain.service(GrizzlyAdapter
    Chain.java:196)
            at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java
    :179)
            at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:8
    49)
            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(DefaultProtocolFil
    ter.java:228)
            at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultPro
    tocolChain.java:137)
            at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
    a:104)
            at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.jav
    a:90)
            at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java
    :79)
            at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextT
    ask.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(AbstractThreadP
    ool.java:532)
            at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool
    .java:513)
            at java.lang.Thread.run(Unknown Source)
    Please help me

  • APEX Listener 2.0 - RESTful Services Failure with  404 - Not Found

    Versions used:
    * APEX Listener 2.0.0.354.17.05
    * Application Express 4.2.1.00.08
    * Oracle Database 11.2.0.1
    When testing the sample RESTful Service Module oracle.example.hr I always get 404 - Not Found page.
    I followed the documentation to install and configure APEX 4.2 and the Listener 2.0. Everything in my APEX installation works fine except RESTful Services.
    For example, when calling this RESTful Service:
    http://company.com:45678/apex/DEV/xxuapex/hr/empinfo/
    I get a 404 page.
    The corresponding entry in url-mapping.xml is:
    <pool base-path="/DEV" name="od01" workspace-id="xxuapex"/>
    where xxuapex is the name of the schema as well as the workspace where the RESTful Service is installed.
    Moreover, the corresponding od01.xml, od01_rt.xml and od01_al.xml in the conf directory seem correct.
    Any help is greatly appreciated.
    Thanks.
    Eddie Awad.

    Hi Eddie,
    +> try the other option base-url of the url-mapping+
    I did. No change. Still getting 404.When active it should transform the 404 page into a detailed 404 with a description of what the error is. Just to be sure, this is activated in the defaults.xml file of the APEX Listener as: *<entry key="log.logging">true</entry>*.
    You should then see a detailed 404 output in your browser of what's going wrong first of all.
    +> Could you post your url-mapping.xml file?+
    <?xml version="1.0" encoding="UTF-8"?>
    <pool-config xmlns="http://xmlns.oracle.com/apex/pool-config">
    <pool base-path="/DEV" name="od01" workspace-id="xxuapex"/>
    <pool base-path="/TEST" name="ot01" workspace-id="xxuapex"/>
    </pool-config>
    Despite using the url mapping script, it didn't map mine correctly and had to edit it manually. It was the use of "apex" that got it to work for me:
    *<pool base-path="/" name="apex" workspace-id="workspace-name-here" updated="2013-01-09T20:48:59.75Z"/>*
    Nick.

  • APEX Listener and EPG - strange behaviour

    Hi
    For some years, I've used EPG for APEX but have struggled with performance particularly as I can have up to 150 student developers using at any one time.
    I do a fair amount of work using ORDImage and have successfully developed APEX applications to upload image files and display full-size and thumbnail images.
    After upgrading to APEX 4.1 (from 4.0), I decided to install APEX Listener standalone.
    Before I did so I checked that my applications still worked in 4.1 and they did.
    However, just installing APEX Listener but not configuring it (yet) has meant that my image display in a report using a procedure based on wpg_docload.download_file( l_ordimage_image.source.localData ) no longer works in EPG - the images are not displayed.
    Configuring APEX Listener and running the same application through that DOES display the images.
    So this part of the application works under APEX Listener but not under EPG.
    My application also allows users to upload images from APEX_APPLICATION_FILES using standard code. Under APEX Listener after uploading, I'm left with a blank page with a wwv_flow.accept URL although the image does indeed upload. Under EPG it works as expected and I get a success confirmation.
    So this part of the application works under EPG but not under APEX Listener.
    Has anyone else come across different behaviour depending on the mode of connection?
    Thanks
    Brian
    [Oracle EE 11gR2, Windows Server 2008R2, APEX 4.1, APEX Listener 1.1.3]

    Hi Brian,
    it sounds like you have both EPG and APEX Listener running on the same machine, so your problem might result from a port conflict. Note that both services use TCP port 8080 as default.
    At least a port conflict would explain the strange behaviour in your case, some things working on one web server and some on the other.
    Some parts of your initial post hint to that direction, e.g.
    However, just installing APEX Listener but not configuring it (yet) has meant that my image display in a report using a procedure based on >wpg_docload.download_file( l_ordimage_image.source.localData ) no longer works in EPG - the images are not displayed.... because the APEX Listener only interfere with the EPG if it is at least running on the same machine as your database and furthermore, if it is unconfigured in terms of ist database connection, a port conflict might be the only way it could cause anything like that.
    However, if you are sure that's not the issue, please check if you see any error in the APEX Listener's log for the following action you performed:
    My application also allows users to upload images from APEX_APPLICATION_FILES using standard code. Under APEX Listener after uploading, I'm left with a blank >page with a wwv_flow.accept URL although the image does indeed uploadIf you actually see just a blank screen, something very bad must have happened and you should see some kind of stack trace there.
    For further investigations, if necessary, it would be helpful to know how you deployed or started your APEX Listener and which JDK version you use.
    For the moment, I still think the port conflict is my best guess.
    You could avoid it by either changing the port for EPG (I'd not recommend that if you have other users still using it) or by changing the port for your APEX Listener.
    -Udo

  • Apex Listener Configuration Issue.

    Hi there,
    As I wanted to try the latest Restful services in apex 4.2, I decided to install Apex Listener 2.0. I downloaded the file and followed the steps as in the installation notes. As a pre-requisite, I configured the Restful services successfully in apex 4.2 along with Oracle 11g Express Edition. However, the installation of listener seems to be not compleated successfully with the following installation feed back.
    D:\software\apex_listener>java -jar apex.war
    This Listener instance has not yet been configured.
    Please complete the following prompts
    Enter the location to store configuration data:d:\apexlistnerconf
    Dec 27, 2012 3:34:47 PM oracle.dbtools.common.config.cmds.ConfigDir execute
    INFO: Set config.dir to d:\apexlistnerconf in: D:\software\apex_listener\apex.war
    Dec 27, 2012 3:34:49 PM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
    INFO: Using configuration folder: D:\apexlistnerconf\apex
    Enter the name of the database server [localhost]:
    Enter the database listen port [1521]:
    Enter 1 to specify the database service name, or 2 to specify the database SID [1]:2
    Enter the database SID [xe]:
    Enter the database user name [APEX_PUBLIC_USER]:
    Enter the database password for APEX_PUBLIC_USER:
    Password must not be empty
    Enter the database password for APEX_PUBLIC_USER:
    Confirm password:
    Enter 1 to enter passwords for the RESTful Services database users (APEX_LISTENER,APEX_REST_PUBLIC_USER), 2 to use the same password as used for APEX_PUBLIC_USER or, 3 to skip this step [1]:3
    Dec 27, 2012 3:37:03 PM oracle.dbtools.common.config.file.ConfigurationFiles update
    INFO: Updated configurations: defaults, apex
    Enter 1 if you wish to start in standalone mode or 2 to exit [1]:
    Enter the APEX static resources location or Enter to skip:D:\software\apex42en\apex\images
    Enter the HTTP port [8080]:
    Dec 27, 2012 3:41:17 PM oracle.dbtools.standalone.Standalone execute
    INFO: NOTE:
    Standalone mode is designed for use in development and test environments. It isnot supported for use in production environments.
    Dec 27, 2012 3:41:17 PM oracle.dbtools.standalone.Standalone execute
    INFO: Starting standalone Web Container in:  d:\apexlistnerconf\apex
    Dec 27, 2012 3:41:17 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Will deploy application path = d:\apexlistnerconf\apex\apex\WEB-INF\web.xml
    Dec 27, 2012 3:41:17 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Deployed application path = d:\apexlistnerconf\apex\apex\WEB-INF\web.xml
    Dec 27, 2012 3:41:18 PM oracle.dbtools.common.config.file.ConfigurationFolder logConfigFolder
    INFO: Using configuration folder: D:\apexlistnerconf\apex
    Default Database connection not configured properly
    Dec 27, 2012 3:41:20 PM 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
    Dec 27, 2012 3:41:20 PM com.sun.grizzly.Controller logVersion
    INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 12/27/12 3:41 PM
    Dec 27, 2012 3:41:20 PM com.sun.grizzly.SelectorHandlerRunner handleSelectException
    SEVERE: doSelect IOException
    java.net.BindException: No free port within range: 8080=com.sun.grizzly.http.SelectorThreadHandler@480d41f3
            at com.sun.grizzly.TCPSelectorHandler.initSelector(TCPSelectorHandler.java:432)
            at com.sun.grizzly.TCPSelectorHandler.preSelect(TCPSelectorHandler.java:378)
            at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:188)
            at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:132)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    Dec 27, 2012 3:41:20 PM com.sun.grizzly.http.SelectorThread$3 onException
    SEVERE: Exception during starting the controller
    java.net.BindException: No free port within range: 8080=com.sun.grizzly.http.SelectorThreadHandler@480d41f3
            at com.sun.grizzly.TCPSelectorHandler.initSelector(TCPSelectorHandler.java:432)
            at com.sun.grizzly.TCPSelectorHandler.preSelect(TCPSelectorHandler.java:378)
            at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:188)
            at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:132)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    java.net.BindException: No free port within range: 8080=com.sun.grizzly.http.SelectorThreadHandler@480d41f3
            at com.sun.grizzly.TCPSelectorHandler.initSelector(TCPSelectorHandler.java:432)
            at com.sun.grizzly.TCPSelectorHandler.preSelect(TCPSelectorHandler.java:378)
            at com.sun.grizzly.SelectorHandlerRunner.doSelect(SelectorHandlerRunner.java:188)
            at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:132)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
            at java.lang.Thread.run(Unknown Source)
    Dec 27, 2012 3:41:20 PM oracle.dbtools.standalone.Standalone execute
    INFO: http://localhost:8080/apex started.It simply hangs at the last line and I couldn't make any further progress.
    Can you please help to find out what went wrong?
    Thanks in advance.
    Regards,
    Natarajan

    Thank you Probodh for your quick help. I set the port 8080 to apex listener and it does not give that error now.
    However, it still says "Default Database Connection not configured properly"
    I gave the SID name as xe which is the default one, and that is the correct SID for my DB also.
    Any possible mistakes in there?
    D:\software\apex_listener>java -jar apex.war
    Dec 27, 2012 7:29:45 PM 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.
    Dec 27, 2012 7:29:45 PM oracle.dbtools.standalone.Standalone execute
    INFO: Starting standalone Web Container in:  d:\apexlistnerconf\apex
    Dec 27, 2012 7:29:45 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Will deploy application path = d:\apexlistnerconf\apex\apex\WEB-INF\web.xm
    l
    Dec 27, 2012 7:29:46 PM oracle.dbtools.standalone.Deployer deploy
    INFO: Deployed application path = d:\apexlistnerconf\apex\apex\WEB-INF\web.xml
    Dec 27, 2012 7:29:46 PM oracle.dbtools.common.config.file.ConfigurationFolder lo
    gConfigFolder
    INFO: Using configuration folder: D:\apexlistnerconf\apex
    Default Database connection not configured properly
    Dec 27, 2012 7:29:48 PM 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
    Dec 27, 2012 7:29:48 PM com.sun.grizzly.Controller logVersion
    INFO: GRIZZLY0001: Starting Grizzly Framework 1.9.49 - 12/27/12 7:29 PM
    Dec 27, 2012 7:29:48 PM oracle.dbtools.standalone.Standalone execute
    INFO: http://localhost:8080/apex started.Regards,
    Natarajan

Maybe you are looking for