Tuxedo Event Notification Thread Hard-Loops On Sched_yield()

(Doc ID 1395284.1)

Last updated on FEBRUARY 11, 2017

Applies to:

Oracle Tuxedo - Version: 10.3.0 and later   [Release: and later ]
Information in this document applies to any platform.


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.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms