Timothy Bish e872f1524a 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.

2017-05-12 14:48:23 -04:00

..

activemq5-unit-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

artemis-test-support

ARTEMIS-1160 AMQP test client should configure netty WS maxFrameSize

2017-05-12 14:48:23 -04:00

config

NO-JIRA Logging integration-tests/DEBUG is being too verbose on the testsuite

2017-01-30 22:26:48 -05:00

extra-tests

NO-JIRA: bumping 2.2.0-SNAPSHOT release on extra-tests

2017-05-08 12:06:18 -04:00

integration-tests

NO-JIRA: trivial test fixes on AMQP

2017-05-12 14:36:01 -04:00

jms-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

joram-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

performance-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

smoke-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

soak-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

stress-tests

ARTEMIS-1156: moving our collections on its own package

2017-05-12 10:06:05 -04:00

timing-tests

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00

unit-tests

ARTEMIS-1156: moving our collections on its own package

2017-05-12 10:06:05 -04:00

pom.xml

[maven-release-plugin] prepare for next development iteration

2017-05-08 15:20:12 -04:00