Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UnsupportedOperationException when using pipeline and execute #3112

Open
J4ckTh3R1pper opened this issue Feb 28, 2025 · 0 comments
Open

UnsupportedOperationException when using pipeline and execute #3112

J4ckTh3R1pper opened this issue Feb 28, 2025 · 0 comments
Labels
status: waiting-for-triage An issue we've not yet triaged

Comments

@J4ckTh3R1pper
Copy link

J4ckTh3R1pper commented Feb 28, 2025

spring-data-redis version: 3.4.3
I got following error when trying to execute a HEXPIREAT command in pipelined execution, which is kinda similar to redis/lettuce#2831 (comment)

Caused by: java.lang.UnsupportedOperationException: io.lettuce.core.output.ByteArrayOutput does not support set(long)
	at io.lettuce.core.output.CommandOutput.set(CommandOutput.java:111)
	at io.lettuce.core.protocol.RedisStateMachine.safeSet(RedisStateMachine.java:782)
	at io.lettuce.core.protocol.RedisStateMachine.handleInteger(RedisStateMachine.java:433)
	at io.lettuce.core.protocol.RedisStateMachine$State$Type.handle(RedisStateMachine.java:210)
	at io.lettuce.core.protocol.RedisStateMachine.doDecode(RedisStateMachine.java:363)
	at io.lettuce.core.protocol.RedisStateMachine.decode(RedisStateMachine.java:324)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:844)
	at io.lettuce.core.protocol.CommandHandler.decode0(CommandHandler.java:795)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:778)
	at io.lettuce.core.protocol.CommandHandler.decode(CommandHandler.java:661)
	at io.lettuce.core.protocol.CommandHandler.channelRead(CommandHandler.java:601)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1357)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:868)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:796)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:732)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:658)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)
	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:833)


@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

No branches or pull requests

2 participants