title: red5 RTMPClient is not publishing stream if streamname is big enough
body: <p>I have a Red5 client implementation which publishes streams, loaded from video file to our wowza media server. The problem is that if stream name is to big - approximately more than 90 symbols - the client is not publishing it and fails silently. All others actions expected from client are fulfilled: it connects to server and creates a stream. But never publishes the stream. I dont see a corresponding RTMP message and I dont see a resulting reaction in the logs of wowza.</p>
  
  <p>I tried to debug the client and tracked the execution until it starts to write to SocketChannel. Everything is the same for the cases of execution of shorter named stream (which publishes ok), and stream with the long name, which RTMP command "to publish" is never sent. </p>
  
  <p>A questions are:</p>
  
  <ol>
  <li><p>whats up?</p></li>
  <li><p>if I have written some bytes to SocketChannel without any exceptions thrown - does it guarantees that the corresponding message was sent?</p></li>
  <li><p>if I have written some bytes to SocketChannel without any exceptions thrown - can I check by the means of my OS (MACOS in my case) whether the bytes were really written somewhere? Although I know, by the means of WireShark, that this piece of data was never sent.</p></li>
  </ol>
  
  <p>UPDATE
  ...and which is even more strange - after sending "the big" packet sending a smaller one doesn't help. No packets can be sent after a packet of bigger length have been submitted to the socket.</p>