We have our own application-specific replicator that I wrote. I am
having a strange problem.

I have a transaction, which is attached to the local replicator
database, as well as the different remote databases that are
replicated together.

Once in a while, the replicator machine will lose connection with one
of the remote databases. This is fine. I have logic in the code so
that if I get a "An existing connection was forcibly closed by the
remote host." error while trying to perform an operation on one of the
remote databases, I set a flag so that the next time through the
replication loop, it will reconnect to the database.

Here's the strange thing: If the connection to the remote database is
lost, I get the "An existing connection was forcibly closed by the
remote host." error (referring to the IP address of the remote
database) even when trying to perform an update to the local
replicator database (I am trying to set the "need to reconnect" flag
there).

Why would it complain about the remote database when trying to update
the local database?

-Joe