BusinessEvents application instance can be started from TEA, but cannot be monitored in TEA
Article ID: KB0072535
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 6.x |
Description
NOTE: For clarity, the following terminology is used in this article:
In some cases, a BusinessEvents application instance can be started successfully from the TEA Server web ui, but it never shows a status of 'Started'. Instead, the instance will display a Deployment Status of 'Deployed' and will remain in a pending state for some time (~2 minutes)..
Eventually, the state will incorrectly change to Stopped, as indicated by the yellow circle icon:
However, the 'BE Log' view in the TEA Server web ui indicates that the application has successfully started and is logging messages to the console:
On the BE worker machine, the application is also shown to be running:
- BE TEA Agent machine - The machine which runs the BE TEA Agent
- BE worker machine - The BE machine that you added in the TEA Server web ui for the BusinessEvents product. This machine receives deployment requests from the BE TEA Agent machine.
In some cases, a BusinessEvents application instance can be started successfully from the TEA Server web ui, but it never shows a status of 'Started'. Instead, the instance will display a Deployment Status of 'Deployed' and will remain in a pending state for some time (~2 minutes)..
Eventually, the state will incorrectly change to Stopped, as indicated by the yellow circle icon:
However, the 'BE Log' view in the TEA Server web ui indicates that the application has successfully started and is logging messages to the console:
On the BE worker machine, the application is also shown to be running:
$ ps -aux | grep be\-engine ec2-user 1938 16.7 12.6 3008136 1009400 ? Sl 12:33 0:40 /opt/tibco/be/6.2/bin/be-engine --propFile fd_Instance0.tra -n Instance0 -c fd.cdd -u default fd.ear --propVar jmx_port=5500 --propVar jmx_host=172.31.84.74 --innerProcess
Issue/Introduction
This article describes the bad behavior that is observed in the TEA Server web ui when JMX connections are blocked between the BE TEA Agent machine and the BE Worker machine.
Environment
All Supported Platforms
Resolution
This behavior indicates that the JMX tcp port is not open on the BE worker machine. The BE TEA Agent machine needs to communicate with the application instance via this JMX port.
By default, a suggested JMX port of 5500 is used, as shown in the 'ps -aux' output shown above. This port number is configured during the PU Instance Creation step in the TEA Server web ui.
For successful monitoring of the BE application shown in the above example, inbound tcp port 5500 needs to be open on the BE worker machine. This will allow the BE TEA agent machine to connect to the BE application on that port, and report statistics/status back to the TEA Server. To ensure this port is open, consult with your IT team as needed. Multiple JMX ports will need to be open if multiple BE applications will be run on the BE worker machine. Refer to the Knowledge article "How to set unique JMX monitoring ports when running multiple inference engines" for guidance on how to manage a large number of JMX ports for BE applications.
By default, a suggested JMX port of 5500 is used, as shown in the 'ps -aux' output shown above. This port number is configured during the PU Instance Creation step in the TEA Server web ui.
For successful monitoring of the BE application shown in the above example, inbound tcp port 5500 needs to be open on the BE worker machine. This will allow the BE TEA agent machine to connect to the BE application on that port, and report statistics/status back to the TEA Server. To ensure this port is open, consult with your IT team as needed. Multiple JMX ports will need to be open if multiple BE applications will be run on the BE worker machine. Refer to the Knowledge article "How to set unique JMX monitoring ports when running multiple inference engines" for guidance on how to manage a large number of JMX ports for BE applications.
Feedback
Yes
No
Powered by
