[
https://issues.apache.org/jira/browse/QPID-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924863#comment-13924863
]
Fraser Adams commented on QPID-5611:
------------------------------------
It mostly seems back to how it was now, though I'm still seeing:
[Broker] MNG-1001 : QMF2 Management Startup
[con:0(/127.0.0.1:46829)] CON-1001 : Open
[con:0(/127.0.0.1:46829)] CON-1001 : Open : Protocol Version : 0-10
[Broker] MNG-1004 : QMF2 Management Ready
Now the QMF2 plugin is indeed establishing its own AMQP connection and the
message shown isn't intrusive, but it's still different to what I was seeing
before (I was previously only seeing the [Broker] messages before you started
tweaking the logging).
It won't kill me, but I thought you'd at least like to be aware that there was
still a difference.
> [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]
