Skip to content

[ISSUE #7454] Restore RabbitMQ selector clients after global fallback - #33

Open
yangjj-iso wants to merge 2 commits into
apache:masterfrom
yangjj-iso:feat/issue-7454-rabbitmq-client-restore
Open

yangjj-iso wants to merge 2 commits into
apache:masterfrom
yangjj-iso:feat/issue-7454-rabbitmq-client-restore

Conversation

@yangjj-iso

Copy link
Copy Markdown

Switching a RabbitMQ logging Selector from custom configuration A to global settings and then back to the identical A currently leaves it using the global client. Client invalidation retains the saved configuration, so the equality check suppresses reconstruction.

Remove the saved Selector configuration when invalidating its custom client. Add regression controls for A → global → identical A, unchanged live configuration, and changed configuration. Align the existing shared fixture's builder call with the pinned core API so this branch builds independently.

Fixes apache/shenyu#7454.

Validation: 14 tests in LoggingRabbitmqPluginDataHandlerTest and RabbitmqClientCacheTest, with Checkstyle and RAT. Broker-facing construction is mocked; no real RabbitMQ broker is required. Tested against core 2.7.2-SNAPSHOT at b46bf15c3a243e926994cb32c3f0a23eadc41adf.

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.

[BUG] RabbitMQ logging does not restore a selector client after clearing and reapplying the same handle

1 participant