-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQS queue url seems to hardcoded to 9324 #33
Comments
You need to also specify the However this is still inconvenient, when using a custom port, the server address should be changed as well, unless a custom one is provided. So that's a thing to fix. |
yes. Because I want to let system choose a ephemeral port, I passed port 0 to withPort(...) method. I can't really construct NodeAddress with port 0 to withServerAddress(...) method. I would expect server address to be changed to the actual bound port (e.g. 59923). |
is there a difference between using |
No; |
@adamw this caught me out as well and I almost abandoned ElasticMQ as a result. Since it is the common case that the bound and node addresses are equal, wouldn't it make sense if they were permitted to differ by exception only? Otherwise the API violates the principle of least surprise. |
Yes I definitely want to take care of this in the next release, once I'll have some more time :) |
I'm going to close this issue; although confusing, I did not find a good way to automatically set node-address basing on bind address. Even the defaults (bind: 0.0.0.0, node-address host: localhost) are different, plus ElasticMQ can be configured through code or config file. I added a note in the readme, close to the top, hopefully people will spot that :) |
I have started elasticMQ server by using "java -jar elasticmq-server-0.13.8.jar" command and below response i got. 12:04:09.476 [main] INFO org.elasticmq.server.Main$ - Starting ElasticMQ server But when i tried to access http://localhost:9324, it is displaying blank page with "The requested resource could not be found." message. Is something wrong with my SQS server ? |
@sfanish no, there's no http interface, so you shouldn't expect to be able to open the page in the browser. Instead, that address exposes a number of REST endpoints which can be accessed using an AWS client - and specifying |
this will cause connection error when trying to use AmazonSQSClient to send msg later, because it tries to connect to port 9324 instead of the correct ephemeral port 59923.
here is the output from the test code below.
here is the complete test code to reproduce the issue
The text was updated successfully, but these errors were encountered: