[
https://issues.apache.org/jira/browse/ARTEMIS-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466475#comment-17466475
]
Erwin Dondorp edited comment on ARTEMIS-3592 at 12/29/21, 2:43 PM:
-------------------------------------------------------------------
[~jbertram]
I just completed a PR that 'solves' this, see ARTEMIS-3621.
With certain client software, the timestamp part of the received message is 0.
In my case this was happening with a client that was QPID-proton (python) based
and {{msg.creation_time}} was not set after creating the message with {{{}msg =
proton.Message(...){}}}.
was (Author: erwindon):
[~jbertram]
I just completed a PR that 'solves' this, see ARTEMIS-3621.
With certain client software, the timestamp part of the received message is 0.
In my case this was happening with a client that was QPID-proton (python) based
and `msg.creation_time` was not set after creating the message with `msg =
proton.Message(...)`.
> Messages timestamp is always equal to "epoch" in console
> --------------------------------------------------------
>
> Key: ARTEMIS-3592
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3592
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.19.0
> Reporter: Giuseppe Lio
> Priority: Major
> Attachments: browse.png, image-2021-11-29-17-27-18-155.png
>
>
> Please see attached screenshot
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
