Feature208965 Improve fairness even more while growing the connection pool
Releases 6.0.110 and 6.0.111 offered a fairer way of growing the connection pool. This has been optimised further.
Technical details
The two prior releases attempted to offer a fairer way of growing the connection pool, so a thread that requests an extra connection could also use it. However, there the algorithm was still not as good as it could be, because it did the following:
- Thread A requests growing the pool
- The pool adds an extra connection
- The extra connection is put into the pool of available connections
- Thread A then quickly fetches the new connection
While this performed better than before, this still allowed for another thread to hijack the connection between steps 3 and 4.
We now changed this to the following:
- Thread A requests growing the pool
- The pool adds an extra connection
- The pool marks the connection as being used
- The extra connection is put into the pool of available connections
- The extra connection is returned for Thread A to use
The extra step 3 implies that no other thread can take the connection after step 4. Thus, Thread A is always able to use the new connection.
Changes impacting client API
None.
Issue202334 Modify Tomcat examples to use Docker
| Severity: | 4 |
|---|---|
| Affected version(s): | 6.0.110 |
Description
The Tomcat examples have been modified to user Docker, but this does not work on all platforms yet.
Technical details
The Docker image generated to run the Tomcat examples contains a Java JDK that is not binary compatible with all platforms yet.
Add a comment