This discussion is archived
12 Replies Latest reply: Feb 8, 2013 7:47 AM by Colm Divilly RSS

blank screen after login listener hung

cawli2 Newbie
Currently Being Moderated
I have installed the apex listener 2.0.0, standalone, apex 4.2. I start the listener, browse to localhost:8080/apex and the login screen appears. I fill in internal/admin/password, hit enter, and the screen goes blank. It is subsequently non-responsive.

This is repeatable.

any suggestions?

windows server 2008, rdbms 10.2.0.4. java 1.6_38 and also tried with 1.7. tried with firefox and chrome.
previously tried with glassfish, but now uninstalled it to isolate problem at the basics

Wayne Linton

Edited by: cawli2 on Jan 14, 2013 4:40 PM
  • 1. Re: blank screen after login listener hung
    Colm Divilly Journeyer
    Currently Being Moderated
    Can you verify that your APEX static resources are configured correctly, in particular that the version string for /i/apex_version.txt matches the installed APEX version, see here:

    https://cdivilly.wordpress.com/2013/01/08/configuring-application-express-static-resources-with-listener-2-0/

    Thanks,
    Colm
  • 2. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    thanks,

    I've been bashing my head on images but everything looks as it should:

    from dba_registry:

    APEX
    Oracle Application Express
    4.2.1.00.08 VALID 10-JAN-2013 22:10:20 SERVER SYS
    APEX_040200 VALIDATE_APEX
    FLOWS_FILES

    and from localhost:8080/i/apex_version.txt

    Application Express Version: 4.2.1

    I can enter this url in the browser many times and get a response. But as soon as I enter something 'real' like this:

    localhost:8080/apex

    I get a blank screen.

    I seem to get one crack at displaying something on the /apex/ route, then that's it - blank screens after that.

    Is it required to set up these special routes/maps to solve this image issue as I've read elsewhere? Seems not right.

    Wayne

    Edited by: cawli2 on Jan 15, 2013 8:14 AM

    Edited by: cawli2 on Jan 15, 2013 8:16 AM
  • 3. Re: blank screen after login listener hung
    Colm Divilly Journeyer
    Currently Being Moderated
    No you should not need to setup any routes, can you try the following:

    /apex/ (note trailing slash)
    /apex/f?p=4550:1

    Can you post the full http response (use Firebug etc to get this) so I can see the HTTP headers and the response body. Can you view source on the returned response to see if it has any content.

    I assume your db is configured as follows:

    pool named: 'apex'

    conf folder contains:

    defaults.xml
    conf/apex.xml
    conf/apex_al.xml
    conf/apex_rt.xml

    apex.xml db.username = APEX_PUBLIC_USER
    apex_al.xml db.username = APEX_LISTENER
    apex_rt.xml db.username = APEX_REST_PUBLIC_USER

    You are not seeing any log messages about connections not being correctly configured.

    If any of the above assumptions are not correct, please let me know how your environment differs

    Thanks,
    Colm
  • 4. Re: blank screen after login listener hung
    Damir Vadas Newbie
    Currently Being Moderated
    Hi,
    Excuse if I'm wrong but I think that Apex listener needs additional installation.
    So, did you pass section "Configure RESTful Services" (after Apex 4.2.1 installation)?
    Described in "http://docs.oracle.com/cd/E37097_01/doc/install.42/e35123/otn_install.htm", 3.3.4 Configure RESTful Services

    rg
    Damir Vadas
    http://damir-vadas.blogspot.com
  • 5. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    yes I did set that up.
  • 6. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    No you should not need to setup any routes, can you try the following:

    +/apex/ (note trailing slash)+
    +/apex/f?p=4550:1+

    did that, same blank screen (note that I DO get one first screen, the login screen, but after that, nothing)

    Can you post the full http response (use Firebug etc to get this) so I can see the HTTP headers and the response body. Can you view source on the returned response to see if it has any content.

    From firebug:

    Response Headers
    Server     grizzly/1.9.49
    Content-Type     text/plain; charset=iso-8859-1
    Content-Length     0
    Date     Tue, 15 Jan 2013 21:15:30 GMT
    Request Headersview source
    Host     localhost:8080
    User-Agent     Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
    Accept     text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
    Accept-Language     en-US,en;q=0.5
    Accept-Encoding     gzip, deflate
    Connection     keep-alive
    Cookie     ORA_WWV_USER_71328134294939=777730A9CCD53B738B4B26C835BF0EE5

    there is no source/content on the page.


    I assume your db is configured as follows:

    pool named: 'apex'

    conf folder contains:

    defaults.xml
    conf/apex.xml
    conf/apex_al.xml
    conf/apex_rt.xml

    apex.xml db.username = APEX_PUBLIC_USER
    apex_al.xml db.username = APEX_LISTENER
    apex_rt.xml db.username = APEX_REST_PUBLIC_USER

    Correct.

    You are not seeing any log messages about connections not being correctly configured.

    If any of the above assumptions are not correct, please let me know how your environment differs

    nothing comes out in the listener log/screen even though I have turned on all the logging/debugging parameters.
    I get no clues whatsoever from this dreaded listener. horrible thing to work with.

    Wayne
  • 7. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    I note in Firebug that I am getting

    POST wwv_flow.accept 302 Moved Temporarily localhost:8080 454 B

    when the first screen is posted with login credentials.

    The response is:

    Failed to load source for: http://localhost:8080/apex/wwv_flow.accept

    On subsequent attempts I got "reload to get source for ..." and when I reloaded, I finally got some content for what it's worth...

    <html>
    <head></head>
    <body>
    <pre></pre>
    </body>
    </html>



    wayne

    Edited by: cawli2 on Jan 15, 2013 3:34 PM
  • 8. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    by the way, just to validate the apex 4.2 installation, a dad was set up in an OHS machine and it works just fine. This is clearly a listener problem.

    Wayne
  • 9. Re: blank screen after login listener hung
    Damir Vadas Newbie
    Currently Being Moderated
    Did you really verify Apex installation? Details in:
    "APEX Installation Verification Script [ID 1254932.1]"

    Could you check invalid objects in your database ...

    Haven't seen db version ... if 11g ACL settings is fine I suppose ...
    Rg
    Damir Vadas
    http://damir-vadas.blogspot.com
  • 10. Re: blank screen after login listener hung
    cawli2 Newbie
    Currently Being Moderated
    yes, I ran utlrp and ran the verify script. all apex/flows objects are valid.

    I give up. I got it working with OHS in as long as it takes to set up a DAD. I don't need this frustration. Let's just say that I am not at all impressed with this new listener. I've wasted more than 2 mandays fiddling with this particular deployment.

    I've previously installed it with glassfish in Linux and Windows, including the 2EA release, but all were on 11g installs (11.2.0.3 and XE). My guess is that 10g is problematic in some way and I do not have the time to bother with this.

    Thank you to all who tried to help me.

    Wayne Linton
  • 11. Re: blank screen after login listener hung
    user382328 Newbie
    Currently Being Moderated
    I've same problems listed on this page. This (Apex Listener 2) is a RAW product
  • 12. Re: blank screen after login listener hung
    Colm Divilly Journeyer
    Currently Being Moderated
    Thanks for your report,

    there is a regression in Listener 2.0.0 that causes APEX not to work properly on 10.x databases. We will release a patch release of 2.0 to address this (and other issues reported in this forum) in due course. The problem does not affect 11.x databases.

    C.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points