Overview
20+ resource leak issues : memory leaks, thread leaks, connection leaks, file handle leaks.
Leak Types
Memory: Bug: ApplicationResourceMonitor.shutdown() doesn't wait for scheduler termination #235 Bug: ApplicationResourceMonitor.shutdown() doesn't wait for scheduler termination #234 bug: ClusteredApplicationManager anonymous listener creates potential memory leak #277 bug: EtcdServiceRegistry.start() can be called multiple times creating resource leaks #269
Threads: VaultConfigSource.setConfig() overwrites entire secret, destroying other keys #239 Bug: ApplicationResourceMonitor.shutdown() doesn't wait for scheduler termination #234 bug: EtcdServiceRegistry.start() can be called multiple times creating resource leaks #269 bug: EtcdServiceRegistry lease renewal task doesn't handle exceptions #246
Connections: Bug: DatabaseVolumeManager uses database-specific SQL despite claiming JDBC compatibility #226 Bug: ConsulServiceRegistry leaves inconsistent state when Consul registration fails #231 Bug: ConsulConfigSource.loadAllConfig() doesn't handle null return from getValues() #232
Files: Bug: ClusterConfig.Builder methods don't validate parameters #237 Bug: ApiServerConfig.Builder methods don't validate parameters #238
Acceptance Criteria
All AutoCloseable implemented correctly
Try-with-resources used
Shutdown hooks clean up
All executors properly shut down
All connections closed in finally
Leak detection tests pass
Estimated Impact
~30+ leak locations, 3-4 weeks work, CRITICAL for stability
Overview
20+ resource leak issues: memory leaks, thread leaks, connection leaks, file handle leaks.
Leak Types
Acceptance Criteria
Estimated Impact
~30+ leak locations, 3-4 weeks work, CRITICAL for stability