Resolution:
This issue might be due to one of the following reasons.

1. Make sure the following properties are set in your be-engine.tra file. You can see the Tangosol Cache details only if you have configured the tangosol properties in your .tra file.

# **************
#jmx settings

java.property.com.sun.management.jmxremote=true
java.property.com.sun.management.jmxremote.port=5555
java.property.com.sun.management.jmxremote.authenticate=true
java.property.tangosol.coherence.management=all
java.property.tangosol.coherence.management.remote=true

# TANGOSOL FAULT TOLERANCE
be.ft.enabled = true
be.ft.cluster.name = FT-CLUSTER-BE
#&ltinteger> < lower the number the higher the priority.>
be.ft.priority = 1


2. If you are running the BE Engine/Java process in a Windows machine, then the problem might be on the Windows Temp directory location. Please check the following URL http://java.sun.com/j2se/1.5.0/docs/guide/management/faq.html for details.

3. If you are still not able to connect your JConsole tool to the running BE engine, then try enabling the JMX properties in a simple Java process and see if you are able to connect to it. For Eg. you can run your Java process with the options below and try connecting your JConsole to it.

> Java -Dcom.sun.management.jmxremote Helloworld

Note: in this approach make sure the Helloworld test case is up an running for a while when you try to connect your JConsole utility.

4. Also please check out this following URL, in how to debug JConsole with logging features.
      http://blogs.sun.com/jmxetc/entry/troubleshooting_connection_problems_in_jconsole

Not able to connect JConsole to a JMX enabled BE engine process.