Fix intermittently failing test.

If you fake a blocking with async write while processing a read there is
a strong chance of a deadlock. The read will be holding a lock on the
SocketWrapper. If the async write does not complete in-line it will
perform a dispatch when it is ready to write and that dispatch will try
to obtain a lock on the socket wrapper. The lock on that opbject is
already held and a deadlock will follow.

Author: markt-asf

test/org/apache/tomcat/websocket/pojo/TestEncodingDecoding.java

@@ -403,7 +403,7 @@ public static class MessagesServer {
         @OnMessage
         public String onMessage(String message, Session session) throws Exception {
             received.add(message);
-            session.getAsyncRemote().sendText(MESSAGE_ONE).get();
+            session.getBasicRemote().sendText(MESSAGE_ONE);
             return message;
         }
 
@@ -425,9 +425,9 @@ public static class BatchedServer {
         @OnMessage
         public String onMessage(String message, Session session) throws IOException {
             received.add(message);
-            session.getAsyncRemote().setBatchingAllowed(true);
-            session.getAsyncRemote().sendText(MESSAGE_ONE);
-            session.getAsyncRemote().setBatchingAllowed(false);
+            session.getBasicRemote().setBatchingAllowed(true);
+            session.getBasicRemote().sendText(MESSAGE_ONE);
+            session.getBasicRemote().setBatchingAllowed(false);
             return MESSAGE_TWO;
         }