This content has been marked as final. Show 12 replies
Forgot - Apex 4.2. Upgraded from 4.0Are you sure you've copied the new images for APEX 4.2 to your Tomcat? If so, do you use a war file to deploy them or do you use the ROOT-context to serve static contents?
After upgrade everything was working perfectly fine with 1.1.4 Listener, so my guess - this is something related to 2.0 listener itself...How much time (and how many restarts of your browser and Tomcat) had been between these two events?
Thanks for you answer, Udo!!!
Images are definitely there. As I said - 4.2 was working perfectly fine after the upgrade and new images deployed to the server.
Also, whenever I had problem with images before - there were problems with the page, but there was SOMETHING returned. Here - absolutely empty page (no source at all). Though http 200 return code.
As for time between these events - all happened the same day. We upgraded to 4.2. Deployed new images. Confirmed everything is working fine. Start playing with 2.0 listener...
Still trying to figure out what is going on...
In one of APEX_PUBLIC_USER active sessions I found SQL like this:
msg := dbms_java.endsession_and_related_state;
I'm not 100% sure, but I believe dbms_java.endsession_and_related_state is defined in 11G. We are on 10.2.0.5.0. Am I missing something?
Getting more and more interesting :-)
If you wait long enough (20-30 minutes) and refresh the browser on the same url, that was giving absolutely blank screen before (http://localhost:8080/apex/f?p=4550:1:3416114183042) - you are getting perfect login screen! All the images are fine, everything looks great. But if you try to login - getting absolutely blank screen with the url of below:
And yes - I used wrong id/password when trying to login.
OK, tried to rollback to 1.1.4 version and as expected everything is working perfectly fine.
With 2.0: Very strange - if you leave browser for 20-30 minutes on the same initially absolutely blank page and refresh - you get correct result. And after you login successfully - you have kind of regular admin screens without any delay or blank screens. If you logof - same story. Blank screens, keep them for 20 minutes alone, then refresh - you are in.
When I said "kind" of regular screens - any screens, that have interactive reports, show error "there can be one interactive report per page". And just to confirm: when we rolled back to 1.1.4 - same screens worked perfectly well.
I'm lost 100% and hope only that sooner or later some Tomcat/Listener/Apex gurus can help me :-)
Meanwhile - back to 1.1.4 working version...
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.
Edited by: Colm Divilly on Feb 8, 2013 7:45 AM
We are also interested in:
(a) whether or not the patch/fix for APEX Listener 2.0 with DBMS 10g has been completed; and
(b) (if not) what the current ETA for said patch is.
(c) What the relevant links (tech notes, bug #'s, etc.) are for monitoring progress on this issue.
Edited by: MarkB on Apr 11, 2013 10:28 AM