JMS Queue Unevenly Consumed.
Last updated on SEPTEMBER 12, 2016
Applies to:Oracle Communications Converged Application Server - Version 4.0.0 and later
Information in this document applies to any platform.
Messages are time stamped before being put into JMS queue. Time stamp is then read and compared with current time when the message is consumed. This shows how long every messages has been in the queue before being processed. The queue has multiple consumers and performance preference is set to #Do Not Batch Messages#.
Expectations are that the messages in the queue should be consumed in the same order as they entered the queue but we can see that this is not always the case.
In the provided logs there is an example where messages appear to be consumed in an orderly fashion after 1-2 ms on the queue. Last message in the log has however been in the queue 12165 ms before being processed.
(Find "handleSignalFromNRG()The message has been in the CDGQueue for")
There has obviously been consumers available judging from the previously consumed messaged, so how to make sure this message has been processed earlier?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms