-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
-
When an AJP request with a request duration longer than 90 seconds as read-timeout=“90000”, we can see duplicate response on wireshark. mod_proxy_ajp and mod_jk ignore duplicate responses, so it doesn't seem to cause any actual harm.
jbeap_ajp_read-timeout_issue.pcap
1 2024-12-06 17:24:11.211286 127.0.0.1 127.0.0.1 TCP 74 49708 → 8009 [SYN] Seq=0 Win=65495 Len=0 MSS=65495 SACK_PERM TSval=1576498431 TSecr=0 WS=128 2 2024-12-06 17:24:11.211291 127.0.0.1 127.0.0.1 TCP 74 8009 → 49708 [SYN, ACK] Seq=0 Ack=1 Win=65483 Len=0 MSS=65495 SACK_PERM TSval=1576498431 TSecr=1576498431 WS=128 3 2024-12-06 17:24:11.211296 127.0.0.1 127.0.0.1 TCP 66 49708 → 8009 [ACK] Seq=1 Ack=1 Win=65536 Len=0 TSval=1576498431 TSecr=1576498431 4 2024-12-06 17:24:11.211316 127.0.0.1 127.0.0.1 AJP13 244 2:REQ:GET /app/sleep.jsp HTTP/1.1 5 2024-12-06 17:24:11.211319 127.0.0.1 127.0.0.1 TCP 66 8009 → 49708 [ACK] Seq=1 Ack=179 Win=65408 Len=0 TSval=1576498431 TSecr=1576498431 6 2024-12-06 17:25:51.479581 127.0.0.1 127.0.0.1 AJP13 350 2:RSP:SEND BODY CHUNK 7 2024-12-06 17:25:51.479591 127.0.0.1 127.0.0.1 TCP 66 49708 → 8009 [ACK] Seq=179 Ack=285 Win=65280 Len=0 TSval=1576598699 TSecr=1576598699 8 2024-12-06 17:25:51.480255 127.0.0.1 127.0.0.1 AJP13 72 2:RSP:END RESPONSE 9 2024-12-06 17:25:51.480260 127.0.0.1 127.0.0.1 TCP 66 49708 → 8009 [ACK] Seq=179 Ack=291 Win=65280 Len=0 TSval=1576598700 TSecr=1576598700 10 2024-12-06 17:25:51.482553 127.0.0.1 127.0.0.1 AJP13 84 2:RSP:END RESPONSE <<<=== duplicate reponse due to read-timeout 11 2024-12-06 17:25:51.482563 127.0.0.1 127.0.0.1 TCP 66 49708 → 8009 [ACK] Seq=179 Ack=309 Win=65280 Len=0 TSval=1576598702 TSecr=1576598702 12 2024-12-06 17:25:51.483542 127.0.0.1 127.0.0.1 TCP 66 8009 → 49708 [FIN, ACK] Seq=309 Ack=179 Win=65536 Len=0 TSval=1576598703 TSecr=1576598702 13 2024-12-06 17:25:51.524009 127.0.0.1 127.0.0.1 TCP 66 49708 → 8009 [ACK] Seq=179 Ack=310 Win=65280 Len=0 TSval=1576598744 TSecr=1576598703