Under what situations would one see message memory usage be higher than the max_msg_memory limit?
Article ID: KB0091325
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
There are sever possible situations that you may notice this symptom.
1). You manually set the max_msg_memory to a lower value.
2). You have offline durables for system monitor topics, or you have a slow consumer for system monitor topics. We do not swap out monitor messages and we do not block generating system monitor messages.
3). You are using a queue browser. When the queue browser is created, if messages were swapped out, the server needs to swap them back in. Suppose the MMU is close to max_msg_memory. When the queue browser is created, messages are swapped in (when needed) though the messages will automatically be swapped out as needed. But it is still possible that the MMU can go above the max_msg_memory limit.
4). You have many topic durable subscribers/queue receivers at the same time, so that when they consume messages, tibemsd needs to load and swap in the messages from each subscribers. It consumes "Message
Memory Usage", therefore, tibemsd size may increase. "Message Memory usage" may increase and "Message Memory usage" can go above the limit, as we do not block subscribers.
5). You are using selectors with your consumer. When a new consumer is created, tibemsd may need to swap in the messages from the db files.
6). An application is sending messages to the EMS server and has not committed the transactions.
There are sever possible situations that you may notice this symptom.
1). You manually set the max_msg_memory to a lower value.
2). You have offline durables for system monitor topics, or you have a slow consumer for system monitor topics. We do not swap out monitor messages and we do not block generating system monitor messages.
3). You are using a queue browser. When the queue browser is created, if messages were swapped out, the server needs to swap them back in. Suppose the MMU is close to max_msg_memory. When the queue browser is created, messages are swapped in (when needed) though the messages will automatically be swapped out as needed. But it is still possible that the MMU can go above the max_msg_memory limit.
4). You have many topic durable subscribers/queue receivers at the same time, so that when they consume messages, tibemsd needs to load and swap in the messages from each subscribers. It consumes "Message
Memory Usage", therefore, tibemsd size may increase. "Message Memory usage" may increase and "Message Memory usage" can go above the limit, as we do not block subscribers.
5). You are using selectors with your consumer. When a new consumer is created, tibemsd may need to swap in the messages from the db files.
6). An application is sending messages to the EMS server and has not committed the transactions.
Issue/Introduction
Under what situations would one see message memory usage be higher than the max_msg_memory limit?
Additional Information
KB 46508
Feedback
Yes
No
Powered by
