[
https://issues.apache.org/jira/browse/QPID-8217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8217:
-----------------------------
Comment: was deleted
(was: QPID-6962 added ability to impose max message size on a per virtual host
basis. This ability was lost as as part of refactoring made in
[https://svn.apache.org/r1745091] against QPID-7000. It seems it make sense to
restore this ability)
> [Broker-J] Evaluation of maximum message size can result in unexpected value
> ----------------------------------------------------------------------------
>
> Key: QPID-8217
> URL: https://issues.apache.org/jira/browse/QPID-8217
> 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,
> qpid-java-broker-7.0.5, qpid-java-broker-7.0.6
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Priority: Trivial
> Fix For: qpid-java-broker-7.1.0, qpid-java-broker-7.0.7
>
>
> The maximum message size is evaluated as a minimum among context variable
> values for maximum message size on {{Port}} and {{Broker}} . Thus, when
> {{Broker}} maximum message size have value of {{10K}} and Port maximum
> message size have value of {{100M}}, the maximum message size would be
> {{10K}}. According to the rules for evaluation of context variables the
> {{Port}} context variable value should override the {{Broker}} one.
--
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
