charle-z opened a new pull request, #26: URL: https://github.com/apache/shenyu-plugin-store/pull/26
## Problem When a RabbitMQ logging selector switches from a custom handle to global settings, the cached selector client is removed but the saved selector configuration is retained. Reapplying the identical custom handle then skips client initialization, so logs continue through the global client. ## Fix - Clear the saved selector configuration when an empty or invalid host switches the selector back to global logging. - Skip client recreation for equal configuration only when its custom cached client actually exists. - Keep multi-client state consistent when the plugin or last custom selector is removed. - Add a constructor-mocked regression for custom A → identical A → empty/global → identical A, plus cache-missing and changed-config controls. The new test does not require a RabbitMQ broker. ## Verification - `LoggingRabbitmqPluginDataHandlerTest`: 9/9 passed. - `RabbitmqClientCacheTest`: 1/1 passed. - Five-module Maven reactor: BUILD SUCCESS (10 tests, 0 failures/errors). - Checkstyle: 0 violations; `git diff --check`: clean. - Dependencies built from apache/shenyu 2.7.2-SNAPSHOT in a local isolated Maven cache, without changing repository POMs. Fixes apache/shenyu#7454. The RabbitMQ module was moved to this repository by apache/shenyu#7506. -- 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]
