[
https://issues.apache.org/jira/browse/QPID-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503972#comment-16503972
]
Keith Wall edited comment on QPID-8203 at 6/7/18 7:43 AM:
----------------------------------------------------------
Production code change (master.7.0.x) looked reasonable. The new protocol
test file didn't follow the naming conventions demanded by the configuration of
the maven-surefire-plugin, so wasn't being run when invoked from Maven. I
fixed that and added a 0-10 protocol test. I noted that an equivalent AMQP 1.0
test already existed.
was (Author: k-wall):
Production code change (master.7.0.x) looked reasonable. The new protocol
test file didn't follow the naming conventions demanded by the configuration of
the maven-surefire-plugin, so wasn't being run when invoked from Maven. I
fixed that and added a 0-10 protocol test. I noted that a AMQP 1.0 already
existed.
> [Broker-J][AMQP 0-9] Improve maximum message size check
> -------------------------------------------------------
>
> Key: QPID-8203
> URL: https://issues.apache.org/jira/browse/QPID-8203
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.3, qpid-java-broker-7.0.2,
> qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, qpid-java-broker-7.0.4
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Critical
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.5
>
>
> Maximum message size check needs to be improved
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
