I have written both a server and a client using WSE 2.0 SP3.
Generally, it works very well.  However, it is possible for the client
to fire a lot of requests in quick succession.  Occasionally when the
client fires too many requests too quickly, the server stops
responding to the client.  The server stops responding only to the
specific client that caused the problem, and it seems the server will
never again respond to that client.  If I stop and restart the client,
the communication works again.  Unfortunately, I haven't been able to
figure out what causes this nor the threshold at which it happens.
I've turned on both logging and detailed error messages, but all this
shows is "System.Web.Services.Protocols.SoapHeaderException: Server
unavailable, please try later".

What I would like is either 1) to be able to fix the problem so that
this never happens, or 2) figure out some meaningful way of preventing
the client from firing too many requests, or 3) figure out how to
resent the communications in such a situation so that the server will
respond to the client again.

There are, of course, simple ways of preventing too many requests
(e.g. timer), but I'd much prefer something elegant that is actually
linked to the problem.  For example, if the server is getting too busy
(whatever that means), have it return a response to the client telling
the client to slow down or something.

Any ideas on 1) what's causing this, and 2) how to work around it?

Thanks!
Brad.