{"action":"closed","issue":{"url":"https://api.github.com/repos/awslabs/amazon-sqs-java-messaging-lib/issues/28","repository_url":"https://api.github.com/repos/awslabs/amazon-sqs-java-messaging-lib","labels_url":"https://api.github.com/repos/awslabs/amazon-sqs-java-messaging-lib/issues/28/labels{/name}","comments_url":"https://api.github.com/repos/awslabs/amazon-sqs-java-messaging-lib/issues/28/comments","events_url":"https://api.github.com/repos/awslabs/amazon-sqs-java-messaging-lib/issues/28/events","html_url":"https://github.com/awslabs/amazon-sqs-java-messaging-lib/issues/28","id":184406202,"number":28,"title":"Why only one SQSSessionCallbackScheduler thread in a Session?","user":{"login":"sunhelly","id":10123703,"avatar_url":"https://avatars1.githubusercontent.com/u/10123703?v=3","gravatar_id":"","url":"https://api.github.com/users/sunhelly","html_url":"https://github.com/sunhelly","followers_url":"https://api.github.com/users/sunhelly/followers","following_url":"https://api.github.com/users/sunhelly/following{/other_user}","gists_url":"https://api.github.com/users/sunhelly/gists{/gist_id}","starred_url":"https://api.github.com/users/sunhelly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sunhelly/subscriptions","organizations_url":"https://api.github.com/users/sunhelly/orgs","repos_url":"https://api.github.com/users/sunhelly/repos","events_url":"https://api.github.com/users/sunhelly/events{/privacy}","received_events_url":"https://api.github.com/users/sunhelly/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-10-21T06:05:01Z","updated_at":"2017-04-25T17:12:02Z","closed_at":"2017-04-25T17:12:02Z","body":"We can use multi-consumers in a Session, but only one SQSSessionCallbackScheduler.\nWhy not callback and ack in the prefetch thread?\n"}}
{"actor":{"display_login":"kuba-aws"}}