You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2023/03/03 09:07:00 UTC

[jira] [Commented] (CAMEL-19109) camel-vertx-websocket: Consumer should avoid blocking the Vert.x event loop

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

Claus Ibsen commented on CAMEL-19109:
-------------------------------------

Have you backported this to the 3.x branches?

> camel-vertx-websocket: Consumer should avoid blocking the Vert.x event loop
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-19109
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19109
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-vertx-websocket
>    Affects Versions: 3.18.5, 3.20.2, 4.0-M1
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Major
>             Fix For: 3.18.6, 3.20.3, 3.21.0, 4.0-M2, 4.0
>
>
> There's the potential to block the Vert.x event loop if route processing coming after the vertx-websocket consumer does blocking operations. E.g like:
> {code}
> from("vertx-websocket:localhost:8080/slow")
>     .delay(5000).syncDelayed()
>     .to("mock:result");
> {code}
> We should do like what happens with camel-platform-http-vertx and wrap the exchange processing in a Vert.x blocking handler.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)