| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 2181678.1 : IMF "Apply Changes" Action Reaches its Timeout Without The Changes are Applied and Action Status displays "Pending"
Apply Changes does not complete needed actions. The action reaches its timeout and the status returned after the time out is "Pending", showing that no changes were applied. In this Document
Created from <SR 3-13311014585> Applies to:Oracle Communications Performance Intelligence Center (PIC) Software - Version 10.1.5 and laterInformation in this document applies to any platform. SymptomsThe Apply Changes fails on IMF systems. CauseIn this case check first whether jmx agent is running on the system. The result should look like this: [root@IMF-1A ~]# ps -ef | grep jmx
root 7393 7316 0 15:51 pts/0 00:00:00 grep jmx cfguser 15371 6620 0 Sep09 ? 00:00:00 /bin/sh /opt/TKLCjmxagent/bin/startJmxAgentXmf.sh cfguser 15372 15371 0 Sep09 ? 00:00:00 /bin/sh /opt/TKLCjmxagent/bin/startJmxAgentXmf.sh cfguser 15373 15371 0 Sep09 ? 00:00:02 circAdd /tekelec/TKLCmf/runtime/run/proc/jmx_agent.log cfguser 15410 15372 0 Sep09 ? 00:00:00 /bin/bash /opt/TKLCjmxagent/bin/jmxagent -Dmysql.port=15616 -Dplat.function=IMF -Ddesig=1A root 15414 15410 0 Sep09 ? 00:00:00 sudo /opt/TKLCjmxagent/bin/jmxagentrun -Dmysql.port=15616 -Dplat.function=IMF -Ddesig=1A root 15415 15414 0 Sep09 ? 00:13:12 /etc/alternatives/java -Djava.awt.headless=true -Dweblogic.corba.client.bidir=true -Dcom.steleus.jmx.home=/opt/TKLCjmxagent -Dcom.steleus.jmx.log=/var/TKLC/log/jmxagent -Dmysql.port=15616 -Dplat.function=IMF -Ddesig=1A -cp /opt/TKLCjmxagent/jar/com.steleus.jmx.jar com.steleus.jmx.Agent When the "Apply changes" action is launched, open the jmx_agent.log display in real time to verify whether there are currently actions related to the Apply Changes: [root@IMF-1A ~]# cf.follow -15 jmx_agent.log | grep –v Sending
(The option -v Sending is to avoid having a huge number of alarm messages displayed.) If:
It means that the jmx connection is stuck and unusable for Apply Changes operations management.
Another check to be done is to verify the good status of xMF/NSP connection. It is essential to guarantee the operation can be completed correctly. Below, the command to launch analyze_subsystem (as cfguser) and a correct result. In case of wrong communication with the NSP, this point will have to be identified and fixed. [cfguser@IMF0101-1A ~]$ analyze_subsystem.sh
----------------------------------------------------- cfguser@yellow-1b's password: 04:11:24: STARTING HEALTHCHECK PROCEDURE - SYSCHECK=0
SolutionIf the issue comes from jmx side, restarting the jmx agent will release the connection. Connect on IMF as cfguser and launch: pm.kill jmx_agent.log
Launch the "Apply changes" from NSP GUI and check jmx_agent log to verify whether operations are managed. This must be done on all IMF.
Attachments This solution has no attachment |
||||||||||||||||
|
||||||||||||||||