[
https://issues.apache.org/jira/browse/DISPATCH-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118211#comment-17118211
]
ASF GitHub Bot commented on DISPATCH-1646:
------------------------------------------
kgiusti commented on pull request #748:
URL: https://github.com/apache/qpid-dispatch/pull/748#issuecomment-635036555
Take a look at
[this](https://gist.github.com/kgiusti/b984e742d7e5056efeb5ca7664c071d7)
The "find_package" command allows a minimum version to be given. Our hacked
up FindLibWebSockets.cmake needs to handle that.
In addition cmake provides a macro for making a build flag
(USE_LIBWEBSOCKETS) conditionally available if another flag
(LIBWEBSOCKETS_FOUND) is true.
I think that's the cmake-y way of doing this....
----------------------------------------------------------------
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]
> Unable to delete listener with http enabled
> -------------------------------------------
>
> Key: DISPATCH-1646
> URL: https://issues.apache.org/jira/browse/DISPATCH-1646
> Project: Qpid Dispatch
> Issue Type: Improvement
> Reporter: Ulf Lilleengen
> Assignee: Ganesh Murthy
> Priority: Major
> Fix For: 1.13.0
>
>
> I'm running into an issue when trying to delete a listener which has 'http:
> true' set. The router returns the error message "HTTP listeners cannot be
> deleted". I can see that there is a test for this in the router code as well.
> However, in order for EnMasse to be able to create and delete listeners that
> are used to handle websocket connections for different tenants, we need a way
> to delete listeners with http: true set through AMQP management without
> restarting the router.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
