bug: Encountered errors during stress testing when deploying services on Kylin OS

### Current Behavior

When using JMeter to perform stress testing on interfaces deployed on APISIX, the error rate reached 10%.

### Expected Behavior

We expect no errors to occur under the stress test environment.

### Error Logs

### Steps to Reproduce

Register the interface to APISIX
Conduct stress testing via JMeter
Set the concurrency to 10
Errors appear in logs, with an error rate of approximately 10%

### Environment

- APISIX version (3.10)
- Operating system (Kylin OS):
- OpenResty / Nginx version (openresty/1.25.3.2):
- etcd version, if relevant ({"hostname":"cnbj02vl00505.cmftdc.cn","boot_time":1778826739,"version":"3.10.0","id":"a9833363-ca78-4588-8db4-de4a70e824b9","etcd_version":"3.5.0"}):
- APISIX Dashboard version, if relevant:
- Plugin runner version, for issues related to plugin runners:
- LuaRocks version, for installation issues (/usr/local/bin/luarocks 3.12.0):

Start by reproducing the issue with APISIX 3.10 on Kylin OS using the reported interface, JMeter, and concurrency of 10. The missing error.log prevents identifying the failing entry point; collect the actual logs and compare behavior with the listed OpenResty/Nginx and etcd versions. Done means determining the cause of the approximately 10% error rate and confirming that the stress test completes without errors.

Written by the indexing model from the issue text.