Oracle APEX Listener 1.1.3

Released September 2011

The Oracle Application Express architecture requires some form of Web server to proxy requests between a Web browser and the Oracle Application Express engine. In addition to Oracle HTTP Server/mod_plsql and the XDB HTTP protocol server/embedded PL/SQL gateway, there is now an alternative - the Oracle APEX Listener.

Changes since Release 1.2

• Fixed a problem with OWA responses of exactly 32767 characters producing error

Changes since Release 1.1

• Fixed a problem with second and subsequent deployments of the Listener using the configuration of the first Listener deployment.
• Reduced the default value of apex.jdbc.MaxConnectionReuseCount from 50000 to 1000. This may address issues with the database temp segment being exhausted (Error ORA-01652).
• Fixed a problem with character encoding when consuming HTML forms submitted using the multipart/form-data content-type.
• Fixed a problem with an IllegalStateException being thrown when the path /apex (instead of /apex/) was accessed on the standalone Listener.
• Fixed a problem where stored procedures defined by the database user which the listener connects as, could not be invoked without prefixing with the schema name.
• Fixed a problem with some JDBC settings in apex-config.xml not actually being used to configure the connection pool.
• Fixed flexible parameter support to handle POSTs without requiring a query string to be present in the submitted URI.
• Fixed a problem with the standalone Listener where the location of the images folder could not be overwritten.
• Removed obsolete cache.dir parameter from web.xml. Use the apex.cache.directory setting instead
• Removed obsolete apex-config.xml in the distribution zip file