Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

HA system throwing NullPointer Exception on click of Logoff link

SA-30695

Summary



User has implemented High Availability changes in our application following the High Availability guide.

User has web servers placed in-between the load balancer and app servers. There are one to many mapping between web and app servers. After implementing High Availability changes, we are able to achieve HA features, user is able to do a rolling restart without any outages).

However, when users click on the log off link in the screen one can see some null pointer exception on the screen. See error messages for details.


Error Messages



2016-11-08 10:51:13,301 [ WebContainer : 0] [ STANDARD] [ ] [ REImp:02.01.01] (ngineinterface.service.HttpAPI) ERROR <ip1>|<ip2>- : java.lang.NullPointerException
java.lang.NullPointerException
at com.pega.pegarules.session.internal.mgmt.util.URLAccessUtil.validate(URLAccessUtil.java:103)
at com.pega.pegarules.session.internal.mgmt.util.URLAccessUtil.validate(URLAccessUtil.java:69)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.handleWhiteListParameters(HttpAPI.java:5279)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:545)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:382)
......


Steps to Reproduce



1) Implement High Availability changes in Pega 7.1.7 application as per High Availability Guide
2) Log in as Non Quiesce admin user into one of the application servers
3) Click on "Begin Quiesce" button in SMA. After Quiesce is completed, we see that the logged in requestor session is being moved from Quiesce node to active server node and user is able to perform all the required operations. This is working as expected.
4) Click on log off button. User is seeing Null pointer exception as shown above.


Root Cause



A defect in Pegasystems’ code or rules. The fix is to expire exile requestor cookie.

Resolution



Apply HFix-30603.

 

Suggest Edit

Published December 14, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us