Server stops responding after a while when exchange.Accept used in resource with high message rate.

[Brumawen]

When using exchange.Accept in a resource with a high incoming rate (250+ messages/sec) the server stops responding to all messages after 2-3 minutes. Investigations so far point to possible Task Starvation. If exchange.Accept is commented out, then the server stabilizes and responds to all messages being received.

Replication is easy.

• Create a resource that accepts a message and immediately executes an exchange.Accept and then, after a delay of 2 seconds, sends the response.
• Send 250+ messages a second to the server
• After 2-3 minutes, the server will stop responding to all messages.