I was testing out different codecs in different environments connected to the same redis instance. I provided a different `keyPrefix` in `context.xml` to prevent one environment's codec from messing with another environment's session management. However, since the `keyPrefix` is only applied to the session contents themselves and not the topic subscription, codec errors were still present and causing a lot of log spew.
I expected `keyPrefix` to apply not only to the session contents but also to the topic updates, so I'm publishing this PR to see if you guys agree.
Here are example of updates for two different codecs with two different `keyPrefix` BEFORE this commit is applied.
```+1544721052.037348 [0 10.0.1.184:40588] "publish" "redisson:tomcat_session_updates:" "{\"@class\":\"org.redisson.tomcat.AttributesPutAllMessage\",\"attrs\":{\"@class\":\"java.util.HashMap\",\"session:thisAccessedTime\":[\"java.lang.Long\",1544721052035],\"session:isNew\":true,\"session:lastAccessedTime\":[\"java.lang.Long\",1544721052035],\"session:maxInactiveInterval\":3600,\"session:isValid\":true,\"session:creationTime\":[\"java.lang.Long\",1544721052035]},\"nodeId\":\"a2a9d075-4b40-4ea4-a8f4-174cb8caaa08\",\"sessionId\":\"1D83362C925593187FB081FE63BD14D0\"}"```
```+1544721052.300687 [0 10.0.0.213:55652] "publish" "redisson:tomcat_session_updates:" "\xac\xed\x00\x05sr\x00*org.redisson.tomcat.AttributeUpdateMessage\x04\x81\x81\xaa!\xb5\xabE\x02\x00\x02L\x00\x04namet\x00\x12Ljava/lang/String;L\x00\x05valuet\x00\x12Ljava/lang/Object;xr\x00$org.redisson.tomcat.AttributeMessage_\xc4\xf5\xe6~\xa9v\xa3\x02\x00\x02L\x00\x06nodeIdq\x00~\x00\x01L\x00\tsessionIdq\x00~\x00\x01xpt\x00$178c19c3-a5d5-4152-bf99-72c5102c0addt\x00 1CAE476D1DCC75948E8DBD7BCA48FF16t\x00\rsession:isNewsr\x00\x11java.lang.Boolean\xcd r\x80\xd5\x9c\xfa\xee\x02\x00\x01Z\x00\x05valuexp\x00"```
Nikita Koksharov
Nikita Koksharov
Alex
Rui Gu