How to troubleshoot EMS pending messages on Hawk topics, such as "_HAWK.;"?
Article ID: KB0089244
Updated On:
| Products | Versions |
|---|---|
| TIBCO Hawk | - |
| Not Applicable | - |
Description
Description:
EMS pending message on topics named "_HAWK.>". This kind of issue indicates that some consumers of this topics stopped consuming messages.
Issue/Introduction
How to troubleshoot EMS pending messages on Hawk topics, such as "_HAWK.;"?
Resolution
1). Start EMS Administrator Tool and login EMS as an Admin user.
2). Run the following example command and find the connection ID "Conn" of which the consumer has pending message.
show consumers topic=_HAWK.jackie574.nl.pa.p1.agent4.hb.test.yanjie-lt2 full
3). Run the following command and find the IP address(machine) of the connection ID.
show connections full
4). Remote connect to this machine and use the following command to track the process which is an EMS consumer and causes this pending message issue.
Windows Platform
netstat -nao|find "7222"
Linux Platform
lsof|grep "7222"
Here are possible processes which are blocking consumers on Hawk topics:
a). Hawk display, Hawk event service, Hawk webconsole, Hawk HTTP adapter, Hawk SNMP adapter and all other Hawk console applications.
b). RTview.
c). AppManage, AppStatusCheck, wrap and ConfigureMonitoring.
d). TIBCO Administrator.
e). RVD.
5). Restart these processes which create a TCP connection to the EMS server and check the pending messages again.
If you need further investigation about why this process stops consuming messages, contact the vendor of this process. If the pending messages persist after you restart all process related to TIBCO, contact the TIBCO Hawk Support group.
Feedback
Yes
No
Powered by
