[TriLUG] Web Site access testing

[Brian McCullough via TriLUG]

Thank you all for the valuable suggestions.

In no particular order, it turned out to be DNS issues, Firewalls
between segments of the network, and, most importantly in this case, the
above causing the application not to be able to reach its database.


The 25-30 second delay was composed of 15+ seconds of timeout trying to
contact the database, and 10+ seconds sending the e-mail message
complaining about that to a non-existent e-mail address!

Once the firewall issue blocking the application's access to the
database had been resolved, things still didn't work until an entry had
been put into /etc/hosts giving an address to the name of the database
machine.

The web application itself rarely uses the database since the displayed
content is part of the code.


Response is MUCH better now, just as fast as it can be displayed on the
browser. 



Once more "the Oracle" comes through.

Thanks again,
Brian