[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924906#comment-13924906
]
Rob Godfrey commented on QPID-5611:
-----------------------------------
OK... well, at this point I'm just going to consider it a change in behaviour
then... presumably you are bringing up your connection while the broker is
still initialising and before it is fully "ready" (or maybe you have a listener
on the broker state and trigger connection establishment on that?... it looks
like the code to switch to normal logging happens immediately after changing
the state of the broker... but state change listeners probably get fired before
that state change returns).
> [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
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
