{"action":"created","issue":{"url":"https://api.github.com/repos/wso2/product-ei/issues/2740","repository_url":"https://api.github.com/repos/wso2/product-ei","labels_url":"https://api.github.com/repos/wso2/product-ei/issues/2740/labels{/name}","comments_url":"https://api.github.com/repos/wso2/product-ei/issues/2740/comments","events_url":"https://api.github.com/repos/wso2/product-ei/issues/2740/events","html_url":"https://github.com/wso2/product-ei/issues/2740","id":369389444,"node_id":"MDU6SXNzdWUzNjkzODk0NDQ=","number":2740,"title":"Improve message processor poison message handling","user":{"login":"Asitha","id":919462,"node_id":"MDQ6VXNlcjkxOTQ2Mg==","avatar_url":"https://avatars3.githubusercontent.com/u/919462?v=4","gravatar_id":"","url":"https://api.github.com/users/Asitha","html_url":"https://github.com/Asitha","followers_url":"https://api.github.com/users/Asitha/followers","following_url":"https://api.github.com/users/Asitha/following{/other_user}","gists_url":"https://api.github.com/users/Asitha/gists{/gist_id}","starred_url":"https://api.github.com/users/Asitha/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Asitha/subscriptions","organizations_url":"https://api.github.com/users/Asitha/orgs","repos_url":"https://api.github.com/users/Asitha/repos","events_url":"https://api.github.com/users/Asitha/events{/privacy}","received_events_url":"https://api.github.com/users/Asitha/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-10-12T03:52:30Z","updated_at":"2018-11-28T03:20:05Z","closed_at":null,"author_association":"MEMBER","body":"**Description:**\r\n<!-- Give a brief description of the issue -->\r\n\r\nWhen a poison message is processed by the message processor it will keep on retrying the backend with the same message. This stops the whole message processing flow when a poison message is reached.\r\n\r\nNeed to come up with a new design to properly handle this scenario. \r\n\r\nOne design consideration is, It can be difficult to distinguish between a backend outage or a poison message for the backend.\r\n\r\nAffected versions:\r\nESB 4.9.0, ESB 5.0.0, EI 6.x.x\r\n"},"comment":{"url":"https://api.github.com/repos/wso2/product-ei/issues/comments/442304873","html_url":"https://github.com/wso2/product-ei/issues/2740#issuecomment-442304873","issue_url":"https://api.github.com/repos/wso2/product-ei/issues/2740","id":442304873,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MjMwNDg3Mw==","user":{"login":"Ibaqu","id":43578935,"node_id":"MDQ6VXNlcjQzNTc4OTM1","avatar_url":"https://avatars3.githubusercontent.com/u/43578935?v=4","gravatar_id":"","url":"https://api.github.com/users/Ibaqu","html_url":"https://github.com/Ibaqu","followers_url":"https://api.github.com/users/Ibaqu/followers","following_url":"https://api.github.com/users/Ibaqu/following{/other_user}","gists_url":"https://api.github.com/users/Ibaqu/gists{/gist_id}","starred_url":"https://api.github.com/users/Ibaqu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Ibaqu/subscriptions","organizations_url":"https://api.github.com/users/Ibaqu/orgs","repos_url":"https://api.github.com/users/Ibaqu/repos","events_url":"https://api.github.com/users/Ibaqu/events{/privacy}","received_events_url":"https://api.github.com/users/Ibaqu/received_events","type":"User","site_admin":false},"created_at":"2018-11-28T03:20:05Z","updated_at":"2018-11-28T03:20:05Z","author_association":"NONE","body":"The MessageContext now successfully displays on the front end on a separate page. Im currently working on the button to Pop the message from the queue"}}
{"actor":{"display_login":"Ibaqu"}}