134
92%

Ran 31 Jan 2015 05:04AM UTC

Jobs 1

Files 117

Run time 48s

Badge

Embed ▾

pending completion

Build # 134

Build Type

Pull #27

travis-ci

Committed by

kichik

Commit Message

Fix channel loss on reconnect
The scenario requires two or more close-by disconnections
1. Connect to Redis
2. Subscribe successfully to a channel
3. Forcibly kill the connection (by taking down Redis for example)
4. Let lettuce reconnect successfully
5. Forcibly kill the connection again right before activate() successfully subscribes
6. Let lettuce reconnect successfully
7. RedisPubSubConnectionImpl.channels is empty and the channel will stay unsubscribed

There doesn't seem to be a reason to clear out channels and patterns.
It is only used for persistence over different connections.
There is no downside to having a channel in that set even if the subscription was not successful.

Pull Request Pull Request #27: Fix channel loss on reconnect

Run Details

3508 of 3643 relevant lines covered (96.29%)

0.96 hits per line

Uncovered Existing Lines

Lines	Coverage	∆	File
1	100.0		com/lambdaworks/redis/pubsub/RedisPubSubConnectionImpl.java

Jobs

ID	Job ID	Ran	Files	Coverage
2	134.2	31 Jan 2015 05:04AM UTC	0	96.29	Travis Job 134.2

Source Files on build 134

Detailed source file information is not available for this build.

mp911de / lettuce / 134
92%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 134

mp911de / lettuce / 134 92%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build 134

mp911de / lettuce / 134
92%

README BADGES
x