Repository navigation
Conversation
A turn could lose every tool for the rest of its run once the model spent more than five minutes generating between tool calls. The in-process JP MCP Server used rmcp's default session config, whose 300-second idle timeout ended the Host's session while no traffic flowed. Every later call then failed with `Session expired (HTTP 404)`, and the assistant was handed those failures as tool results to retry against a connection that could not recover. The endpoint's sessions no longer expire when idle. They last until their client closes them or the endpoint shuts down at the end of the turn, which already bounds a session an external client abandons. When JP's own connection to the server is lost anyway, the turn now ends with "Lost the connection to the JP MCP Server" instead of continuing. Every unsettled call is recorded as not executed, or as possibly run if it had been released, so each request stays paired with a response; no follow-up request is sent, and nothing more is prompted for. A single `WARN` names the error and the endpoint. A tool that fails on its own still fails only its own call. Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A turn could lose every tool for the rest of its run once the model spent more than five minutes generating between tool calls. The in-process JP MCP Server used rmcp's default session config, whose 300-second idle timeout ended the Host's session while no traffic flowed. Every later call then failed with
Session expired (HTTP 404), and the assistant was handed those failures as tool results to retry against a connection that could not recover.The endpoint's sessions no longer expire when idle. They last until their client closes them or the endpoint shuts down at the end of the turn, which already bounds a session an external client abandons.
When JP's own connection to the server is lost anyway, the turn now ends with "Lost the connection to the JP MCP Server" instead of continuing. Every unsettled call is recorded as not executed, or as possibly run if it had been released, so each request stays paired with a response; no follow-up request is sent, and nothing more is prompted for. A single
WARNnames the error and the endpoint. A tool that fails on its own still fails only its own call.