Skip to content

chore: Adding stack trace for errors in fetching tenant from redis to debug the root cause #38842

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

Merged
trishaanand merged 1 commit into from
Jan 24, 2025
Merged

chore: Adding stack trace for errors in fetching tenant from redis to debug the root cause #38842

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion ...er/appsmith-server/src/main/java/com/appsmith/server/services/ce/TenantServiceCEImpl.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,8 @@ public Mono<Tenant> getDefaultTenant() {
.tap(Micrometer.observation(observationRegistry))
.flatMap(tenant -> repository.setUserPermissionsInObject(tenant).switchIfEmpty(Mono.just(tenant)))
.onErrorResume(e -> {
log.error("Error fetching default tenant from redis!", e);
e.printStackTrace();
log.error("Error fetching default tenant from redis : {}", e.getMessage());
// If there is an error fetching the tenant from the cache, then evict the cache and fetching from
// the db. This handles the case for deserialization errors. This prevents the entire instance to
// go down if tenant cache is corrupted.
Expand Down
Loading