InvalidAction on sendMessage

79 views
Skip to first unread message

Arne Claassen

unread,
Aug 16, 2019, 3:12:42 PM8/16/19
to ElasticMQ
I've set up the latest docker container, but when I tried using the v2 AWS Java SDK to test it, I received:

InvalidAction; see the SQS docs. (Service: AmazonSQS; Status Code: 400; Error Code: InvalidAction; Request ID: 00000000-0000-0000-0000-000000000000)


on client.sendMessage

So I tried the v1 Java SDK and verified the syntax against the AmazonJavaSdkTestSuite, but I'm getting the same result.

I've tried building the project, so I could verify the Test suite against master, but the project fails to load with:

[error] error while loading CharSequence, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home/jre/lib/rt.jar(java/lang/CharSequence.class)' is broken
[error] (bad constant pool tag 18 at byte 10)
[error] error while loading Comparator, class file '/Library/Java/JavaVirtualMachines/jdk1.8.0_192.jdk/Contents/Home/jre/lib/rt.jar(java/util/Comparator.class)' is broken
[error] (bad constant pool tag 18 at byte 20)
[error] two errors found
[error] (compile:compile) Compilation failed


I noticed that the docs, keep saying that ElasticMQ supports "a subset of the SQS query (REST) interface", so does that mean SendMessage is not supported, and if so, how is it in the Test suite?

Any help troubleshooting either why I can't send messages or even why the project won't load would be appreciated.

cheers,
arne

Arne Claassen

unread,
Aug 16, 2019, 3:39:31 PM8/16/19
to ElasticMQ
Never mind on both. A clear case of PEBKAC.

The send error happened because I passed queueName rather than queueUrl to sentMessage.

The second happened because apparently I already had an ancient fork of elasticMQ (0.7) which relied on defunct sbt and scala versions.
Reply all
Reply to author
Forward
0 new messages