WebSocket Client ignores maxFrameSize property

[andlinger]

Describe the bug

The Quarkus Websocket Client from the extension io.quarkus:quarkus-websockets-client.
There was already an issue about this: #17206
It seems that the problem happens again in Quarkus 2.3.0.Final.

I create the session as described in the documentation:

ContainerProvider.getWebSocketContainer().connectToServer(EmptyEndpoint.class, URI.create(url));

@ClientEndpoint(decoders = DevToolsResponseDecoder.class, encoders = DevToolsRequestEncoder.class)
public static class EmptyEndpoint {}

Property max-frame-size is configured.
quarkus.websocket.max-frame-size=15000000

Expected behavior

The frame size should match the configuration.

Actual behavior

The frame size does not match the configuration.

io.netty.handler.codec.http.websocketx.CorruptedWebSocketFrameException: Max frame length of 1280000 has been exceeded.
	at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.protocolViolation(WebSocket08FrameDecoder.java:424)
	at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.decode(WebSocket08FrameDecoder.java:286)
	at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:507)
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:446)
	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
	at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)
	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)

How to Reproduce?

No response

Output of uname -a or ver

Darwin Kernel Version 20.6.0

Output of java -version

openjdk version "11.0.12" 2021-07-20

GraalVM version (if different from Java)

21.2.0 (build 11.0.12+6-jvmci-21.2-b08)

Quarkus version or git rev

2.3.0.Final

Build tool (ie. output of mvnw --version or gradlew --version)

------------------------------------------------------------ Gradle 6.8 ------------------------------------------------------------ Build time: 2021-01-08 16:38:46 UTC Revision: b7e82460c5373e194fb478a998c4fcfe7da53a7e Kotlin: 1.4.20 Groovy: 2.5.12 Ant: Apache Ant(TM) version 1.10.9 compiled on September 27 2020 JVM: 11.0.12 (GraalVM Community 11.0.12+6-jvmci-21.2-b08) OS: Mac OS X 11.5 x86_64

Additional information

No response

[quarkus-bot]

/cc @evanchooly

[gsmet]

/cc @stuartwdouglas I suppose we don't apply the config properly in the client anymore?

[stuartwdouglas]

Looks like this was never propagated to the client: quarkusio/quarkus-http#88