When browsing messages on a queue using JMS Test Client, the message property JMSExpiration shows a time according to the system time of the client. If the client system time is wrong, the JMSExpiration time makes no sense on the server when browsing the messages on a queue - it will be the wrong system time + the value of TimeToLive. Am I missing something here, or is this expected behavior where the only solution is to synchronize the system time on all clients?
I am going to answer this myself:
JMSTimestamp is the client time of sending
JMSExpiration is the time of the server when the message came in + the timeToLive value specified by the client
Comparing the two values makes little sense, as it is the system time of the server that should compared to the value of JMSExpiration.