Details
-
Task
-
Resolution: Done
-
Minor
-
JBoss A-MQ 6.0
-
None
-
Documentation (Ref Guide, User Guide, etc.)
Description
Red Hat JBoss A-MQ - Configuring Broker Persistence Guide at
https://access.redhat.com/site/documentation/en-US/JBoss_A-MQ/6.0.EA/html/Configuring_Broker_Persistence/files/FuseMBPersistCursorsTypes.html
says
As shown in Figure 6, store-based cursors address the fast consumer case by skipping the message cursor. When a message consumer is keeping pace with the message producers, persistent messages are written to the message store and moved directly into a dispatch queue for the consumer.
Basically the statement is inaccurate since fast consumers are dealt with the same for both StoreCursor and VMCursor. It does not skip StoreCursor/Pending Cursor as the messages will be held in memory and dispatch from the memory. In fast consumers situation, StoreCursor will behave exactly the same as VMCursor but with a few differences that VMCursor will be a snapshot of entire persistent message store in memory as it needs to hold all messages in memory while StoreCursor will be a mapping of only a fraction of persistent message store in memory since it can only hold limited messages in memory.
Fuse ESB 7.1 documentation has the same error at:
https://access.redhat.com/site/documentation/en-US/Fuse_MQ_Enterprise/7.1/html/Configuring_Broker_Persistence/files/FuseMBPersistCursorsTypes.html
Attachments
Issue Links
- relates to
-
AMQ-5341 Loading...