微信公众号搜"智元新知"关注
微信扫一扫可直接关注哦!

Java Lettuce Redis 客户端中的RedisCommandExecutionException

如何解决Java Lettuce Redis 客户端中的RedisCommandExecutionException

我在使用带有 ACL 的 Java Lettuce Redis 客户端时遇到问题:我收到一个 io.lettuce.core.RedisCommandExecutionException: WRONGPASS invalid username-password pair or user is disabled 异常。 我有一个配置如下的Redis Docker容器:

我的Dockerfile

FROM redis:6.2.1

copY redis.conf /usr/local/etc/redis/redis.conf
copY users.acl /etc/redis/users.acl

EXPOSE 6379

CMD ["redis-server","/usr/local/etc/redis/redis.conf"]

redis.conf 文件是:

aclfile /etc/redis/users.acl

users.acl 文件是:

user myuser on +@all ~* >mypassword
user default off

我使用以下命令运行容器:

docker run -it -p 6379:6379 --name myredis myredis

我的 Java 客户端是:

...

import io.lettuce.core.RedisClient;
import io.lettuce.core.api.StatefulRedisConnection;

public class Main {
    public static void main(String... args) {
        try {
            RedisClient redisClient = RedisClient.create("redis://myuser:mypassword@localhost");
            StatefulRedisConnection<String,String> connection = redisClient.connect();
            System.out.println("Connected to Redis");
            connection.close();
            redisClient.shutdown();
        } catch (Exception e) {
            e.printstacktrace();
        } finally {
            System.out.println("End!");
        }
    }
}

当我尝试运行它时,出现错误

io.lettuce.core.RedisConnectionException: Unable to connect to localhost:6379
    at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:78)
    at io.lettuce.core.RedisConnectionException.create(RedisConnectionException.java:56)
    at io.lettuce.core.AbstractRedisClient.getConnection(AbstractRedisClient.java:234)
    at io.lettuce.core.RedisClient.connect(RedisClient.java:207)
    at io.lettuce.core.RedisClient.connect(RedisClient.java:192)
    at [MY_PACKAGE].Main.main(Main.java:16)
Caused by: io.lettuce.core.RedisCommandExecutionException: WRONGPASS invalid username-password pair or user is disabled.
    at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:135)
    at io.lettuce.core.ExceptionFactory.createExecutionException(ExceptionFactory.java:108)
    at io.lettuce.core.protocol.AsyncCommand.completeResult(AsyncCommand.java:120)
    at io.lettuce.core.protocol.AsyncCommand.complete(AsyncCommand.java:111)
    at io.lettuce.core.protocol.CommandHandler.complete(CommandHandler.java:654)
    at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:614)
    at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:565)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
    at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
    at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1422)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
    at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:931)
    at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
    at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:700)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:635)
    at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:552)
    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514)
    at io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050)
    at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.base/java.lang.Thread.run(Thread.java:834)

我做错了什么?提前致谢。

解决方法

这对我有用(生菜 6.0.4),但它是纯粹的魔法:

改变

user default off

进入

user default off -@all +hello

我阅读了 redis 和 lettuce 文档,但找不到合适的解释,但这对您来说可能听起来更合理:

user default on nopass -@all +hello

这将使客户端能够使用默认用户仅运行 hello 命令,然后通过某种方式,客户端将知道使用配置的用户 (myuser) 执行进一步的命令。

希望能帮到你,等待大家的解释:penguin:

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。