Hi @Abu,
DMQ always set to true
If your JMS apps use Solace’s JNDI provider to lookup its connection factory then you can set DMQ eligible to true, as well as other properties (such as retries, timeouts, etc.) in one place.
JMSTimestamp
I believe this already automatically gets set if it isn’t touched? Are you seeing otherwise (i might be wrong here)
JMSMessageID
Again, I believe the Solace API sets a default (I am seeing something that looks like:ID:fe80:0:0:0:0:0:0:1%lo0f5d517e4ac6cb730:70) but your applications would be on your own to configure it if you want something different. A lot of times applications will set this ID to an identifier that has some context to the event/processing that is done in the app and that ID will also be included in the logs upstream/downstream to allow for log correlation. If you want it to be the same format across many apps then one option might be to have your apps use a common send method that is in a shared library. This would also allow you to set other properties in one place if desired (this pattern could also be used to set DMQ eligible if you don’t do it on the connection factory).
Hope that helps!