Resolution:
Description:
============
Due to mis-configuration JMX monitoring applications like JConsle are not able to communicate with TIBCO BusinessEvents (BE) engine.


Environment:
==========

   o TIBCO BusinessEvents 3.x release.

   o All OS


Symptoms:
=========
When you try to use JMX monitoring applications like JConsole you can see process id of BE engine, in the list of processes but it is grayed out so you cannot select it as one of the local processes to manage.


Cause:
=====
This situation could arise if the default settings in your be-engine.tra gets over ridden by the properties at deploy/run time. Or if the BE engine process is started without the correct TRA file, where it defaults to the be-engine.tra in your BE/Bin path.



Resolution:
=========
Make sure that the following situations hold true.

1. You are always referring to the correct TRA file when starting up your engines from command/shell prompt. You can do this by making sure that the --propFile parameter to the be-engine process is used and its value points to the correct TRA file.

2. The current settings in the TRA file is not over-ridden at the later part of the TRA file, as the TRA file is read from top to bottom, if you change the values of these properties at the end of the TRA file, then you may see different behavior.

3. Make sure that at the minimum, the following properties are mentioned in your TRA file.

java.property.com.sun.management.jmxremote=true
java.property.com.sun.management.jmxremote.port 34003

Add these properties for monitoring Coherence Parameters

java.property.tangosol.coherence.management=all
java.property.tangosol.coherence.management.remote=true



References:
==========

TIBCO BusinessEvents Users Guide.

Unable to connect from a Remote machine to the Java Management Extension (JMX) port, configured in TIBCO BusinessEvents (BE) engine.