Affects Version/s: 22.214.171.124-fuse
Fix Version/s: 126.96.36.199-fuse
Similar Issues:Show 10 results
MB-632 Support STOMP+NIO in FUSE Message Broker release. MB-709 Usage manager exceeds 100% when sending messages from multiple producers and producerFlowControl is turned off MB-343 broker looses messages using multiple consumers accessing persistent messages from a queue MB-1188 Fuse Message Broker's REST API support for application/json as content type MB-655 Multiple duplicate messages and extra durable subscription created after a broker in a network of brokers is restarted. MB-295 Broker support for dynamic cleanup of message reference store and durable subscriber indexes MB-317 Broker should only send persistent messages to persistent brokers in a network of brokers MB-988 Enhance HTTP transport connector to support message Compression MB-611 Message can be consumed twice over network of brokers MB-535 Consumer does not receive all messages if producer on another networked broker OOMs
We are trying to achieve the following:
Network of brokers with:
- Two or more 'sending' brokers, each with one or more message producer attached.
- Two or more 'receiving' brokers, each with one or more message consumers attached.
We have sequences of messages that might be sent by different 'sending brokers', but would like them to always be received by the same 'receiving broker'. We've set it up so the producers will assign the same message group to all the messages within a sequence.
Currently the message group feature requires that all messages originate from the same broker instance. This is an enhancement to support messages(w/message group) originating from any broker in the network.