Skip to content

CAMEL-24380: Fix platform-http timeout returning Whitelabel Error Page - #1886

Merged
davsclaus merged 1 commit into
camel-spring-boot-4.18.xfrom
fix/CAMEL-24380
Aug 11, 2026
Merged

CAMEL-24380: Fix platform-http timeout returning Whitelabel Error Page#1886
davsclaus merged 1 commit into
camel-spring-boot-4.18.xfrom
fix/CAMEL-24380

Conversation

@davsclaus

Copy link
Copy Markdown
Contributor

Summary

  • Remove the WebAsyncTask.onTimeout() callback that called response.sendError(503) directly, bypassing Spring MVC's exception resolution chain
  • Without the callback, Spring's default AsyncRequestTimeoutException propagates normally, populating the jakarta.servlet.error.* request attributes so that Boot's BasicErrorController renders the standard JSON error response
  • This aligns with how main and 4.22.x handle timeouts (neither has a custom onTimeout callback)

Test plan

  • Verify that a platform-http route with a slow downstream returns Spring Boot's standard JSON error response ({"status":503,"error":"Service Unavailable",...}) when the request timeout is exceeded
  • Verify that non-timeout requests are unaffected

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

🤖 Generated with Claude Code

Remove the WebAsyncTask onTimeout callback that called
response.sendError(503) directly, bypassing Spring MVC's exception
resolution chain. Without the callback, Spring's default
AsyncRequestTimeoutException propagates normally, populating the
jakarta.servlet.error.* request attributes so that Boot's
BasicErrorController renders the standard JSON error response.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
@davsclaus
davsclaus merged commit c1dc0b7 into camel-spring-boot-4.18.x Aug 11, 2026
2 checks passed
@davsclaus
davsclaus deleted the fix/CAMEL-24380 branch August 11, 2026 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant