Last updated on DECEMBER 22, 2016
Applies to:Oracle ATG Web Commerce - Version 2006.3 and later
Information in this document applies to any platform.
***Checked for relevance on 10-Apr-2013***
This behavior only becomes apparent when there is a large number of unhandled JMS messages in the database. This can occur if the ATG servers that process those messages are offline for a period of time or the rate of incoming JMS messages is faster than the rate at which they can be processed.
Uneven distribution of SQL JMS messages to subscribers
Processing of global ScenarioManager events is handled primarily by a single server
Backlog of JMS messages when servers are under high load
JMS message processing is not concurrent and appears to be synchronous
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