We are attempting to use the amqp basic property "timestamp" via the
RabbitMQ java client (see code below) to record the point in time when
the message gets sent. However, we are finding that when a message is
pulled from the bus, the timestamp property of the retrieve message
has had its milliseconds component dropped. We are using rabbitmq
2.7.1 with erlang R15B. Is this a bug or by design? Other than using
our own headers, is there a better way to do this? We would love it
if Rabbit itself would provide this timestamp as it would eliminate
issues with client clocks not being in sync.

BasicProperties props = new BasicProperties.Builder()
.messageId(UUID.randomUUID().toString())
.correlationId(UUID.randomUUID().toString())
.type("test.event")
.replyTo("replyto_routingkey")
.timestamp(new Date(2930830427321L))
.headers(headers)
.build();

Thereafter do a basicPublish and basicGet() and compare sent and
received timestamps. They differ by 321 mills.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 3 | next ›
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedFeb 22, '12 at 8:04p
activeFeb 23, '12 at 11:15a
posts3
users2
websiterabbitmq.com
irc#rabbitmq

2 users in discussion

Marek Majkowski: 2 posts Ken Baltrinic: 1 post

People

Translate

site design / logo © 2022 Grokbase