Do not return Jedis conns to pool after NPE

DATAREDIS-153

- Return conn to pool as broken resource if NPE
occurs (for example if a null key or value is given),
preventing later flush of OutputStream with incomplete
data

- Workaround Jedis issue in pub/sub tests that prevents
subscribing with a pooled connection

- Continue not using pool in conn tests, as they
are too brittle with potentially unclosed pipelines,
unexecuted txs, etc

src/test/resources/org/springframework/data/redis/connection/jedis/JedisConnectionIntegrationTests-context.xml

@@ -4,13 +4,8 @@
 	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
 
 
-	<!-- DATAREDIS-153 We can't pool connections for this test because Jedis
-		leaves OutputSteam in compromised state on NullPointerException (which happens
-		if a null key or value is used) but doesn't remove them from the pool or
-		reconnect them on next attempted use -->
-	<bean id="jedisConnectionFactory "
-		class="org.springframework.data.redis.connection.jedis.JedisConnectionFactory"
-		p:usePool="false" p:timeout="60000">
+	<bean id="jedisConnectionFactory"
+		class="org.springframework.data.redis.connection.jedis.JedisConnectionFactory" p:timeout="60000" p:usePool="false">
 		<property name="hostName">
 			<bean class="org.springframework.data.redis.SettingsUtils"
 				factory-method="getHost" />