Issue #207 - Using connection idle-timeout declared in annotation

jetty-websocket/websocket-common/src/main/java/org/eclipse/jetty/websocket/common/WebSocketSession.java

@@ -177,6 +177,8 @@ public class WebSocketSession extends ContainerLifeCycle implements Session, Rem
         addManaged(this.endpointFunctions);
     
         super.doStart();
+        
+        connection.setMaxIdleTimeout(this.policy.getIdleTimeout());
     }
 
     @Override

jetty-websocket/websocket-common/src/main/java/org/eclipse/jetty/websocket/common/io/AbstractWebSocketConnection.java

@@ -729,9 +729,12 @@ public abstract class AbstractWebSocketConnection extends AbstractConnection imp
 
     @Override
     public void setMaxIdleTimeout(long ms)
+    {
+        if(ms >= 0)
         {
             getEndPoint().setIdleTimeout(ms);
         }
+    }
 
     @Override
     public SuspendToken suspend()

jetty-websocket/websocket-server/src/test/java/org/eclipse/jetty/websocket/server/IdleTimeoutTest.java

@@ -88,7 +88,8 @@ public class IdleTimeoutTest
             client.expectUpgradeResponse();
 
             // This wait should be shorter than client timeout above, but
-            // longer than server timeout configured in TimeoutServlet
+            // longer than server timeout configured in FastTimeoutRFCSocket
+            // eg: websocket server endpoint timeout < this timeout < websocket client idle timeout
             client.sleep(TimeUnit.MILLISECONDS,1000);
 
             // Write to server