Monitoring JMS Messages Gives Wrong Message ID And Timestamp on WLS

(Doc ID 1339216.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.3 to 10.3.3
Information in this document applies to any platform.


The timestamp and Message ID of messages change once the WebLogic Server Administration Console is refreshed, immediately after a message is sent. This behavior persists every time the JMS Resource Monitoring Show Messages Tab is refreshed. However, if the console screen is idle for a few minutes and then refresh the same, the correct timestamp as well as ID are displayed.

Steps to reproduce:

  1. Create a JMS Module.
  2. Create a connection factory.
  3. Create a Distributed Queue.
  4. Deploy a sample application or run a standalone client.
  5. Post a Distributed Queue message.
  6. Wait 30 sec. and post another.
  7. Monitor the queue.
  8. Show messages.
  9. Notice the messages have different time stamps and IDs.
  10. Refresh the page.
  11. Notice the messages are now showing the same time stamps and IDs.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms