You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "James Netherton (Jira)" <ji...@apache.org> on 2023/03/24 15:54:00 UTC
[jira] [Commented] (CAMEL-19190) camel-vertx-websocket: sendToAll option may not discover connected host peers correctly
[ https://issues.apache.org/jira/browse/CAMEL-19190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704674#comment-17704674 ]
James Netherton commented on CAMEL-19190:
-----------------------------------------
Fixed this for 4.x. Before resolving the ticket I'll check if it's feasible to backport the changes to other branches.
> 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
>
> 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)