[
https://issues.apache.org/jira/browse/AMQ-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14542595#comment-14542595
]
Christopher L. Shannon commented on AMQ-5774:
---------------------------------------------
Timothy, thanks for the detailed explanation, that was very helpful to
understand what's going on under the covers. Now that I know that OpenWire
encodes a single message as one frame than I am fine with using maxFrameSize
and there is the added benefit of being able to check the size before
unmarshalling which would be preferred. I was also not aware that message
properties could be missed when using other protocols which would certainly be
bad. I will go ahead and close my pull request since my fix isn't going to be
the ideal solution.
I agree with your last statement about applying maxFrameSize across all
protocols. I am primarily interested in JMS and STOMP support so should I open
another Jira to add maxFrameSize support to all protocols? (especially STOMP
for my use case)
Thanks,
Chris
> 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)
