masaori335 opened a new issue #8273:
URL: https://github.com/apache/trafficserver/issues/8273
@elsloo found that inactive timeout is odd on POST request cases on our
9.0.3 deployment.
When this issue happens, debug logs are below. It looks like the HttpSM
starts TLS handshake with origin server and read op of inbound side connection
is disabled. But the inactive_cop closed the inbound connection immediately.
```
[Aug 24 02:05:31.976] [ET_NET 19] DEBUG: <HttpSM.cc:5272
(do_http_server_open)> (http) calling sslNetProcessor.connect_re
...
[Aug 24 02:05:31.976] [ET_NET 19] DEBUG: <HttpSM.cc:1817
(state_http_server_open)> (http) [10713971] setting handler for TCP handshake
[Aug 24 02:05:31.976] [ET_NET 19] DEBUG: <P_UnixNet.h:554 (read_disable)>
(socket) read_disable updating inactivity_at 0, NetEvent=0x7fbf7811dc30
...
[Aug 24 02:05:32.552] [ET_NET 19] DEBUG: <UnixNet.cc:56 (check_inactivity)>
(inactivity_cop_check) Checking inactivity on Thread-ID #19
[Aug 24 02:05:32.552] [ET_NET 19] DEBUG: <UnixNet.cc:574
(manage_active_queue)> (v_net_queue) max_connections_per_thread_in: 4687
max_requests_per_thread_in: 937 total_connections_in: 12 active_queue_size: 10
keep_alive_queue_size: 2
[Aug 24 02:05:32.552] [ET_NET 19] DEBUG: <UnixNet.cc:683 (_close_ne)>
(net_queue) closing connection NetEvent=0x7fbf7811dc30 idle: 2 now: 1629770732
at: 0 in: 70 diff: 1629770802
[Aug 24 02:05:32.552] [ET_NET 19] DEBUG: <HttpSM.cc:2632 (main_handler)>
(http) [10713971] [HttpSM::main_handler,
VC_EVENT_INACTIVITY_TIMEOUT/TS_EVENT_VCONN_INACTIVITY_TIMEOUT]
```
I think #7304 introduced this behavior. The is gone by reverting the commit.
To fix this issue with #7304, we need to check the
`ne->next_inactivity_timeout_at` before closing the connection by the
inactive_cop. A caveat is connection throttling is using the same function
(`NetHandler::manage_keep_alive_queue()`).
--
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]
