[
https://issues.apache.org/jira/browse/AMQ-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542614#comment-14542614
]
Timothy Bish commented on AMQ-5774:
-----------------------------------
What I would do is to open a more general issue about maxFrameSize and its
usage across all the protocols / transports, then create subtasks for each
protocol to test and validate / fix them such that there is some reasonable
implementation of maxFrameSize processing done for each. I am currently
spending a lot of time in AMQP land so I could take on that one right now and
if you want to tackle STOMP that'd be good.
So for STOMP you'd wan to test TCP, SSL, NIO and NIO+SSL and if feeling really
motivated also STOMP over WS and WSS. I think there is some checks in STOMP
now for maximum body size and possibly some others but I think this should be
group under a more general application of maxFrameSize which I'm not sure is
being done right now.
> Add maximum message size per transport
> --------------------------------------
>
> Key: AMQ-5774
> URL: https://issues.apache.org/jira/browse/AMQ-5774
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Christopher L. Shannon
> Priority: Minor
>
> It would be useful to be able to configure a limit for the maximum size per
> message that can be sent by a client per transport. This will help prevent
> bad behaving clients from affecting the performance of the broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
