Hi All, With regards to the issue [1], it was observed that its due to the client not sending the rejection ack during a high load
MB caches the message ids in-memory before sending to the client in order to track the delivery status. It will only remove the stored cache when the subscriber acknowledges. The issue was produced at a situation where the subscriber does not send any acknowledgment when the load became high. As a result MB will infinitely await to the response from the client without re attempting to send the message. 1) The client needs to be fixed to acknowledge at high loads 2) Also what if there will be situations where the client acknowledgment is dropped due to a networking issue ? in that case IMO we need to set an expiry to the message so that it would timeout after a certain period of time. WDYT ? [1] https://wso2.org/jira/browse/MB-586 Thanks, Pamod -- *Pamod Sylvester * *Senior Software Engineer * Integration Technologies Team, WSO2 Inc.; http://wso2.com email: [email protected] cell: +94 77 7779495
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
