java.util.concurrent.ExecutionException: Provider ExceptionBug? Expecting status code for size/count

[alphazero]

java.util.concurrent.ExecutionException: Provider ExceptionBug? Expecting status code for size/count

[jabley]

Please let me know if I can provide any further information which will help me understand why I'm seeing this problem. Currently, I'm having to restart each app server multiple times a day.

[alphazero]

Hi Jabley,

First thought was that the client and server were mismatched. But looks like a concurrent use of the connection. In general, unless you have client/server version mismatch, that sort of un-expected token in the response is generally due to 2 or more thread using a non-threadsafe connector.

1. Try using a pipeline connection instead.

2. Alternatively, see what happens if you comment out "connectionSpec.isReliable(true);"

[jabley]

Just to be explicit: the JRedisAsyncClient reference is being used as a shared resource across all request threads in my webapp, with no external mutex acting as a barrier. Is that a safe way of using it?

I'm going to switch this to using a pipeline connection instead and see what happens, as you suggest.

[jabley]

So my understanding of your suggestion is to change the JRedisFuture implementation that I am using; i.e. from
redis = new JRedisAsynchClient(connectionSpec);
to
redis = new JRedisPipeline(connectionSpec);

I haven't found any documentation showing how to use this class (wiki / Javadoc). Are you familiar with the JSR-305 or JCIP annotations regarding thread-safety? I've found them useful from a documentation perspective at least.

I'll make the above change to my code and try to test. Unfortunately, I'm not able to reliably reproduce the problem, so I'll just have to see if the current situation improves at all.

Cheers,

James

[alphazero]

Its not thread safe.

Semantics are defined: JRedsAsynch interface. Its identical to any implementation of JRedisAsynch.

Its trivial to reproduce the problem: the heartbeat is sending PING and expecing +Pong. That's a status response. Just simply do a tight loop with INCR (expecting a number response) and you'll get your exception.