[jira] [Resolved] (CAMEL-25076) camel-mcp-server - stdio: adding a tool fails when stdin is closed, which breaks StdioMcpServerEngineTest

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-25076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-25076.
---------------------------------
    Fix Version/s: 4.23.0
       Resolution: Fixed

Fixed in https://github.com/apache/camel/pull/26966, merged as 7b853fb76834.

> camel-mcp-server - stdio: adding a tool fails when stdin is closed, which breaks StdioMcpServerEngineTest
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25076
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25076
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-mcp-server
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.23.0
>
>
> With the stdio transport (StdioMcpServerEngine), adding an ai-tool route fails once stdin has been closed (the client went away): McpSyncServer.addTool registers the tool and then notifies the client that the tool list changed, and that notification fails with RuntimeException: Failed to enqueue message, as the SDK closes the outbound side of the session when stdin ends. The exception fails CamelContext startup or the added route.
> StdioMcpServerEngineTest uses an empty stdin, so it races with this and now fails consistently (it breaks CI of PRs that build camel-mcp-server).
> Fix: the tool is registered either way, so a failed notification is logged as a WARN instead of failing the route. Invalid tools (IllegalArgumentException/IllegalStateException) still fail.



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