WebSocket / Performance - cleaning up tests from fallout on bug 414913

+ Copying payload in test cases for comparison reasons, as the reuse of
  payloads by the implementation now means that the payload might be
  masked by a random client side mask.
+ Cleaning up Abnormal Close handling for idle timeout cases
+ Fixing logging a tag
+ Fixing intermittent test failure in jsr EchoTest

1 files changed, 6 insertions, 0 deletions

diff --git a/jetty-websocket/websocket-api/src/main/java/org/eclipse/jetty/websocket/api/StatusCode.java b/jetty-websocket/websocket-api/src/main/java/org/eclipse/jetty/websocket/api/StatusCode.java
index f286e7dbc4..ee3a13c4b9 100644
--- a/jetty-websocket/websocket-api/src/main/java/org/eclipse/jetty/websocket/api/StatusCode.java
+++ b/jetty-websocket/websocket-api/src/main/java/org/eclipse/jetty/websocket/api/StatusCode.java
@@ -75,6 +75,12 @@ public class StatusCode
      * See <a href="https://tools.ietf.org/html/rfc6455#section-7.4.1">RFC 6455, Section 7.4.1 Defined Status Codes</a>.
      */
     public final static int NO_CLOSE = 1006;
+    
+    /**
+     * Abnormal Close is a synonym for {@link #NO_CLOSE}, used to indicate a close
+     * condition where no close frame was processed from the remote side.
+     */
+    public final static int ABNORMAL = NO_CLOSE;
 
     /**
      * 1007 indicates that an endpoint is terminating the connection because it has received data within a message that was not consistent with the type of the