Skip to content

FINERACT-2684: Add "App is ready" message to log - #6387

Open
adamsaghy wants to merge 1 commit into
apache:developfrom
adamsaghy:FINERACT-2684/app-is-running-message
Open

FINERACT-2684: Add "App is ready" message to log#6387
adamsaghy wants to merge 1 commit into
apache:developfrom
adamsaghy:FINERACT-2684/app-is-running-message

Conversation

@adamsaghy

Copy link
Copy Markdown
Contributor

Description

Add "App is ready" and "App is shutting down" (not these words) message for better clarity over the lifecycle of the running Fineract instance

@adamsaghy
adamsaghy force-pushed the FINERACT-2684/app-is-running-message branch from 7aae2cc to cc1fe78 Compare September 7, 2026 13:18

@TianHengZhuang TianHengZhuang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Excellent approach using @EventListener for Spring lifecycle events!

  1. Separation of concerns: A dedicated FineractApplicationLifecycleLogger component is clean — no coupling to the main application class.
  2. volatile context field: Good thread-safety practice since ApplicationReadyEvent and ContextClosedEvent may fire on different threads.
  3. Test coverage: The two test cases cover HTTPS+context-path and IPv6+root context. Consider adding a third test for plain HTTP (no SSL) with default port for completeness.
  4. README note: The BUILD CANCELLED Gradle message explanation is valuable for new developers.

Solid implementation. ✅

@TianHengZhuang TianHengZhuang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM — well-structured Spring lifecycle observer pattern, minimal and focused. The tests provide good confidence. ✅

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.

2 participants