two different requests get the same result
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
In the course of applying feign, two different requests get the same result.
service A invoke service B
Only one request was received on service B.
service A log
request one
2022-12-26 08:57:01.574 - traceId[] [http-nio-18003-exec-3] INFO {"code":"200","data":{"scaRecId":1607178636649340928}
request two
2022-12-26 08:57:01.578 - traceId[] [http-nio-18003-exec-11] INFO {"code":"200","data":{"scaRecId":1607178636649340928}
service B log
2022-12-26 08:57:01.566 - traceId[] [http-nio-10087-exec-10] INFO "id":1607178636636758016 【 this response missed】
2022-12-26 08:57:01.569 - traceId[] [http-nio-10087-exec-9] INFO "id":1607178636649340928
This id is the primary key id of the mysql table
Why is this return confusing？？？
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the service A Feign call and compare the two logged requests with the corresponding service B logs and MySQL primary-key results. The issue does not name repository files, tests, or a reproducible setup, so first establish a minimal reproduction showing whether both requests reach service B; done means identifying and documenting why the responses differ or are conflated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, mysql
- Domain
- api, backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100