raboof commented on PR #230: URL: https://github.com/apache/commons-pool/pull/230#issuecomment-3098564518
> I want to know when the community will take this issue seriously? This should not be ignored - this problem has been ongoing for two years now. The way I read the issue so far: * the community *is* taking this potential issue seriously. * it is not yet clear what exactly was causing the pinning/deadlock that @zenghu1chen observed. That means it is not clear it was caused by commons-pool, and it is not clear that this proposed change fixes it. * the discussion and investigation on the issue did lead to the insight that it would be good to eliminate the use of intrinsic locks here, regardless of whether the issue @zenghu1chen observed was caused by that * the current PR is not suitable because it does not have unit tests showing a change in behavior * the current PR is not suitable because it uses a global lock Since you commented, I assume you're seeing this problem (or a similar one) as well? If so, we need your help. You are part of the community, too. Can you describe with what code you're seeing the problem? Which JVM versions? Which version of commons-pool? Any other versions? Can you construct a small example project you can share that we can analyze? -- 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]
