Browser Timeout with no response on login attempt

Question

Environment: Windows XP running Oracle 10gR1 and Application Express 3.1.2
Situation: I have a working ApplExpresss application .. it has worked for over two years. All of a sudden, two days ago, when I attempted to log-in via the browser there was a time-out with no response whatsoever. I've checked my firewall settings, looked for log entries, etc and I have found nothing to signal what the problem is.
My browser connect string is "http://<ip address>:7777/pls/htmldb/f?p=102:1". Port 7777 is open in the firewall. I'm running Apache and the DADS.CONF file is:
Alias /i/ "f:\oracle\product\10.1.0\db_2\htmldb\images/"
AddType text/xml xbl
AddType text/x-component htc
<Location /pls/htmldb>
SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername HTMLDB_PUBLIC_USER
PlsqlDatabasePassword Yesterday04
PlsqlDatabaseConnectString 128.135.244.193:1521:diyalah.orientalinstitute.uchicago.edu ServiceNameFormat
PlsqlDefaultPage htmldb
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDocumentPath docs
PlsqlDocumentProcedure wwv_flow_file_manager.process_download
PlsqlAuthenticationMode Basic
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
</Location>
I am able to connect to the database using SqlDvlpr without difficulty. I would appreciate any suggestions for what to investigate to re-establish the connection.
Thanks,
George
Edited by: George on Feb 3, 2012 7:50 AM

Answer 1

George,
Sorry to be so dumb, but what is 'OHS'?If somebody had to apologize, it would be me for assuming you'd have to know that acronym. It stands for Oracle HTTP Server, and I assumed that's the "Apache" you referred to.
Another thing comes up my mind as I review your dads.conf: Did you really always use HTMLDB_PUBLIC_USER to connect to your APEX? When HTMLDB became APEX, the default user for the mod_plsql-Connection became APEX_PUBLIC_USER . So is there any chance that either this or some synonyms etc. in your database changed lately? Could you try to use APEX_PUBLIC_USER instead (needing, of course, a reload of your Apache's config to find out).
-Udo