activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6675) AMQP Test client doesn't configure its netty WS handler with the AMQP frame size
Date Thu, 11 May 2017 22:38:04 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007322#comment-16007322
] 

ASF subversion and git services commented on AMQ-6675:
------------------------------------------------------

Commit 88efa01e119197fb043a890c54ddb37abce21ff4 in activemq's branch refs/heads/master from
[~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=88efa01 ]

AMQ-6675 AMQP Test client can't accept bigger frames on WS 

Need to configure the WS Handshaker in the test client's netty transport
with the same value given to the proton connection via setMaxFrameSize
so that incoming frames larger than the default 65535 over WS don't
trigger netty to fail the connection.

> AMQP Test client doesn't configure its netty WS handler with the AMQP frame size
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-6675
>                 URL: https://issues.apache.org/jira/browse/AMQ-6675
>             Project: ActiveMQ
>          Issue Type: Test
>          Components: AMQP
>    Affects Versions: 5.14.5
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.15.0
>
>
> The AMQP test client's WS transport should be configured with the AMQP max frame size
given to it's proton connection otherwise the broker can send it a larger frame than it's
Netty WS handshaker will accept leading to dropped connections due to max incoming frame size
violations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message