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?
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.
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