AWS AmazonSNSClient instance fails to perform any work
I have web services running on Elastic Beanstalk. I am trying to add SNS to it for mobile push notification. I have successfully tested it from AWS console.
I instantiated AmazonSNSClient and it is not null. However any method call such as listEndpointsByPlatformApplication, createPlatformEndpoint, publish etc. appears to be stuck. These calls never returns and does not throwing any exception.
I have given full SNS permission to the service role.
BasicAWSCredentials creds = new BasicAWSCredentials(AWS_ACCESS_KEY_ID, AWS_SECRET_KEY);
AmazonSNSClient snsClient = new AmazonSNSClient(creds).withRegion(Region.getRegion(Regions.US_EAST_1));
Any help is greatly appreciated.
amazon-web-services firebase-cloud-messaging publish android-push-notification
add a comment |
I have web services running on Elastic Beanstalk. I am trying to add SNS to it for mobile push notification. I have successfully tested it from AWS console.
I instantiated AmazonSNSClient and it is not null. However any method call such as listEndpointsByPlatformApplication, createPlatformEndpoint, publish etc. appears to be stuck. These calls never returns and does not throwing any exception.
I have given full SNS permission to the service role.
BasicAWSCredentials creds = new BasicAWSCredentials(AWS_ACCESS_KEY_ID, AWS_SECRET_KEY);
AmazonSNSClient snsClient = new AmazonSNSClient(creds).withRegion(Region.getRegion(Regions.US_EAST_1));
Any help is greatly appreciated.
amazon-web-services firebase-cloud-messaging publish android-push-notification
add a comment |
I have web services running on Elastic Beanstalk. I am trying to add SNS to it for mobile push notification. I have successfully tested it from AWS console.
I instantiated AmazonSNSClient and it is not null. However any method call such as listEndpointsByPlatformApplication, createPlatformEndpoint, publish etc. appears to be stuck. These calls never returns and does not throwing any exception.
I have given full SNS permission to the service role.
BasicAWSCredentials creds = new BasicAWSCredentials(AWS_ACCESS_KEY_ID, AWS_SECRET_KEY);
AmazonSNSClient snsClient = new AmazonSNSClient(creds).withRegion(Region.getRegion(Regions.US_EAST_1));
Any help is greatly appreciated.
amazon-web-services firebase-cloud-messaging publish android-push-notification
I have web services running on Elastic Beanstalk. I am trying to add SNS to it for mobile push notification. I have successfully tested it from AWS console.
I instantiated AmazonSNSClient and it is not null. However any method call such as listEndpointsByPlatformApplication, createPlatformEndpoint, publish etc. appears to be stuck. These calls never returns and does not throwing any exception.
I have given full SNS permission to the service role.
BasicAWSCredentials creds = new BasicAWSCredentials(AWS_ACCESS_KEY_ID, AWS_SECRET_KEY);
AmazonSNSClient snsClient = new AmazonSNSClient(creds).withRegion(Region.getRegion(Regions.US_EAST_1));
Any help is greatly appreciated.
amazon-web-services firebase-cloud-messaging publish android-push-notification
amazon-web-services firebase-cloud-messaging publish android-push-notification
edited Nov 22 '18 at 9:02
Roy
asked Nov 22 '18 at 8:05
RoyRoy
418812
418812
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The weird stuck like behavior was caused by AWS core's version mismatch in eclipse pom file. Resolved the issue by making sure compatible AWS libraries.
Hope this helps someone in future.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426342%2faws-amazonsnsclient-instance-fails-to-perform-any-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The weird stuck like behavior was caused by AWS core's version mismatch in eclipse pom file. Resolved the issue by making sure compatible AWS libraries.
Hope this helps someone in future.
add a comment |
The weird stuck like behavior was caused by AWS core's version mismatch in eclipse pom file. Resolved the issue by making sure compatible AWS libraries.
Hope this helps someone in future.
add a comment |
The weird stuck like behavior was caused by AWS core's version mismatch in eclipse pom file. Resolved the issue by making sure compatible AWS libraries.
Hope this helps someone in future.
The weird stuck like behavior was caused by AWS core's version mismatch in eclipse pom file. Resolved the issue by making sure compatible AWS libraries.
Hope this helps someone in future.
answered Nov 22 '18 at 10:28
RoyRoy
418812
418812
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53426342%2faws-amazonsnsclient-instance-fails-to-perform-any-work%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown