This content has been marked as final. Show 6 replies
When you say that you're experiencing this behaviour "through normal use", could you possibly provide some steps so we can attempt to reproduce the behaviour you're reporting?
Hi Scott,1 person found this helpful
this is a known issue with Apex Listener standalone. We were also puzzled by that on the OOW demo booths. It's caused by browsers automatically requesting /favicon.ico, although you don't see that request in the chrome dev tools. I found it with wireshark. The standalone listener redirects everything that is not /i/* or /apex/* to /apex, where it invalidates the builder session. The Apex Listener guys are already aware of that issue.
You could embed the listener in another web server or run a proxy server in front, to circumvent the logouts.
Thanks for the info & suggestions - although anything involving networking is my Achilles, so I wouldn't know how to action your suggestions.
Happy to wait for a patched listener. I run multiple browsers, and I think it tends to happen when running applications in mobile UI in same browser as developer.
I never encountered the problem when using apex.oracle.com, so story is checking out.
as you surely know, you can install the Apex Listener in Weblogic or Glassfish. It's described in the Apex Listener docs, there are also blog posts with screenshots and even videos about the installation out there. Maybe that's worth checking out again, even if you are not so well versed in networking.
I realise you're politely suggesting I venture out instead of being spoon fed in here - I know there is a fine line between RTFM & assistance, but every time I attempt it I quickly get lost.
I would like to retain the stand-alone option - I've used glassfish & others in the past, and I like the "thin-ness" the standalone option provides.
Would you please elaborate or provide some direction on what you mean by
run a proxy server in frontThere is only one reference to the word "proxy" in the installation instructions.
and other searches are resulting in scenarios irrelevant to the task at hand.
the proxy server would be another web server that sits in front of Apex Listener standalone. For example, you could install Apache (not necessarily Oracle HTTP server) and add something like
to the configuration. For example, on one of my machines (running Oracle Enterprise Linux with OEL's Apache), I put these lines in /etc/httpd/conf.d/apex.conf. After a restart of Apache, it serves /i/ directly and passes all requests to /apex/... on to http://127.0.0.1:8888/apex/... In that configuration, Apex Listener standalone has to listen on port 8888 on the same machine (127.0.0.1, or localhost). You will have to consult /etc/httpd/conf/httpd.conf to find the port where Apache listens (e.g. "Listen 8080") and maybe modify it, to avoid server port clashes.
Alias /i/ /path/to/apex/images/ <Location /apex/> ProxyPass http://127.0.0.1:8888/apex/ ProxyPassReverse http://127.0.0.1:8888/apex/ </Location>
Other HTTP servers (e.g. NGINX) can also be used as proxy servers, the config syntax is different. I wasn't suggesting to RTFM, but since you mentioned that you were not really comfortable with that lower level web stuff, I thought blogs with install pics would be more appealing to you.
Btw, just for reference: An easy way to test if your Apex Listener version is affected by that bug is to go to
If the builder login shows up, the request just nuked your previous builder session.
Edited by: Christian Neumueller on Nov 26, 2012 7:27 AM