首页新闻找找看学习计划

lettuce集成使用问题

0
悬赏园豆:20 [已关闭问题] 关闭于 2018-11-01 15:00

使用Eclipse 搭建SSM框架 redis使用的lettuce,测试通过。但发现2个问题或者疑问:
1、项目启动以后每隔一分钟就会打印一堆debug的日志。
2、项目中使用了spring-redis-session来接管HttpSession。可是在我项目启动一段时间以后,我没有任何操作的情况下,会突然报redis的某个对象序列化(UserInfoPojo)错误。而这个对象只是我用来保存在登录session中的。也就是说应该是将其他工程里面用到的session对象取出时反序列化错误了。这是为什么?是否跟lettuce有关?是否跟问题1有关?

附:每分钟打印内容
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.RedisChannelHandler - dispatching command AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write() writeAndFlush command AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write(ctx, AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command], promise)
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandEncoder - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379] writing command AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write() done
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] Received: 4 bytes, 1 commands in the stack
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] Stack contains: 1 commands
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.RedisStateMachine - Decode AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.RedisStateMachine - Decoded AsyncCommand [type=SMEMBERS, output=ValueSetOutput [output=[], error='null'], commandType=com.lambdaworks.redis.protocol.Command], empty stack: true
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.RedisChannelHandler - dispatching command AsyncCommand [type=DEL, output=IntegerOutput [output=null, error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write() writeAndFlush command AsyncCommand [type=DEL, output=IntegerOutput [output=null, error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write(ctx, AsyncCommand [type=DEL, output=IntegerOutput [output=null, error='null'], commandType=com.lambdaworks.redis.protocol.Command], promise)
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandEncoder - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379] writing command AsyncCommand [type=DEL, output=IntegerOutput [output=null, error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [pool-2-thread-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] write() done
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] Received: 4 bytes, 1 commands in the stack
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.CommandHandler - [channel=0x2e362e40, /192.168.9.31:49488 -> /192.168.19.34:6379, chid=0x1] Stack contains: 1 commands
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.RedisStateMachine - Decode AsyncCommand [type=DEL, output=IntegerOutput [output=null, error='null'], commandType=com.lambdaworks.redis.protocol.Command]
14:38:00 [lettuce-nioEventLoop-4-1] DEBUG com.lambdaworks.redis.protocol.RedisStateMachine - Decoded AsyncCommand [type=DEL, output=IntegerOutput [output=0, error='null'], commandType=com.lambdaworks.redis.protocol.Command], empty stack: true

Mr.xiong的主页 Mr.xiong | 初学一级 | 园豆:79
提问于:2018-10-29 14:39
< >
分享
清除回答草稿
   您需要登录以后才能回答,未注册用户请先注册