Starting with TIBCO LogLogic Log Management Intelligence (LMI) version 6.3.0, watchqueue has implemented a new page to display the wrapper status for the Advanced Features engines. For users who are unfamiliar with watchqueue command in LMI, it serves as a status check page for all the various engine wrappers that run in LMI in order to provide the functionality status to the users. In older versions of LMI prior to 6.3.0 the watchqueue page 1 listed the following Advanced Features engine wrappers and their status:
NAME STATUS HEARTBEAT AVG MAX FAILURES
engine_llzookeeper_sync RUNNING 10.000s 9.999 10.002 0/0
engine_llwebapp RUNNING 30.000s 30.001 120.014 0/0
engine_llzookeeper RUNNING 30.000s 30.001 120.019 0/0
engine_llaggregation RUNNING 30.000s 30.001 120.014 0/0
engine_llcorrelation RUNNING 30.000s 30.001 120.013 0/0
engine_llquerynode RUNNING 30.000s 30.001 120.013 0/0
engine_lldatanode RUNNING 30.000s 30.001 120.014 0/0
Starting with LMI 6.3.0 these engine wrappers have been moved to a new page 'x' (lower case).
Here is a sample output of watchqueue page x in LMI 6.3.0:
shm->currentTime = Tue Nov 26 18:11:58.807840 (1574791918)
uptime: 635999 refresh: 200 ms
ADVANCED FEATURES NODE(s)
Controlled by service engine_lldaemon
NAME PID STATUS
lmi-zookeeper pid: 16954 status: RUNNING
lmi-datanode pid: 17530 status: RUNNING
lmi-querynode pid: 25860 status: RUNNING
lmi-correlationnode pid: 17353 status: RUNNING
lmi-webapp pid: 18192 status: RUNNING
The exception to this are the following engines which still show up in page 1 output:
engine_lldaemon RUNNING 10.000s 10.001 90.091 0/0
engine_llzookeeper_sync RUNNING 10.000s 9.999 10.004 0/0
Note: In an HA cluster, these engine wrappers appear in the Master and VIP only