amazon-ses-quickstart getting multiple errors #597
Comments
|
@marcinczeczko could you have a look at that report? |
|
I'm on PTO atm, will take a look Aug.
czw., 16 lip 2020, 15:42 użytkownik Guillaume Smet <[email protected]>
napisał:
… @marcinczeczko <https://github.com/marcinczeczko> could you have a look
at that report?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#597 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAF4GZTPPM25NUSQNADQ53R337VHANCNFSM4N2H3XXQ>
.
|
|
Run docker run --rm --name local-ses 8012:4579 -e SERVICES=ses -e START_WEB=0 -d localstack/localstack:0.11.1 This is user error. You have to put -p in front of the port statement. The error message gives us a clue "Unable to find image..." I've got a ton of PRs coming that improves this experience by just using docker-compose files. (Feel free to use my fork edtbl76/quarkus-quickstarts) |
|
@gsmet could be closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem:
Quickstart is not working as described, receiving different errors, not possible to send mails locally
Expectations:
Follow quickstart guide and have working example
Steps to reproduce:
Environment:
openjdk 11.0.7 2020-04-14OpenJDK Runtime Environment GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02)OpenJDK 64-Bit Server VM GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02, mixed mode, sharing)Quarkus 1.5.0-final
Variant A:
docker run --rm --name local-ses 8012:4579 -e SERVICES=ses -e START_WEB=0 -d localstack/localstack:0.11.1Error: Unable to find image '8012:4579' locally
Variant B:
clone the ses-quickstart
Add to application.properties:
quarkus.ses.endpoint-override=http://localhost:8080quarkus.ses.aws.region=us-east-1quarkus.ses.aws.credentials.type=staticquarkus.ses.aws.credentials.static-provider.access-key-id=test-keyquarkus.ses.aws.credentials.static-provider.secret-access-key=test-secretAdd profile:
aws configure --profile localstack(Used data from above)
Run './mvnw clean quarkus:dev'
Results in:
2020-06-10 12:23:19,336 INFO [io.quarkus] (Quarkus Main Thread) amazon-ses-quickstart 1.0-SNAPSHOT on JVM (powered by Quarkus 1.5.0.Final) started in 1.331s. Listening on: http://0.0.0.0:8080 2020-06-10 12:23:19,338 INFO [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated. 2020-06-10 12:23:19,339 INFO [io.quarkus] (Quarkus Main Thread) Installed features: [amazon-ses, cdi, mutiny, resteasy, resteasy-jsonb, resteasy-mutiny]Verify email-identity:
aws ses verify-email-identity --email-address [email protected] --profile localstack --endpoint-url=http://localhost:8080Error:
Unable to parse response (no element found: line 1, column 0), invalid XML received. Further retries may succeed: b''Post Mail:
curl -XPOST -H"Content-type: application/json" http://localhost:8080/sync/email -d'{"from": "[email protected]", "to": "[email protected]", "subject": "Hello from Quarkus", "body": "Quarkus is awsome"}'Error:
<title>Internal Server Error - Error handling ffd53bd0-0bd2-4251-a2ce-6a2ffb1df01e-10, org.jboss.resteasy.spi.UnhandledException: software.amazon.awssdk.services.ses.model.SesException: null (Service: Ses, Status Code: 500, Request ID: null)</title> <style> html, body { margin: 0; padding: 0; font-family: 'Open Sans', Helvetica, Arial, sans-serif; font-size: 100%; font-weight: 100; line-height: 1.4; }`<!doctype html>
html {
overflow-y: scroll;
}
body {
background: #f9f9f9;
}
.container {
width: 80%;
margin: 0 auto;
}
.content {
padding: 1em 0 1em 0;
}
header, .component-name {
background-color: #ad1c1c;
}
ul {
line-height: 1.5rem;
margin: 0.25em 0 0.25em 0;
}
.exception-message {
background: #be2828;
}
h1, h2 {
margin: 0;
padding: 0;
}
h1 {
font-size: 2rem;
color: #fff;
line-height: 3.75rem;
font-weight: 700;
padding: 0.4rem 0rem 0.4rem 0rem;
}
h2 {
font-size: 1.2rem;
color: rgba(255, 255, 255, 0.85);
line-height: 2.5rem;
font-weight: 400;
padding: 0.4rem 0rem 0.4rem 0rem;
}
.intro { font-size: 1.2rem;
font-weight: 400;
margin: 0.25em 0 1em 0;
}
h3 {
font-size: 1.2rem;
line-height: 2.5rem;
font-weight: 400;
color: #555;
margin: 0.25em 0 0.25em 0;
}
.trace, .resources {
background: #fff;
padding: 15px;
margin: 15px auto;
border: 1px solid #ececec;
}
.trace {
overflow-y: scroll;
}
.hidden {
display: none;
}
pre {
<script> function toggleStackTraceOrder() { var stElement = document.getElementById('stacktrace'); var current = stElement.getAttribute('data-current-setting'); if (current == 'original-stacktrace') { var reverseOrder = document.getElementById('reversed-stacktrace'); stElement.innerHTML = reverseOrder.innerHTML; stElement.setAttribute('data-current-setting', 'reversed-stacktrace'); } else { var originalOrder = document.getElementById('original-stacktrace'); stElement.innerHTML = originalOrder.innerHTML; stElement.setAttribute('data-current-setting', 'original-stacktrace'); } return; } function showDefaultStackTraceOrder() { var reverseOrder = document.getElementById('reversed-stacktrace'); var stElement = document.getElementById('stacktrace'); if (reverseOrder == null || stElement == null) { return; } // default to reverse ordered stacktrace stElement.innerHTML = reverseOrder.innerHTML; stElement.setAttribute('data-current-setting', 'reversed-stacktrace'); return; } </script>white-space: pre;
font-family: Consolas, Monaco, Menlo, "Ubuntu Mono", "Liberation Mono", monospace;
font-size: 12px;
line-height: 1.5;
color: #555;
}
</style>
Internal Server Error
Error handling ffd53bd0-0bd2-4251-a2ce-6a2ffb1df01e-10, org.jboss.resteasy.spi.UnhandledException: software.amazon.awssdk.services.ses.model.SesException: null (Service: Ses, Status Code: 500, Request ID: null)
Click Here to see the stacktrace in reversed order (root-cause first)
The stacktrace below has been reversed to show the root cause first. Click Here to see the original stacktrace
The text was updated successfully, but these errors were encountered: