Remove assertions that assert a completed op isn't timed out

Matt was trying to assure we weren't erroneously marking something
timedout that had been completed. The timeout can come from either
the IO thread or the latch from the asynch call. Now that we have
synchronized methods this shouldn't happen.

Change-Id: I4b7e02f839074f80909d4f0fb44b707b76a1a5d5
Reviewed-on: http://review.couchbase.org/9436
Reviewed-by: Matt Ingenthron <[email protected]>
Tested-by: Michael Wiederhold <[email protected]>

Author: Mike Wiederhold

src/main/java/net/spy/memcached/protocol/BaseOperationImpl.java

@@ -157,7 +157,6 @@ public void setHandlingNode(MemcachedNode to) {
 
         @Override
         public synchronized void timeOut() {
-	    assert (state != OperationState.READING || state != OperationState.COMPLETE);
             timedout = true;
             callback.complete();
         }
@@ -172,7 +171,6 @@ public synchronized boolean isTimedOut(long ttlMillis) {
 		long elapsed = System.nanoTime();
 		long ttlNanos = ttlMillis * 1000 * 1000;
 		if (elapsed - creationTime > ttlNanos) {
-			assert (state != OperationState.READING || state != OperationState.COMPLETE);
 			timedOutUnsent = true;
 			timedout = true;
 			callback.complete();