zenghu1chen commented on PR #230: URL: https://github.com/apache/commons-pool/pull/230#issuecomment-1643446429
> @zenghu1chen I think the first step would be to test your use case with the current version of Pool, 2.11.1, not 2.4.2. Also consider testing with git branch POOL_2_X. 2.4.2 is very old! @garydgregory I tried to test Jedis to reproduce deadlock situations, but I failed because I was not clear about what kind of Redis failure would lead to deadlock. However, since I observed the occurrence of "pinning" in the GenericObjectPool class, I started testing this class. Currently, there is an imperfect test case that can reproduce the deadlock situation. The usage is a bit strange and relies on probability to generate deadlock, but it should also demonstrate the possibility of deadlock. You can find the test case at the following link: https://github.com/zenghu1chen/loom-compatibility-test/blob/main/src/main/java/org/example/commonspool2/GenericObjectPoolTest.java -- 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]
