You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2016/01/11 18:21:40 UTC
[jira] [Resolved] (QPID-6973) [Java Broker] Expose message
durability information as part of DEBUG/TRACE logs
[ https://issues.apache.org/jira/browse/QPID-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-6973.
------------------------------
Resolution: Invalid
It is actually possibly to calculate transient and persistent messages on queues by finding JMSDeliveryMode property logged as part of MessageHeader. Closing JIRA as invalid
> [Java Broker] Expose message durability information as part of DEBUG/TRACE logs
> -------------------------------------------------------------------------------
>
> Key: QPID-6973
> URL: https://issues.apache.org/jira/browse/QPID-6973
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Alex Rudyy
>
> On investigation Qpid Broker related problems with provided qpid broker logs it would be useful to know the durability of published messages. At the moment our logs do not provide such details, as result, it is impossible to identify from the logs the number of enqueued transient or persistent messages on the queues on any particular time. Having such information would be useful in investigations of issue related to durability or persistent operations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org