When setting node-address.context-path to a non-empty value, calls to SqsClient.sendMessage stop working.
Issue disappears if node-address.context-path = ""
Calls to SqsClient.getQueueUrl still work, so I think the issue is in the way QueueDirectives.scala#L46 is parsing the request.
Info from some debug logging:
Starting ElasticMQ server on http://localhost:34998/context
Slf4jLogger started
Started SQS rest server, bind address 0.0.0.0:34998, visible server address http://localhost:34998/context
Started statistics rest server, bind address 0.0.0.0:34999
Creating queue QueueData(test-queue-1,MillisVisibilityTimeout(30000),PT0S,PT0S,2021-12-08T13:03:10.252Z,2021-12-08T13:03:10.252Z,None,false,false,None,None,Map())
Dec 08, 2021 1:03:12 PM TestClientClass getQueueUrlFromSqs
DEBUG: GetQueueUrlRequest(QueueName=test-queue-1)
Dec 08, 2021 1:03:13 PM TestClientClass getQueueUrlFromSqs
DEBUG: GetQueueUrlResponse(QueueUrl=http://localhost:34998/context/000000000000/test-queue-1)
Dec 08, 2021 1:03:13 PM TestClientClass addMessage
DEBUG: SendMessageRequest(QueueUrl=http://localhost:34998/context/000000000000/test-queue-1, MessageBody=This is the message)
Dec 08, 2021 1:03:13 PM TestClientClass addMessage
DEBUG: software.amazon.awssdk.services.sqs.model.SqsException: Invalid request: MissingQueryParamRejection(QueueName), MissingQueryParamRejection(QueueUrl); see the SQS docs. (Service: Sqs, Status Code: 400, Request ID: 00000000-0000-0000-0000-000000000000, Extended Request ID: null)
Issue occurred using on:
Java AdoptOpenJDK 1.8.0_292 Hotspot
Maven 3.6.3
org.elasticmq > elasticmq-server_2.13 > version 1.3.3
When setting
node-address.context-path
to a non-empty value, calls toSqsClient.sendMessage
stop working.Issue disappears if
node-address.context-path = ""
Calls to
SqsClient.getQueueUrl
still work, so I think the issue is in the wayQueueDirectives.scala#L46
is parsing the request.Info from some debug logging:
Issue occurred using on: