[JAVA-4630] Remove copy of ConcurrentLinkedDeque Created: 25/May/22  Updated: 28/Oct/23  Resolved: 01/Jun/22

Status: Closed
Project: Java Driver
Component/s: Internal
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Improvement Priority: Minor - P4
Reporter: Jeffrey Yemin Assignee: Jeffrey Yemin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Documentation Changes: Not Needed

 Description   

Once JAVA-4629 is done, we can remove support for Prune.STOP from ConcurrentPool and go back to the original prune algorithm. That will also let us delete our copy of ConcurrentLinkedDeque.



 Comments   
Comment by Githook User [ 01/Jun/22 ]

Author:

{'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}

Message: Remove copy of ConcurrentLinkedDeque (#956)

  • Rely on java.util.concurrent.ConcurrentLinkedDeque instead
  • Change ConcurrentPool#prune to use an algorithm that doesn't
    depend on changes to our ConcurrentLinkedDeque copy

JAVA-4630
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/3702de367dda27bedd4023beac8cdab157a6f489

Generated at Thu Feb 08 09:02:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.