Hello We observed a high CPU usage coming from the broker & dispatch-router while the system"was "idle", meaning no messages were coming in / out. It seems that when some messages are pending (i.e. not yet consumed) in a queue of type multi-cast, the dispatch-routers & brokers are excessively sending messages between themselves, leading to a high CPU usage. We did not observed that with a queue of type balanced.
Looking at the dispatch-router's stack traces, all running threads were processing incoming messages. Looking at the dispatch-router's strace, it was constantly receiving & sending messages to the brokers Looking at the broker's dashboard, the "outbound message rate" on the default virtualhost was going nuts: [cid:[email protected]] The connection 10.25.3.129:45679 is bound to the dispatch-router. Looking at the dispatch-router's qdstat, "rel" is increasing dramatically: type dir conn id id peer class addr phs cap pri undel unsett del presett psdrop acc rej rel mod admin oper ======================================================================================================================================================================================================================================== ... endpoint in 3 133 mobile v1.portfolio-management.full-revaluation.approval-status-notifications-subscription 1 250 0 0 0 286 0 0 286 0 1180920296 0 enabled up endpoint in 4 135 mobile v1.portfolio-management.full-revaluation.approval-status-notifications-subscription 1 250 0 0 0 283 0 0 283 0 1175483817 0 enabled up ... Is that expected? Thanks, Olivier ******************************* This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorized to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.
