"kill -9 TMQUEUE" Leads To All /Q To Be Restarted
(Doc ID 771632.1)
Last updated on MAY 06, 2024
Applies to:
Oracle Tuxedo - Version 8.0 and laterInformation in this document applies to any platform.
Information in this document applies to any platform
Goal
With a Tuxedo 8.0 samples/atmi/qsample sample running everything:
tmshutdown -y
Configure in ubb.sample TMQUEUE MIN=3 and TMQFORWARD MIN=2
tmloadcf
tmboot -y
kill -9 <pid of 1 TMQUEUE process>
-> wait 5 minutes (approximately 2 x SANITYSCAN)
first, the killed TMQUEUE is declared DEAD -> OK
then, the other TMQUEUE processes will be killed -> OK
finally, the TMQFORWARD processes will be killed -> OK
The ULOG with SANITYSCAN=10 seconds shows:
tperrno=16 -> TPERMERR
-> the whole /Q is down due to a kill -9 on one TMQUEUE process
Solution
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
Goal |
Solution |
References |