[
https://issues.apache.org/jira/browse/CAMEL-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Netherton updated CAMEL-19190:
------------------------------------
Fix Version/s: 3.21.0
> camel-vertx-websocket: sendToAll option may not discover connected host peers
> correctly
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-19190
> URL: https://issues.apache.org/jira/browse/CAMEL-19190
> Project: Camel
> Issue Type: Bug
> Components: camel-vertx-websocket
> Reporter: James Netherton
> Assignee: James Netherton
> Priority: Major
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> While adding some more test coverage for vertx-websocket in Camel Quarkus, I
> noticed the logic to find connected peers on the local server when using the
> sendToAll option or the CamelVertxWebsocket.connectionKey header is a bit
> flawed. It can fail to find the correct peer, or incorrectly find matches for
> the wrong peers.
> There's some more background in this Camel Quarkus issue:
> https://github.com/apache/camel-quarkus/issues/4628
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
