We have discovered a defect in EBX 6.2.2, 6.2.2 HF-1 and 6.2.2 HF-2 and therefore recommend upgrading as soon as possible to EBX 6.2.2 HF-3.

Please note that we have not seen this issue in any EBX environment for the moment, but environments running EBX 6.2.2 and 6.2.2 HF-1 may be affected by bug CP-28728 : The index can be corrupted after rollback when pooling is used.
The issue relates to an inconsistency in the in-memory cache for a specific index. The stored index and the persisted data are correct and consistent. The inconsistency occurs in memory after a rollback, combined with a very rare and specific memory state. 
In this situation, the in-memory index is not rolled back for a few seconds or minutes : the related data may be incorrect during that period. 
A garbage collector cycle —which runs regularly every few minutes— will clean up the incorrect in-memory index. 
Therefore, restarting the EBX server is not required to resolve this issue; the garbage collector will fix it more efficiently.
The probability to occur is extremely low but can't be considered null.

EBX 6.2.2 HF-2 is affected by bug CP-28917 : An index exception can be raised when validating a dataset.
The fix introduced by CP-28789 in this version can, sometimes, trigger an index exception when validating a dataset. As a consequence this fix has been reverted.

As a consequence, EBX 6.2.2-HF1 and 6.2.2 HF-2 have been removed from the Downloads section of the TIBCO Support Portal.

Upgrade to EBX 6.2.2 HF-3 recommended for environments running EBX 6.2.2,  6.2.2 HF-1 and 6.2.2 HF-2.