You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/03/01 16:24:50 UTC
[jira] Updated: (QPID-367) maximumMessageSize in AMQQueue should be
marked as configurable
[ https://issues.apache.org/jira/browse/QPID-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-367:
----------------------------------
Description:
Currently the _maximumMessageSize in AMQQueue is not marked with the @Configured annotation - it should be with default value 0
Also, virtualhosts.xml configuration for the following alert types is incorrect in Qpid distributions (trunnk/branches). The tags for <maximumMessageCount> and <maximumQueueDepth> should be child elements of the specific virtual host tag i.e. <test> rather than <virtualhost>.
was:Currently the _maximumMessageSize in AMQQueue is not marked with the @Configured annotation - it should be with default value 0
> maximumMessageSize in AMQQueue should be marked as configurable
> ---------------------------------------------------------------
>
> Key: QPID-367
> URL: https://issues.apache.org/jira/browse/QPID-367
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Rob Godfrey
> Assigned To: Bhupendra Bhardwaj
>
> Currently the _maximumMessageSize in AMQQueue is not marked with the @Configured annotation - it should be with default value 0
> Also, virtualhosts.xml configuration for the following alert types is incorrect in Qpid distributions (trunnk/branches). The tags for <maximumMessageCount> and <maximumQueueDepth> should be child elements of the specific virtual host tag i.e. <test> rather than <virtualhost>.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.