EMS server accepts new messages, even though the pending messages exceed the maxbytes or maxmsgs limit.
Article ID: KB0094125
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
The property maxbytes or maxmsgs will not be always accurate. The messages that are delivered to the consumer for the first time are *not* counted when the server determines if the maxbytes or maxmsgs is exceeded. Note: if the messages were redelivered to the consumer for any reason (rollback or recover a session, close and create a consumer ) are counted. So that if messages are being consumed for instance, the count will not be accurate. To enforce the property maxbytes/maxmsgs, you need to avoid slow consumers and set a smaller prefetch value.
The property maxbytes or maxmsgs will not be always accurate. The messages that are delivered to the consumer for the first time are *not* counted when the server determines if the maxbytes or maxmsgs is exceeded. Note: if the messages were redelivered to the consumer for any reason (rollback or recover a session, close and create a consumer ) are counted. So that if messages are being consumed for instance, the count will not be accurate. To enforce the property maxbytes/maxmsgs, you need to avoid slow consumers and set a smaller prefetch value.
Issue/Introduction
EMS server accepts new messages, even though the pending messages exceed the maxbytes or maxmsgs limit.
Feedback
Yes
No
Powered by
