CODEWITHSUNDEEP
wso2wso2-esbwso2-api-manager
kkodr
kkodr

Reputation: 31

WSO2 Micro Integrator - Message Processors are Stuck After Do Server Stop and Start

I am running WSO2 MI 4.1 in a cluster with two nodes. After I re-enable all message forwarding processors in the Dashboard that are forwarding messages from RabbitMQs message store to an endpoint, each queue says it is running. When I stop the server on one node wait for a short period of time and then start the same node back up and then repeat this on the second node, the message processors look enabled and all have an emabled state. If I go to RabbitMQ, some of the queues are idle. If I try to send a message to these queues the message just sits there in the queue. If I stop and start the message processor for the queue then the queue starts processing messages. This behavior happens with empty queues and queues that have messages in them. Is this a bug or is there a better way to do a system restart?

Upvotes: 0

Views: 289

Answers (1)

kkodr
kkodr

Reputation: 31

Removing the _meta_MSMP* files in the _system/governance/repository/components/org.wso2.carbon.tasks/definitions/-1234/ESB_TASK/folder resolved this issue.

Upvotes: 0

Related Questions