RockteMQ-AI commented on issue #2213: URL: https://github.com/apache/rocketmq-dashboard/issues/2213#issuecomment-5300447454
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** `InstanceProviderRegistry` constructor uses `providerList.forEach(provider -> providers.put(provider.vendor(), provider))` and the same pattern for catalogs. `EnumMap.put` silently replaces existing entries, so if two Spring beans claim the same `InstanceVendor`, the last one wins without any warning or error. The selected implementation depends on Spring's bean ordering, making misconfiguration hard to diagnose. **Impact:** Duplicate provider registrations silently route requests to an unintended implementation. Configuration errors are not caught at startup. **Severity:** medium An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager-bot* -- 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]
