I installed the Apex Listener 2 production (2.0.0.354.17.05) on Glassfish 3.1.2.2, build 5. It's got deployed correct, I've followed all the necessary steps found in the installation and configuration guide. But when I enter the url: http://server:8080/apex, all I see is a blank page. I tried adding a second database, but using the url http://server:8080/apex/zeno (the name of the database is zeno), I also see a blank page.

There aren't any logfiles made when I enter the above urls. In sql developer, I checked the log options, but the logs inside SQL developer are empty, and the Glassfish logs doesn't seem to have logged an error somewhere.

When I stop the Glassfish service, there are no Apex Listener connections to my database. When I start the service, three connections are made; so the db settings must be good?

I am also facing the same problem. The issue seems to be with routing rules. If I directly access any application using f?p=12:101 type URL then I am able to access both instances of apex configured on different DB. But workspace login is still missing. I am trying to find the way out. If you solve this problem please let me know too.

I just found the solution. The issue was with routing rules. Use URL Path as routing Rule type and in Routing rule mention complete URL as http://example.com/apex/sales where /apex is the context path for apex listener on example.com and sales is the settings name in URL settings of connection. Schema for restful services is optional.

Now using http://example.com/apex/sales you will be able to access the workspace login page and no blank page will be shown.

Thanks! That was the problem. I assumed that jou don't have to enter any routing rules, that when the database name you give the connection is used in the url. But when I entered the routing rule, it works like a charm.

Hmm. It seems it works for about 10 seconds, but after 10 seconds, all it gives is a blank page (again). Even when I enter a direct (valid) url, the page is blank. After I restarted Glassfish, it works again for 10 seconds.

It occurs with both urls:
- http://server:8080/apex/f?p=102:2
- http://server:8080/apex/socho/f?p=102:2

There is no error in the server.log file, and also the 'error tracking' report in the apex listener configuration tool in sql developer states: The Application Express Listener does not contain any errors.

I also have the same issue, for me the link for the RESTful service is not working. After having configured Listener, I am able to login to apex. However, when clicking the TEST button on "Resource Handler" page on one of the RESTful services (The sample web service given by Oracle - oracle.example.hr) , listener throws error for the link http://localhost:8585/apex/natarajan/hr/empinfo/. My listener 2.0 is running as a stand alone mode on apex 4.2 and Oracle 11g.

i) /natarajan as Routing Rule
ii)/natarajan as Routing Rule and hr as schema for the RESTful services. Here "natarajan" is my workspace name and hr is the schema associated with the workspace.

For URL Path, as Muzammil suggested, I gave the full URL http://localhost:8585/apex/natarajan/hr/empinfo/.

Still it is giving the page 404 - not found error.

WebException [statusCode=404]
at oracle.dbtools.rt.web.WebException.webException(WebException.java:330)
at oracle.dbtools.rt.web.WebException.notFound(WebException.java:284)
at oracle.dbtools.rt.web.RequestDispatchers.dispatch(RequestDispatchers.java:71)
at oracle.dbtools.rt.web.HttpEndpointBase.restfulServices(HttpEndpointBase.java:336)
at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:125)
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)

Request to please find any possible issues with my configuratio and will greatly appreciate the help.

I'm having the exact same issue. I haven't been able to get the Apex 2.0 listener to work as advertised. I wouldnt' think it should be this hard. I"m using Weblogic...

I can get 1 db connection to work but any other databases don't work or only work once then stop working the next time I restart WL without me even making changes. Not ready for production as far as I can tell..

Hi Folks,
could I ask all people reporting seeing an issue with blank pages to provide the following information

OS Version, DB Version, APEX Version

There seems to be some correlation between having multiple databases defined and seeing this problem, if you do have multiple databases defined can you also include your url-mapping.xml and also indicate whether you enabled RESTful Services for each database (<pool-name>rt.xml and <pool-name>al.xml exist in the conf folder).