fix bug in Protocol.processBulkReply()

* if RedisInputStream().read() at Protocol.processBulkReply() returns
-1, it runs with unexpected behavior
* fix: check and if return value is -1, it throws
JedisConnectionException with message "server has closed the connection"
** prevent unexpected behavior, specially ArrayIndexOutOfBoundException 
*** calls System.arraycopy() with length = -1 (cause limit = -1) at
RedisInputStream.read()

add pubsub unit test scenario : client-output-buffer-limit exceed

* Redis warns event(disconnect client) to their log, and suddenly
disconnected connection
** http://redis.io/topics/clients -> Output buffers limits
** so test expects JedisConnectionException with proper message

src/main/java/redis/clients/jedis/Protocol.java

@@ -101,7 +101,10 @@ public final class Protocol {
 	int offset = 0;
 	try {
 	    while (offset < len) {
-		offset += is.read(read, offset, (len - offset));
+	    	int size = is.read(read, offset, (len - offset));
+	    	if (size == -1)
+	    		throw new JedisConnectionException("It seems like server has closed the connection.");
+	    	offset += size;
 	    }
 	    // read 2 more bytes for the command delimiter
 	    is.readByte();