Tuxedo 9.1 "tmshutdown -g GWGRP" Command Appears Successful But GWTDOMAIN Remains.
(Doc ID 1321280.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle Tuxedo - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
Shut down and reboot Tuxedo domain gateway and the connections being established will not receive data from Tuxedo environments that have remained running.
It was found that the GWTDOMAIN, which was shutdown with a "tmshutdown -g GWGRPNAME" command, did not shutdown even though the command appeared to execute successfully. This original GWTDOMAIN appears to be hung. External gateways continue to try to make connections to this non-responsive GWTDOMAIN and the duplicate GWTDOMAIN which was booted is not used.
Domain Configuration CONNECTION_POLICY is required to be ON_DEMAND. Several GWADM/GWTDOMAIN pairs are configured. Multiple failover network addressing is used and remote domains manually executing the "dmadmin connect" command is an expected administrative responsibility. Connection failure messages in the ULOG is normal.
Changes
Migrated from Tuxedo 8.1 to Tuxedo 9.1 release.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |