qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fraser Adams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-5611) [Java Broker] Simplify logging mechanism for event logging (remove LogActors)
Date Sat, 08 Mar 2014 17:00:47 GMT

    [ https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924924#comment-13924924

Fraser Adams commented on QPID-5611:

Yeah I am "bringing up your connection while the broker is still initialising and before it
is fully "ready" - I create the QmfAgent in the Plugin start() method which is called from
setState() when desiredState == State.ACTIVE

To be honest I don't especially mind the two connection open messages I just flagged it up
because it was a change.

> [Java Broker] Simplify logging mechanism for event logging (remove LogActors)
> -----------------------------------------------------------------------------
>                 Key: QPID-5611
>                 URL: https://issues.apache.org/jira/browse/QPID-5611
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Rob Godfrey
>            Assignee: Rob Godfrey
> The operational logging mechanism within the Java Broker uses a complex set of "actors",
"subjects" and "messages".
> The notion of "actor" is supposed to reflect the entity on whose behalf the actin being
logged is being performed.  Rather than creating a new concept for this, we can utilise the
fact that the current "subject" is available from the runtime context, and based on the principals
available we can generate a log string appropriate for the context.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message