RP/TUX 7.1 - GWADM exits because of SIGALRM (Doc ID 769624.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo
Information in this document applies to any platform.
Information in this document applies to any platform
***Checked for relevance on 13-07-2011***

Goal

Under certain circumstances (DM_MIB calls), the GWADM process simply exits.
Further diagnostics show that it performs an exit(14) after having been interrupted by SIGALRM.

Solution

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