API Server: Session-based reader-writer locking. (4382925)

Within a session, writing API requests must have exclusive access to the session at any given time. Transaction interference between concurrent API requests on shared sessions must be prevented.

A "reading" API request is defined as a GET, HEAD or OPTIONS request. All others are considered "writing" API requests.

Multiple parallel HTTP requests sharing the same ISession instance could execute statements on each other's transactions, leading to data inconsistencies. For example, if Request A opened a transaction, Request B's statements would inadvertently run inside that transaction.

This is a product defect (697916).

WORKAROUND:

None

STATUS:

This will be fixed in a future release of the product. If you require this immediately corrected, please contact support for a hotfix referencing the defect ID 697916.