[
https://issues.apache.org/jira/browse/QPID-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589769#comment-14589769
]
ASF subversion and git services commented on QPID-6591:
-------------------------------------------------------
Commit 1686011 from [email protected] in branch 'java/trunk'
[ https://svn.apache.org/r1686011 ]
QPID-6591: Change the default value for virtual host logger file location and
address code review comments from Rob Godfrey
> [Java Broker] Add ability to generate a virtualhost specific log
> ----------------------------------------------------------------
>
> Key: QPID-6591
> URL: https://issues.apache.org/jira/browse/QPID-6591
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: 6.0 [Java]
>
>
> We need the ability to write a separate log file for a virtualhost which
> contains just the log events for related to the virtualhost.
> * Add a VirtualHostLogger model object (like BrokerLogger) which will be a
> child of Virtualhost. (As such it will be automatically propagated around a
> HA group)
> * Add a VirtualHostFileLogger impl (like BrokerFileLogger impl)
> * Add a VirtualHostNameAndLevelFilter (like BrokerNameAndLevelFilter except
> that it additionally filters for events whose subject has a
> ConnectionPrincipal with a matching virtualhost).
> * Like the Broker counterparts, these Objects must be
> addable/removable/configurable dynamically.
> * ACL rule UPDATE VIRTUALHOST should be applied to these operations.
> * Include adding support for virtualhostloggers and virtualhostfilters to the
> REST API
> * As VH can be stopped and started (or a HA node become active), the
> implementation must be prepared to dynammically add and remove itself at run
> time.
> * Make sure housekeeping/queue running threads have appropriate Subject.
> (Maybe add concept of a VirtualhostPrinicpal).
> Owing to limitations in the model framework code VirtualHostLogger and
> BrokerLogger must be distinct, but there is nothing stopping their
> implementations from sharing a implementation from a non-model object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
