[TINKERPOP-2550] Deadlock on Client initialization

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.4.10
• Fix Version/s: 3.5.0, 3.4.11
• Component/s: driver
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 20/Apr/21 11:25
• Updated: 23/Apr/21 13:32
• Resolved: 23/Apr/21 10:06

Description

Observed from TINKERPOP-2504 but also identified elsewhere. When the workerPoolSize is insufficiently sized it can lead to deadlock because the Host is blocking for its ConnectionPool to initialize and there will be no threads left to service the latter which keeps the former stuck.

Issue Links

• is depended upon by: TINKERPOP-2504 Intermittently failing server/driver integration tests