You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/05/04 20:55:04 UTC

[jira] [Updated] (AMQ-6669) AMQP: WS connections don't respect maxFrameSize value on transportConnection

     [ https://issues.apache.org/jira/browse/AMQ-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish updated AMQ-6669:
------------------------------
    Fix Version/s: 5.14.6

> 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)