Tuxedo Hangs Up With LIBTUX_CAT:5005 When Many Application Server Processes Restarted (Doc ID 2221728.1)

Last updated on JANUARY 11, 2017

Applies to:

Oracle Tuxedo - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

When server processing slows down due to Database problem, many Tuxedo application server processes killed by Tuxedo BBL process because SVCTIMEOUT occurs.

Under this situation, Tuxedo hangs with following ULOG message.

175916.651.server!BBL.9853.2258732800.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=24593
175926.651.server!BBL.9853.2258732800.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=24593
175936.652.server!BBL.9853.2258732800.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=24593
175946.652.server!BBL.9853.2258732800.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=24593
175956.652.server!BBL.9853.2258732800.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=24593

 After the problem happen, all Tuxedo commands including tmadmin also hang. It is needed to restart whole Tuxedo.

Changes

 

Cause

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