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

 Srikanth J (J Srikanth)
Common Wealth Bank
Principal Consultant
Common Wealth Bank
AU
J Srikanth Member since 2010 22 posts
Common Wealth Bank
Posted: Nov 16, 2016
Last activity: Mar 30, 2017
Posted: 16 Nov 2016 2:36 EST
Last activity: 30 Mar 2017 9:50 EDT
Closed
Solved

DSS value configured is not picking correctly

I am working on multinode evironment. In one node the DSS Value configured is picking correctly and on other node the changes are not reflecting.

Ex : i have configured xxxx value first time. Later i updated and have configured yyyyy value second time.

The system is still picking the xxxx value in one node but other node yyyy value is picking. If i clear the cache then it is picking the yyyy value other node which is having issue.

What would be the reason for this behaviour ? As both the nodes are configured to the same DB why was the DSS picking differently in both nodes ?

***Updated by Moderator: Marissa to update categories***

***Updated by moderator: Lochan to add SR details***

To see attachments, please log in.
System Administration
Support Case Created

Accepted Solution

Posted: 7 years ago
Posted: 30 Mar 2017 9:30 EDT
Srikanth J (J Srikanth)
Common Wealth Bank
Principal Consultant
Common Wealth Bank
AU

This issue is resolved as part of the SR-B36268. The issue is because of migration from 6.X to 7.X has not be done in a proper way.

To see attachments, please log in.
Posted: 8 years ago
Posted: 16 Nov 2016 21:11 EST
Srikanth J (J Srikanth)
Common Wealth Bank
Principal Consultant
Common Wealth Bank
AU

Also, i have observed that some of the D pages which are referencing to these DSS are also not getting refreshed/updated. when i tried to remove the D page  from the sma i am facing the below error.   

Show More

Also, i have observed that some of the D pages which are referencing to these DSS are also not getting refreshed/updated. when i tried to remove the D page  from the sma i am facing the below error.   

Exception during engine invocation: com.pega.pegarules.management.internal.DeclarativePageCacheManagementAPI.ClearSharedPages
java.lang.ArrayIndexOutOfBoundsException: 1
    at com.pega.pegarules.management.internal.DeclarativePageCacheManagementAPI.ClearSharedPages(DeclarativePageCacheManagementAPI.java:138)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at com.pega.pegarules.management.internal.MB2EngineAccess.invoke(MB2EngineAccess.java:169)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invoke_privact(EngineImpl.java:364)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.run(EngineImpl.java:349)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1177)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:926)
    at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:777)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:323)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
    at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:240)
    at com.pega.pegarules.management.internal.MBeanHelper.invokeOperation(MBeanHelper.java:77)

 

 


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 18 Nov 2016 1:24 EST
Habeeb Baig (BaigHabeeb)
Virtusa IT Consulting
Lead Decisioning Architect
Virtusa IT Consulting
AE

Some DSS settings require server restart after you update them, have you restarted the node where updated value yyyy?

Can you mention the DSS here?

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 20 Nov 2016 20:31 EST
Srikanth J (J Srikanth)
Common Wealth Bank
Principal Consultant
Common Wealth Bank
AU

Hi baigh,

The DSS values will be updated and set by the system when ever a soap call is happened it will update the time value into that DSS. On one node the update happened is visible and on other node the update is not getting .

when i open the dss it has the updated value and  when i wrote a test activity and verified the dss value by using show-Property. It have returned different value.  Anly clue for such behaviour ?

As i said earlier both nodes are pointing to same db and Also the pega pulse agent is up and running for every minute.

Thanks,

Srikanth J

 

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 21 Nov 2016 5:11 EST
Santanu Bhattacherjee (Santanu) Senior Manager, Cloud Engineering, Management Plane Services
Pegasystems Inc.
IN

Could be some issue with system pulse as well. Can you confirm your pulse is running properly ?

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 23 Nov 2016 8:34 EST
Santanu Bhattacherjee (Santanu) Senior Manager, Cloud Engineering, Management Plane Services
Pegasystems Inc.
IN

Hi

I think this might require some more detailed troubleshooting using some diagnostic patch or log analysis.

May be creating a service request with GCS can help further on this.

To see attachments, please log in.
Posted: 8 years ago
Posted: 24 Nov 2016 5:58 EST
Lochana Durgada Vijayakumar (Lochan_DV)
PEGA
Senior Manager, Knowledge Management
Pegasystems Inc.
IN

Hi Srikanth,

Please let us know the SR number if you create one with Pega Support.

Regards,
Lochan  |  Community Moderator  |  Pegasystems Inc.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 29 Nov 2016 17:32 EST
Leonard Francis (LEONARDF-1)
Serendebyte

Serendebyte
US

Running Pega 7.2 I am experienceing the same issues. DSS values updated on one node does not reflect updated value when retreiving the DSS value using (Pega-RULES:Utilities).getDataSystemSetting on other nodes. Pulse agent is running on all nodes.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 8 Mar 2017 20:21 EST
Ashutosh Arya (Aryaa)
PEGA
Senior Manager, Technical Support - Runtime Engine and Search
Pegasystems Inc.
AU

The issue here is not about DSS update as the DSS change gets updated fine in the pr_data_admin table and also updated value reflects on the Records --> Sysadmin --> Dynamic System Setting page (in the behavior reported node). However, when we open the rule (by clicking on the row) from this page, the rule copy which opens is stale.

 

SR-B36268 has been opened for investigating this further.

To see attachments, please log in.

Accepted Solution

Posted: 7 years ago
Posted: 30 Mar 2017 9:30 EDT
Srikanth J (J Srikanth)
Common Wealth Bank
Principal Consultant
Common Wealth Bank
AU

This issue is resolved as part of the SR-B36268. The issue is because of migration from 6.X to 7.X has not be done in a proper way.

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