[
https://issues.apache.org/jira/browse/ARTEMIS-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17007181#comment-17007181
]
ASF subversion and git services commented on ARTEMIS-2550:
----------------------------------------------------------
Commit 9fac4b866cf9cefbb6f7c13b820e07455b6649f5 in activemq-artemis's branch
refs/heads/master from Dewald Pretorius
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9fac4b8 ]
ARTEMIS-2550 Support Websocket Continuation Frames
Large messages can be split up using Websocket Continuation Frames.
This allows for much smaller buffer sizes to send or receive
potentially very large messages.
> Unsupported STOMP Websocket Continuation Frames
> -----------------------------------------------
>
> Key: ARTEMIS-2550
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2550
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: STOMP
> Affects Versions: 2.10.1
> Reporter: Dewald Pretorius
> Assignee: Justin Bertram
> Priority: Major
> Original Estimate: 24h
> Time Spent: 1h
> Remaining Estimate: 23h
>
> STOMP Websocket Continuation Frames are not supported.
> Large messages can be split up using Websocket Continuation Frames. This
> allows for much smaller buffer sizes to send or receive potentially very
> large messages.
> Constants to control the frame buffer sizes for STOMP can be found here:
> org.apache.activemq.artemis.core.remoting.impl.netty.TransportConstants#STOMP_MAX_FRAME_PAYLOAD_LENGTH
> The Websocket's In/Outbound Channel Handlers need to restrict message frame
> sizes to the configured maximum frame payload length.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
