[
https://issues.apache.org/jira/browse/AMQ-7327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972599#comment-16972599
]
ASF subversion and git services commented on AMQ-7327:
------------------------------------------------------
Commit a6a83b50e1e6cc7293eaec2eb215da60a6b5c92c in activemq's branch
refs/heads/activemq-5.15.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=a6a83b5 ]
[AMQ-7327] Updated unit test around maxFrameSize support on the http transport
connector
(cherry picked from commit 397ede661f505eac82cebcd63e40c06925a7889d)
> HTTP transport connector doesn't limit the message size using maxFrameSize
> --------------------------------------------------------------------------
>
> Key: AMQ-7327
> URL: https://issues.apache.org/jira/browse/AMQ-7327
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.15.10
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.0, 5.15.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ws}} transport connector uses the {{maxFrameSize}} to set binary and
> text message size limit.
> However the {{http}} transport connector doesn't and the user needs a hack on
> {{jetty.xml}}.
> The {{http}} transport connector should directly use the {{maxFrameSize}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
