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/12/29 16:01:02 UTC
[jira] [Updated] (QPID-7419) Consistently log changes (or failure
to change) to the Broker model's state
[ https://issues.apache.org/jira/browse/QPID-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7419:
-----------------------------
Fix Version/s: (was: qpid-java-6.2)
Future
> Consistently log changes (or failure to change) to the Broker model's state
> ---------------------------------------------------------------------------
>
> Key: QPID-7419
> URL: https://issues.apache.org/jira/browse/QPID-7419
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: Future
>
>
> See discussion: http://qpid.2158936.n2.nabble.com/Java-Broker-6-0-4-Rest-API-logs-are-a-bit-tricky-td7650396.html
> Currently the Broker writes operational log messages in response to *most* successful changes made to Broker's model state, for example QUE-1001 for queue creation.
> The Broker should consistently log, in a manner _targeted to the end-user_, all:
> * all changes successfully made to Broker's model state (e.g add a queue object, perform operation {{Queue#clearQueue}}).
> * changes attempted but failed (e..g. add a queue but the alternativeExchange does not exist, Queue#moveMessage where the target queue does not exist.).
--
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