Consumers going down for Oracle advanced queue
When the consumers go down due to some fatal error, no xml is dequed related to that consumer. But if we ignore the fatal error and consumer does not g开发者_C百科o down then all the messages related to that consumer will be dequed.
But the message on which the fatal error came will not get dequed and it will be acting as a loss of data or information.
How can the loss of data be avoided?
Use a WHEN OTHERS THEN wrapper exception handler at the highest level of your consumer, and if you catch a fatal error then write enough information to an 'error' queue that gets monitored by someone (support team, administrator and so on) that is sufficient to identify the message that caused the fatal so it can be 're-processed' or handled somehow.
精彩评论