Skip to content

CAMEL-23253: Fix flaky Infinispan Hot Rod connection timeout in tests #22265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gnodet wants to merge 2 commits into from
Closed

CAMEL-23253: Fix flaky Infinispan Hot Rod connection timeout in tests #22265

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
932b2b2
CAMEL-23253: Fix flaky Infinispan Hot Rod connection timeout in tests
gnodet Mar 25, 2026
5700531
CAMEL-23253: Wait for protobuf metadata cache readiness before starti…
gnodet Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion ...el/component/langchain4j/embeddings/LangChain4jEmbeddingsComponentInfinispanTargetIT.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,7 @@ protected void setupResources() throws Exception {
if (cacheContainer == null) {
cacheContainer = getCacheContainer();
final IterationBoundedBudget budget
= Budgets.iterationBudget().withInterval(Duration.ofSeconds(1)).withMaxIterations(10).build();
= Budgets.iterationBudget().withInterval(Duration.ofSeconds(2)).withMaxIterations(15).build();
final ForegroundTask task = Tasks.foregroundTask()
.withBudget(budget).build();

Expand All @@ -226,6 +226,9 @@ private RemoteCacheManager getCacheContainer() {
private boolean createCache() {
try {
getOrCreateCache();
// Verify the protobuf metadata cache is also ready, as the Infinispan
// component needs it when the route starts
cacheContainer.getCache("___protobuf_metadata");
Comment on lines +229 to +231
Copy link
Copy Markdown
Contributor

@apupier apupier Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this sounds like a workaround for a potential bug in the component. Shouldn't the component be able to wait that the cache is ready?

Copy link
Copy Markdown
Contributor Author

@gnodet gnodet Mar 26, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. This is indeed a workaround in the test — the component's InfinispanRemoteManager.doStart() calls EmbeddingStoreUtil.registerSchema() synchronously during route startup, which accesses the ___protobuf_metadata cache. If that internal cache isn't ready yet, it fails immediately with no retry.

Ideally the component itself should handle this gracefully (e.g., retry schema registration on IllegalLifecycleStateException). I've filed CAMEL-23255 for that. For now, the test-level readiness check ensures the server is fully initialized before starting the route.

Claude Code on behalf of Guillaume Nodet

return true;
} catch (Exception e) {
return false;
Expand All @@ -251,6 +254,8 @@ private ConfigurationBuilder getConfiguration() {
clientBuilder.addServer()
.host(service.host())
.port(service.port());
clientBuilder.socketTimeout(15000)
.connectionTimeout(15000);

clientBuilder.security()
.authentication()
Expand Down
4 changes: 4 additions & 0 deletions ...c/test/java/org/apache/camel/component/infinispan/remote/InfinispanRemoteTestSupport.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,10 @@ protected ConfigurationBuilder getConfiguration() {
.host(service.host())
.port(service.port());

clientBuilder
.socketTimeout(15000)
.connectionTimeout(15000);

// add security info
clientBuilder
.security()
Expand Down
Loading