Question
Chhabra
IN
Last activity: 16 Nov 2017 23:51 EST
SMA Nodes missing sporadically
Hi,
We are facing issues with the nodes configured in SMA. They tend to disappear sporadically. And the reason is not known. This behavior is noticed across all environments. Can you please help us identify the root cause?
Thanks.
Pegasystems Inc.
IN
Hi Rashi,
Are all the nodes affected by this or does this affect particular nodes? Have you been able to establish/guess any pattern for the disappearing nodes? E.g. node restarts? Please give us some further details.
Thanks,
Shreshta
Chhabra
IN
We see both the patterns- some nodes go missing in SMA, and sometimes all the nodes disappear. We did notice that this usually happens after Tomcat Restarts.
Please advise.
Pegasystems Inc.
IN
Hi,
Which is the Pega Version you are using?
Also is auto discovery of node is turned on in SMA?
Thank You
Chhabra
IN
We use Pega 7.2.2
I will have to check on the auto discovery part.
Pegasystems Inc.
IN
Atos Syntel
IN
There is a Nodes.xml file which holds the configuration details of each node configured in SMA, please check if any change is happening there.
Nodes.xml can be found in SMA's Temp directory.
Pegasystems Inc.
IN
Hi,
If the com.pega.sma.tmpdir system property is not specified, SMA will proceed as follows. If there is a Nodes.xml file in the directory specified by the user.home system property, that file is used. Otherwise, the system looks for Nodes.xml in the directory specified by the javax.servlet.context.tempdir property retrieved from the ServletContext object, and creates the file there if it does not exist
You could consider externalizing the nodes.xml user specified directory instead of default tmo
For example, here are the steps needed for WebSphere 6.x, where SERVER_NAME is your server and /SYSTEM/tmp/SMA is the temporary directory.
1. Create a folder where SMA can write the Nodes.xml file and authorize it: mkdir /SYSTEM/tmp/SMA chmod 770 /SYSTEM/tmp/SMA chown ASSR1:WSCFG1 /SYSTEM/tmp/SMA
2. Set the property com.pega.sma.tmpdir on the WebSphere console. Navigate to your server: Application Servers > Servers > SERVER_NAME.
3. Open Server Infrastructure > Java and Process Management > Process Definition > Servant > Additional Properties > Java Virtual Machine. Under Generic JVM arguments, add or replace the property: –Dcom.pega.sma.tempdir=/SYSTEM/tmp/SMA
4. Recycle WebSphere and start SMA.
https://docs.pega.com/system-management-application-reference-guide-63-sp1
Regards,