Hello All Working on $(subject)
In the current scenario, the Message Processor deactivates after processing the Poison Message multiple times. The Poison message cannot be viewed or popped from the queue. The queue waits on the Message Processor for an acknowledgment to drop the message, however in this situation, the ack it is not sent. [image: PoisonMessageScenario.png] In the proposed solution, in case the Poison message scenario occurs, the Message Processor will be deactivated and the specific poison message can be viewed in the Manage Message Processor page of the Integrator Profile. The Poison message can then be popped from the Queue by sending an ack upon pressing a button at the Message Processor Page. -- Mohamed Aquib Zulfikar Associate Software Engineer | WSO2 Email : aq...@wso2.com Mobile : +94777182810 <http://wso2.com/signature>
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
