d62c1311fb
protocol. In the wild, I've only seen this crop up in really really odd circumstances. As it turns out, the throughput tests eventually trigger this when testing TCP. I've lost sleep over wondering when this was going to bite for real so I'm glad to have what is essentially the last known bug in message transfer fixed. This change handles the case where so far only one byte of the two byte message size has been read from the network. Rare, but it can happen. git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@7976 75d07b2b-3a1a-0410-a2c5-0572b91ccdca