[ 
https://issues.apache.org/jira/browse/DISPATCH-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168169#comment-17168169
 ] 

ASF GitHub Bot commented on DISPATCH-960:
-----------------------------------------

jiridanek commented on pull request #802:
URL: https://github.com/apache/qpid-dispatch/pull/802#issuecomment-666631020


   I'm not super excited about how the patch turned out (looks way too 
complicated for the simple thing it is doing...) but if you think it is 
allright, I'll go ahead with it. And it passes the tests ;)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> TCP port randomly assigned when using 'port: amqp' along with 'http: yes' on 
> a listener
> ---------------------------------------------------------------------------------------
>
>                 Key: DISPATCH-960
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-960
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 1.0.1, 1.12.0
>            Reporter: Fernando Giorgetti
>            Priority: Major
>             Fix For: 1.13.0
>
>         Attachments: dispatch-960-reproducer.tar.gz
>
>
> The default configuration for the dispatch router contains a default listener 
> set up to use 'port: amqp'.
> If you change the default listener to use 'http: yes' and starts the router, 
> it causes an issue as the service name (amqp) is not resolved, and so the 
> router attempts to listen to port 0 (random), causing an unpredictable 
> behavior.
>  
> A reproducer is attached to this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to