2.7.8 safe guard client , should not be called ,must have a bug
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
升级到2.7.8之后,日志会频繁打印这个错误,看到在2.7.12中解决了这个问题,但是我看2.7.12中,也不过只是
URL lazyUrl = url.addParameter(LAZY_CONNECT_INITIAL_STATE_KEY, Boolean.TRUE)
//.addParameter(RECONNECT_KEY, Boolean.FALSE)
.addParameter(SEND_RECONNECT_KEY, Boolean.TRUE.toString());
//.addParameter(LazyConnectExchangeClient.REQUEST_WITH_WARNING_KEY, true);
client = new LazyConnectExchangeClient(lazyUrl, client.getExchangeHandler());
也只是注释了这个打印?
Contributor guide
Research direction
Start with LazyConnectExchangeClient and the URL construction shown in the issue, then compare the 2.7.8 behavior with the 2.7.12 change. Reproduce the frequent log message and determine whether the guard is incorrectly reached or only unnecessarily logged. Done means the erroneous warning no longer occurs under the reported conditions, with a regression test or clear verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100