title: websocket closing connection automatically
body: <p>I'm building an application in java that has an embedded websocket server based on jetty. The client is the default websocket implementation in google chrome. Everything is working ok, only if there is no transfer between server and client after a certain time the connection is closed. 
  I'm not sure who's closing the connection: the jetty server or the chrome browser.</p>
  
  <p>The solution to this I think is to send a message every x seconds, but I'm opened to better solutions.</p>
  
  <p>SO... my questions are:</p>
  
  <ol>
  <li><p>Is this something that the websocket protocol requires and in this case the chrome browser is closing my connection?</p></li>
  <li><p>Is this something that is more jetty related and has more or less to do with the websocket protocol? In this case how do I disable this in jetty?</p></li>
  <li><p>Is there another problem??</p></li>
  </ol>
  
  <p>Thanks</p>
  
  <p><strong>UPDATE: even if I send 1 message/second still the connection is closed</strong></p>