qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Giusti (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3417) Support for timestamping messages on arrival at the broker.
Date Wed, 05 Oct 2011 13:36:35 GMT

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

Ken Giusti commented on QPID-3417:

Alan - good point.  I'm guilty of putting the cart before the horse here - I'm assuming calling
AbsTime::now() is going to be a bigger performance hit that using a less frequently updated
timestamp (and the read-locks that would be necessary to keep it consistent).

Since this feature is intended for use as a debug aid - and an performance impact would be
the cost - we're probably best off implementing your simpler solution and qualifying the performance
hit.  I'll give that a try.   Thanks.
> Support for timestamping messages on arrival at the broker.
> -----------------------------------------------------------
>                 Key: QPID-3417
>                 URL: https://issues.apache.org/jira/browse/QPID-3417
>             Project: Qpid
>          Issue Type: New Feature
>          Components: C++ Broker
>    Affects Versions: 0.13
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Minor
>             Fix For: 0.14
> AMQP 0.10 defines an optional message delivery property of timestamp:
> name: timestamp
> type: datetime
> description: message timestamp
> (optional)  The timestamp is set by the broker on arrival of the message.
> I'd like to make use of this timestamp for a proposed debugging feature for message groups.
 See the message groups UI proposal in https://issues.apache.org/jira/browse/QPID-3346 for
details of its use.
> I think it would more useful to introduce a generic message timestamp capability based
on the AMQP 0.10 delivery property, rather than integrate something limited only to message
> Functional Model:
> The broker would support the configuration of a "timestamp interval".  This interval
would be expressed in millisecond units, and would represent the granularity of the message
timestamp.  The default setting of this interval would be zero - which would be interpreted
as disabled.  When enabled (non-zero) the broker would maintain a time-of-day time stamp.
 This time stamp would be updated (resync'ed to the current time-of-day) periodically based
on the configured "timestamp interval".
> When enabled, each message arriving at the broker will have the "timestamp" delivery
property set to the current value of the broker's time stamp.
> This feature will need to be able to be turned on and off on demand, without restarting
the broker.  Therefore new QMF methods would be added to the broker's QMF object to support
run-time configuration:
>    method: getMessageTimestamp - returns the configured timestamp value for the broker
in milliseconds.
>    method: setMessageTimestamp - sets the broker's timestamp value (expressed in milliseconds).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message