The .web application creates a database object with 5 connections to the
Oracle database that is not behind a firewall. That database then has
some distributed updates with a remote Oracle database that is behind
another organizations firewall. Their firewall will time out the remote
session/link after 2 hours of inactivity. All subsequent DML from the
web application that involves the remote database fails with an
end-of-file communication error from Oracle. The only way we have
figured to solve the problem is by restarting the .web application or
programatically disconnecting the database object and reconnecting it
before retrying the DML. This takes too long and is a very inelegant
solution.
If any of you have suggestions to solve this problem, I would be very
interested in discussing them. We have already tried things like closing
and re-opening the link on the database stored procedure side, but that
is not working well.
Thanks
-Rattan