Ex­tremeTrans­ac­tions 6.0.112

Re­lease notes for 6.0.112

Fea­ture208965

Im­prove fair­ness even more while grow­ing the con­nec­tion pool

Re­leas­es 6.0.110 and 6.0.111 of­fered a fair­er way of grow­ing the con­nec­tion pool. This has been op­ti­mised fur­ther.

Tech­ni­cal de­tails

The two pri­or re­leas­es at­tempt­ed to of­fer a fair­er way of grow­ing the con­nec­tion pool, so a thread that re­quests an ex­tra con­nec­tion could also use it. How­ev­er, there the al­go­rithm was still not as good as it could be, be­cause it did the fol­low­ing:

1. Thread A re­quests grow­ing the pool
2. The pool adds an ex­tra con­nec­tion
3. The ex­tra con­nec­tion is put into the pool of avail­able con­nec­tions
4. Thread A then quick­ly fetch­es the new con­nec­tion

While this per­formed bet­ter than be­fore, this still al­lowed for an­oth­er thread to hi­jack the con­nec­tion be­tween steps 3 and 4.

We now changed this to the fol­low­ing:

1. Thread A re­quests grow­ing the pool
2. The pool adds an ex­tra con­nec­tion
3. The pool marks the con­nec­tion as be­ing used
4. The ex­tra con­nec­tion is put into the pool of avail­able con­nec­tions
5. The ex­tra con­nec­tion is re­turned for Thread A to use

The ex­tra step 3 im­plies that no oth­er thread can take the con­nec­tion af­ter step 4. Thus, Thread A is al­ways able to use the new con­nec­tion.

Changes im­pact­ing client API

None.

Is­sue202334

Mod­i­fy Tom­cat ex­am­ples to use Dock­er

Sever­i­ty:	4
Af­fect­ed ver­sion(s):	6.0.110

De­scrip­tion

The Tom­cat ex­am­ples have been mod­i­fied to user Dock­er, but this does not work on all plat­forms yet.

Tech­ni­cal de­tails

The Dock­er im­age gen­er­at­ed to run the Tom­cat ex­am­ples con­tains a Java JDK that is not bi­na­ry com­pat­i­ble with all plat­forms yet.

About Sever­i­ty

The sever­i­ty lev­els we use are de­fined in our sup­port terms and con­di­tions.