Timestamps incorrectly encoded as milliseconds rather than seconds
------------------------------------------------------------------
Key: QPID-1551
URL: https://issues.apache.org/jira/browse/QPID-1551
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: M4
Reporter: Garrett Conaty
It appears that datetime/timestamp values are being encoded by the Qpid Java
client as the number of milliseconds (specifically a timestamp is
System.currentTimeMillis(), whereas from the AMQP Spec (pick 0-8 onwards)
"Time stamps are held in the 64-bit POSIX time_t format with an accuracy of one
second. By using 64 bits
we avoid future wraparound issues associated with 31-bit and 32-bit time_t
values."
Is this accurate or perhaps I"m missing something in the JMS layer that wants
it to be milliseconds rather than seconds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
