[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kennedy updated QPID-2835:
-
Status: Ready To Review (was: In Progress)
Implement connections (CON) operational logging on
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kennedy updated QPID-2835:
-
Attachment: 0001-QPID-2835-Implement-CON-Operational-Logging-on-0-10.patch
Patch from SorinS
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: qpid-2835.patch
Implement connections (CON) operational logging on 0-10
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: (was: qpid-2835.patch)
Implement connections (CON) operational logging on 0-10
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: (was: qpid-2835.patch)
Implement connections (CON) operational logging on 0-10
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: qpid-2835.patch
Implement connections (CON) operational logging on 0-10
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: (was: qpid-2858_1.patch)
Implement connections (CON) operational logging on 0-10
Hi Martin,
Thank you for commenting on this, appreciate your input as always. You
might have seen the email Andrew sent earlier, which outlined a
possible scenario to improve the logging framework - these are just
different options we are looking at in order to provide operational
logging on
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: (was: qpid-2835.patch)
Implement connections (CON) operational logging on 0-10
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: qpid-2835.patch
Modifed so that ConnectionMessages.CLOSE() is fired by CurrentActor.get()
Hi.
The way I see this is that the logging is currently too fragmented
and still manages to be quite tightly coupled to the model objects,
via the LogSubjects. Unless we had a generic subject that could
produce an identifier for anything it was presented with, this will
always be the
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: qpid-2835.patch
Implement connections (CON) operational logging on 0-10
On 2 September 2010 10:53, Sorin S. ssu...@gmail.com wrote:
Hi Martin,
Thanks very much for your feedback.
The main problem I had with the current framework is the fact that the
LogSubject objects seem to have knowledge about broker hierarchy (eg
the SubscriptionLogSubject instantiates a
Hi Martin,
Thanks very much for your feedback.
The main problem I had with the current framework is the fact that the
LogSubject objects seem to have knowledge about broker hierarchy (eg
the SubscriptionLogSubject instantiates a QueueLogSubject, also the
ConnectionLogSubject takes a
Hi Sorin,
I've been watching your changes wrt the Operational Logging apologies
for not replying to your thread over the weekend but I wasn't at a
computer.
I think the addition of the toLogString() is the wrong approach here.
The responsibility for the logging format should not lie with the
[
https://issues.apache.org/jira/browse/QPID-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2835:
--
Attachment: qpid-2835.patch
Implement connections (CON) operational logging on 0-10
16 matches
Mail list logo