[
https://issues.apache.org/jira/browse/ARTEMIS-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram resolved ARTEMIS-4139.
-------------------------------------
Assignee: Justin Bertram
Resolution: Invalid
This issue is technically moot since it was reported against the old web
console, but I've linked 2 related issues.
> JMX field creationTime is not consistently formatted
> ----------------------------------------------------
>
> Key: ARTEMIS-4139
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4139
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMX
> Affects Versions: 2.27.1
> Reporter: Erwin Dondorp
> Assignee: Justin Bertram
> Priority: Minor
>
> When collecting JMX data, several functions return field {{creationTime}} in
> their results.
> I think this happens for
> listConsumers/listProducers/listConnections/listSessions (non-exact spelling
> as there are a few variations: list vs listAll).
> For listConsumer/listConnections/listSessions, a formatted datetime is used,
> e.g. {{Fri Jan 20 01:06:19 UTC 2023}}
> But for listProducers, the underlying milliseconds value is returned, e.g.
> {{1674176779483}}
> I think this should be consistent.
> My first reaction was that the value for listProducers is the exception, and
> thus wrong. But the documentation in ActiveMQServerControl.java shows this as
> a milliseconds value in its examples for all these calls. also other
> timestamp fields are in milliseconds, e.g. firstmessagetimestamp
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
