Description:
When starting a TIBCO ActiveMatrix (AMX) application from the AMX Administrator, the application state stays in the starting state and "Waiting on dependecy... implementation type "null"" can be seen in the node log.

TIBCO ActiveMatrix application remains in starting state with "Waiting on dependecy... implementation type "null"" seen in node log.

At runtime node, ComponentFrameworkTask and ComponentFrameworkDelegate threads are used to perform life cycle actions for AMX components. With the above symptom, a user may capture a few thread dumps on the node and analysis the stacks for these two threads. For example, a constant thread stack like the following indicates the AMX application is not able to get a MQ JMS connection. A user may need to check the connectivity between the client machine to MQ Server to see if there is any problem.

 "ComponentFrameworkDelegate" daemon prio=10 tid=0x00007f072c3e8800 nid=0x4c11 runnable [0x00007f0770736000]
    java.lang.Thread.State: RUNNABLE
     at java.net.SocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(Unknown Source)
    at java.net.SocketInputStream.read(Unknown Source)
    at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.receive(RemoteTCPConnection.java:1324)
    at com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.receiveTSH(RemoteConnection.java:2770)
    at com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.initSess(RemoteConnection.java:1399)
    at com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.connect(RemoteConnection.java:1078)
- locked <0x0000000664237058> (a com.ibm.mq.jmqi.remote.internal.system.RemoteConnection$ConnectionMutex)
    at com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool.getConnection(RemoteConnectionPool.java:338)
     at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:1488)
    at com.ibm.msg.client.wmq.internal.WMQConnection.<init>(WMQConnection.java:336)
    at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection(WMQConnectionFactory.java:6807)
    at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6204)

For AMX Platform 3.2.0 and early versions, the user can capture thread dumps by executing the following.

kill -3 <Node_PID>

Thread dumps can be found from node-stdout.log of the TIBCO Host instance.

For AMX Platform 3.3.0 and later, it is possible to capture threads through the TIBCO AMX Administrator GUI and tibcohost commands. Refer to the documentation of the applicable product for details. If further assistance is needed, contact TIBCO Support with a detailed problem description. Add the following material. 

- Complete logs from both Administrator and Runtime hosts and nodes.
- Thread dumps captured following the instructions above .
- Saved page from Administrator viewaction http://<host>:<port>/amxadministrator/viewaction.jsp .