{"action":"closed","issue":{"url":"https://api.github.com/repos/adamw/elasticmq/issues/88","repository_url":"https://api.github.com/repos/adamw/elasticmq","labels_url":"https://api.github.com/repos/adamw/elasticmq/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/adamw/elasticmq/issues/88/comments","events_url":"https://api.github.com/repos/adamw/elasticmq/issues/88/events","html_url":"https://github.com/adamw/elasticmq/issues/88","id":193462477,"number":88,"title":"Support for dynamic port","user":{"login":"pjungermann","id":2513586,"avatar_url":"https://avatars.githubusercontent.com/u/2513586?v=3","gravatar_id":"","url":"https://api.github.com/users/pjungermann","html_url":"https://github.com/pjungermann","followers_url":"https://api.github.com/users/pjungermann/followers","following_url":"https://api.github.com/users/pjungermann/following{/other_user}","gists_url":"https://api.github.com/users/pjungermann/gists{/gist_id}","starred_url":"https://api.github.com/users/pjungermann/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pjungermann/subscriptions","organizations_url":"https://api.github.com/users/pjungermann/orgs","repos_url":"https://api.github.com/users/pjungermann/repos","events_url":"https://api.github.com/users/pjungermann/events{/privacy}","received_events_url":"https://api.github.com/users/pjungermann/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-05T10:37:08Z","updated_at":"2016-12-07T14:55:05Z","closed_at":"2016-12-07T14:55:05Z","body":"This issue is related to #87 \r\n\r\nInstead of using the default port, it would be great to support a dynamic port. I tried that by using port 0 and then retrieve the actual port from the started `SQSRestServer` instance, but due to #87, the queue addresses have been wrong and due to the fact that the `NodeAddress` is just some kind of string builder, using port 0 at the `serverAddress` just resulted in port 0 being part of the string.\r\n\r\nA workaround here is to find a free socket yourself by i.e. using `new ServerSocker(0).getLocalPort`. For development, that was fine (so far), but there are concurrency issues as other process might bind to the port you have found to be free. Therefore, it was failing on our CI server. But exactly there, we would need that dynamic port feature to allow multiple test runs using ElasicMQ, e.g. feature branches or different projects."}}
{"actor":{"display_login":"adamw"}}