Tuxedo Event Notification Thread Hard-Loops On Sched_yield() (Doc ID 1395284.1)

Last updated on OCTOBER 12, 2022

Applies to:

Symptoms

In a scenario where there is a native Tuxedo client that subscribes to Tuxedo events by using Tuxedo's thread event notification mechanism, if the client starts a global transaction by calling tpbegin() and then it is sent a set of events to which it has subscribed, the event notification thread will continuously call sched_yield() even after the event flood has stopped and there are no more events being sent.

This problem does not occur if a global transaction is not involved.

sched_yield() was detected by using strace command.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.