Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Rashi Chhabra (Rashi_Chhabra)
Chhabra

Chhabra
IN
Rashi_Chhabra Member since 2017 22 posts
Chhabra
Posted: Nov 15, 2017
Last activity: Nov 16, 2017
Posted: 15 Nov 2017 0:14 EST
Last activity: 16 Nov 2017 23:51 EST
Closed

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.

To see attachments, please log in.
Dev/Designer Studio
Data Integration

Posted: 7 years ago
Posted: 15 Nov 2017 3:33 EST
Shreshta Vinayak (vinas) Technical Solutions Engineer
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

To see attachments, please log in.
Posted: 7 years ago
Posted: 15 Nov 2017 4:09 EST
Rashi Chhabra (Rashi_Chhabra)
Chhabra

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.

To see attachments, please log in.
Posted: 7 years ago
Posted: 15 Nov 2017 9:08 EST
Dilipan Venkatesan (DilipanV105)
Atos Syntel
Consultant
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.

To see attachments, please log in.
Posted: 7 years ago
Posted: 15 Nov 2017 9:52 EST
Sushant Samuel (SushantSamuel)
PEGA
Lead Service Assurance Advisor, Cloud Migrations
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-previous.pega.com/system-management-application-reference-guide-63-sp1

Regards,

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice