[
https://issues.apache.org/jira/browse/ARTEMIS-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010455#comment-16010455
]
ASF subversion and git services commented on ARTEMIS-1160:
----------------------------------------------------------
Commit e872f1524abe5738d96feff3a53bd9d25f0151f8 in activemq-artemis's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=e872f15 ]
ARTEMIS-1160 AMQP test client should configure netty WS maxFrameSize
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: ARTEMIS-1160
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1160
> Project: ActiveMQ Artemis
> Issue Type: Test
> Components: AMQP
> Affects Versions: 2.1.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 2.2.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)
