You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/03/01 16:49:18 UTC
[jira] [Commented] (QPID-6962) [Java Broker] Add ability to limit
max message size on a per VirtualHost basis
[ https://issues.apache.org/jira/browse/QPID-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173927#comment-15173927 ]
Keith Wall commented on QPID-6962:
----------------------------------
One comment:
# We said that the correct way to use context variables was for the owing object to materialise the context variable once (in #onOpen) as an derived attribut. I think that AmqpPort.PORT_MAX_MESSAGE_SIZE and VirtualHost.MAX_MESSAGE_SIZE should be treated this way and then AMQPConnection should refer to the derived attributes. I expect this too will prevent the NPEs that are being logged by many unit test (ProtocolEngine_1_0_0Test) etc.
> [Java Broker] Add ability to limit max message size on a per VirtualHost basis
> ------------------------------------------------------------------------------
>
> Key: QPID-6962
> URL: https://issues.apache.org/jira/browse/QPID-6962
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> Currently the maximum message size can be specified on a per port basis, but where there are multiple virtual hosts using the same port, it is impossible to set different max message sizes for different ports.
> We should ensure that these limits are obeyed by all protocols, and that messages are only accepted if they are below both the port and virtual host limits.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org