Why "MDM Administration Agent" is always showing worng status for MDM instance
Article ID: KB0089365
Updated On:
| Products | Versions |
|---|---|
| TIBCO MDM | - |
| Not Applicable | - |
Description
Description:
Even though the MDM instance is up and running the Tibco MDM administration agent shows it is in the stop status.
Symptoms:
Even though the MDM instance is up and running the Tibco MDM administration agent shows it in stop status and we can also see the follwoing error in log file:
Cause:
The agent might not able to get the MDM instance details.
Even though the MDM instance is up and running the Tibco MDM administration agent shows it is in the stop status.
Symptoms:
Even though the MDM instance is up and running the Tibco MDM administration agent shows it in stop status and we can also see the follwoing error in log file:
executeTask() allLocalJvmInstances:={CustomerQA&Member1=com.tibco.mdm.agent.jmx.VMDescriptorMBeanObject@72c50b34}
20:54:42.303 [Timer-0] DEBUG c.t.m.agent.MDMServerHeartBeatPoller - start of executeObjectBuildTask()......
20:54:42.303 [Timer-0] DEBUG com.tibco.mdm.agent.util.JmxUtil - starting getMdmInstanceInfo()....
20:54:42.305 [Timer-0] DEBUG com.tibco.mdm.agent.util.JmxUtil - null check: null
20:54:42.308 [Timer-0] DEBUG com.tibco.mdm.agent.util.JmxUtil - return: error
20:54:42.308 [Timer-0] DEBUG com.tibco.mdm.agent.util.JmxUtil - ending getMdmInstanceInfo()....
20:54:42.308 [Timer-0] DEBUG c.t.m.a.MdmTeaObjectBuilderFactory - start of buildTeaObjects()
{"cluster": {
"description": "Customer 360 view",
"members": {"member": {
"name": "Member1",
"serverUrl": "http://localhost:8080",
"shutdownCmd": "C:/jboss7/bin/jboss-cli.sh --connect --command=:shutdown",
"startCmd": "C:/jboss7/bin/standalone.bat"
}},
"name": "CustomerQA"
}}
Cause:
The agent might not able to get the MDM instance details.
Issue/Introduction
Why "MDM Administration Agent" is always showing worng status for MDM instance
Resolution
One of the reasons could be that you are working on an unsupported version of MDM.
MDM Administration Agent is supported from MDM 8.3.1 HF1. If you have not applied any hotfix on top of MDM 8.3.1 you may face this issue.
Apply hotfix1.If the hotfix level is correct the following are worth checking:
1). In the mdm-agent.properties, check for the following properties:
a). tea.server.url=http://localhost:8777/tea
b). mdmserver.mqhome=C:/tibco/mdm/8.3
2). Check that the Java_HOME and classpath are set in the startMDMAgent.sh/bat file:
set PATH=C:\Java7\bin;%PATH%
export CLASSPATH=C:/tibco/mdm-agent/1.0/lib/lib/mdm-agent.jar;%CLASSPATH%
3). Check that the cluster-config.xml in MQ_HOME/config folder is set:
<member>
<name>Member1</name>
<serverUrl>http://localhost:8080</serverUrl>
<startCmd>C:/jboss7/bin/standalone.bat</startCmd>
<shutdownCmd>C:/jboss7/bin/jboss-cli.sh --connect --command=:shutdown</shutdownCmd>
</member>
Feedback
Yes
No
Powered by
