nic-chen commented on issue #9511:
URL: https://github.com/apache/apisix/issues/9511#issuecomment-1610388193

   Here is my test process(Same configurations with yours, and APISIX version 
is 3.2.1):
   
   Connect to redis through APISIX's proxy:
   <img width="387" alt="image" 
src="https://github.com/apache/apisix/assets/33000667/c82d5404-31b2-4d42-9261-ee12dc73fb26";>
   
   In the APISIX container, we could see connections on ports 9100 and 2379:
   
![img_v2_f9120f08-fe0a-4f31-b712-56074761698g](https://github.com/apache/apisix/assets/33000667/2f76a6dd-dcdb-404c-afc5-8f9b550a634e)
   
   Use the `quit` command to close the connection:
   <img width="245" alt="image" 
src="https://github.com/apache/apisix/assets/33000667/9d3c2372-db3e-4f82-98a9-16eb3f8983d2";>
   
   We could see that the connection on port 9100 no longer exists:
   <img width="615" alt="image" 
src="https://github.com/apache/apisix/assets/33000667/de1dca87-2e48-48b0-adbe-40e1b8a69526";>
   
   After a while, the connection on port 6379 also disappeared:
   <img width="586" alt="image" 
src="https://github.com/apache/apisix/assets/33000667/cf4c9337-4082-43f0-846f-cc4d75627d9f";>
   
   
   Close the connection by `control + c` has the same behavior.
   
   
   So the bug should not exist, and you need to determine whether your client 
is really disconnected from APISIX. @zzqCh 
   
   
   
   


-- 
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]

Reply via email to