yasithdev opened a new pull request, #603:
URL: https://github.com/apache/airavata/pull/603
## Summary
Server reliability improvements addressing the follow-up items from #602.
### 1. Consolidate monitoring servers
- Removed 4 redundant per-service MonitoringServer instances (ports
9093-9096)
- All metrics already share `CollectorRegistry.defaultRegistry` — single
endpoint on :9097 serves everything
- Removed 12 unused monitoring properties from `airavata-server.properties`
and Ansible templates
### 2. Migrate JDBC config to Spring datasource
- Created `SpringSettingsBridge` that injects `spring.datasource.*` values
into `ApplicationSettings` overrides
- Legacy code reading `airavata.jdbc.*` now transparently receives
Spring-managed datasource values
- Removed duplicate `airavata.jdbc.*` properties from
`airavata-server.properties` and all Ansible configs
- `application.yml` is now the single source of truth for database
credentials
### 3. Switch to Spring Boot auto-configured JPA
- Removed manual `LocalContainerEntityManagerFactoryBean` from
`AiravataServerMain`
- Using `@EntityScan("org.apache.airavata")` +
`PhysicalNamingStrategyStandardImpl` in `application.yml`
- This properly resolves the Hibernate 6.6 `DuplicateMappingException` on
shared @Id/@JoinColumn columns
- Added `@DependsOn("springSettingsBridge")` on `AiravataServerHandler` to
ensure JDBC config is available during construction
### 4. Swap Kafka image
- Replaced unmaintained `wurstmeister/kafka` (last updated 2021) with
official `apache/kafka:3.9.0`
- Uses standard `KAFKA_LISTENERS`/`KAFKA_ADVERTISED_LISTENERS` instead of
deprecated `KAFKA_ADVERTISED_HOST_NAME`
- Maintains ZooKeeper mode (still needed for Helix cluster management)
## Test plan
- [x] `mvn test -T4` — 179 tests, 0 failures
- [x] Cold start: `java -jar airavata-server.jar` → all 4 ports UP, 8
services healthy
- [x] `/actuator/health` → UP
- [x] `/health/services` → all services UP
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
