[
https://issues.apache.org/jira/browse/AMQ-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997417#comment-15997417
]
ASF subversion and git services commented on AMQ-6669:
------------------------------------------------------
Commit bc879d762ab4b5e32df9d4bd50c19c192a87a777 in activemq's branch
refs/heads/activemq-5.14.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=bc879d7 ]
https://issues.apache.org/jira/browse/AMQ-6669
Respect the wireFormat.maxFrameSize option on WS and WSS transports
allowing binary content larger than 65535
(cherry picked from commit 2e2d5ddd3de7d0fe36ce5eb3d4fe81e97fe990a4)
> AMQP: WS connections don't respect maxFrameSize value on transportConnection
> ----------------------------------------------------------------------------
>
> Key: AMQ-6669
> URL: https://issues.apache.org/jira/browse/AMQ-6669
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.14.5
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.15.0, 5.14.6
>
>
> For AMQP WebSocket connections the maxFrameSize setting on the ws Transport
> doesn't modify the sockets maxBinaryMessageSize option to allow packets
> larger than 65535 through leading to a dropped connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
