Bug #569
closed
Added by Marc Dequènes over 7 years ago.
Updated over 7 years ago.
Description
In the logs I discovered messages are duplicated for the same timestamp.
The service works fine, so this is annoying but not critical.
- Category set to server-regip
- Status changed from New to Blocked
- Assignee set to Marc Dequènes
I checked if the client was not sending multiple requests, and it was not, and a tshark on the server side confirmed: only 2 requests (IPv4 and IPv6), which is expected.
On the server side the code do not loop on the request so I checked very early the UNIQUE_ID received and the app receives the same request multiple times. I could not find any explanation while looking at the Passenger and Rack stack.
I guess there's a bug in the stask, most probably the Passenger dispatch, but I could not find it. The code is complex so I would probably have to dig more into it. I checked related BRs and did not find any.
So, I plan to look again into it after the Stretch migration. Let's see if this is fixed in a recent version and if not fill a BR.
- Status changed from Blocked to In Progress
The Stretch migration did not change the behavior at all.
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by