Another issue - LargeServerMessage map in replication end point - items aren't removed if the send was aborted - this could result in a memory leak.
No comments on these issues?
Also, one more: Why are you replicating non persistent large messages? Doesn't make sense.
"It's an easy fix, but I can't work out how this code ever worked... Any ideas?"
It seemed to be something else when I was debugging this. I would need to debug it.
Regarding the mapping.. I should send an endLargeMessage if the transmission is interrupted. (I.e. if I get another message on the ServerSession before completing the currentLargeMessage).
I would need to spend some time on it.