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

 Jeffrey Ray (JeffR210)
Mr.
Systems Architect
Mr.
US
JeffR210 Member since 2018 2 posts
Mr.
Posted: Jul 22, 2019
Last activity: Jul 23, 2019
Posted: 22 Jul 2019 10:34 EDT
Last activity: 23 Jul 2019 6:43 EDT
Closed

When running multiple Pega nodes, users are getting logged in to all nodes at once.

I have 4 Pega Nodes running behind an F5 Load Balancer. When I try to login to Pega, it appears that I'm trying to be logged into all 4 nodes at once. Of course when this happens I either get an error stating that I've been logged out for exhausting my maximum number of sessions, or I'm presented a nonfunctional Pega interface.

I receive the following stack trace in the catalina.out log on all four nodes.

Show More

I have 4 Pega Nodes running behind an F5 Load Balancer. When I try to login to Pega, it appears that I'm trying to be logged into all 4 nodes at once. Of course when this happens I either get an error stating that I've been logged out for exhausting my maximum number of sessions, or I'm presented a nonfunctional Pega interface.

I receive the following stack trace in the catalina.out log on all four nodes.

2019-07-22 13:53:15,509 [ttp-nio-8080-exec-16] [ STANDARD] [ ] [ PegaRULES:07.10] (ngineinterface.service.HttpAPI) ERROR pega.mcboss.net| Proprietary information hidden - Exception occured:
com.pega.pegarules.pub.context.PRSecurityException: Authentication Failed.
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.checkForExcessiveLoginAttempts(Authentication.java:2557) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.authentication.Authentication.doAuthentication(Authentication.java:781) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HTTPAuthenticationHandler.performAuthentication(HTTPAuthenticationHandler.java:250) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HTTPAuthenticationHandler.doHttpReqAuthentication(HTTPAuthenticationHandler.java:94) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.handleAuthentication(HttpAPI.java:2327) ~[prprivate.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.activityExecutionProlog(EngineAPI.java:576) ~[prenginext.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:415) ~[prenginext.jar:?]
at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_211]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_211]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1368) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1105) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:959) ~[prprivate.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:354) ~[prenginext.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.invoke(HttpAPI.java:855) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:251) ~[prprivate.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:278) ~[prpublic.jar:?]
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:223) ~[prpublic.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:691) ~[prwebj2ee.jar:?]
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:397) ~[prwebj2ee.jar:?]
at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_211]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_211]
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370) ~[prbootstrap-7.4.0-185.jar:7.4.0-185]
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411) ~[prbootstrap-7.4.0-185.jar:7.4.0-185]
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224) ~[prbootstrap-api-7.4.0-185.jar:7.4.0-185]
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273) ~[prbootstrap-api-7.4.0-185.jar:7.4.0-185]
at com.pega.pegarules.internal.web.servlet.WebStandardBoot.doPost(WebStandardBoot.java:129) ~[prbootstrap-api-7.4.0-185.jar:7.4.0-185]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:661) ~[servlet-api.jar:?]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:742) ~[servlet-api.jar:?]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) ~[catalina.jar:8.5.34]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.34]
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-websocket.jar:8.5.34]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) ~[catalina.jar:8.5.34]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) ~[catalina.jar:8.5.34]

***Edited by Moderator: Lochan to update platform capability tags***


Show Less
To see attachments, please log in.
Pega Platform
Data Integration
System Administration

Posted: 5 years ago
Posted: 22 Jul 2019 22:34 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Technical Support
Pegasystems Inc.
US

How is your F5 configured using Pega? Make sure cookie based session affinity is configured: https://www.f5.com/pdf/deployment-guides/tomcat-dg.pdf. Looks like you are running Pega 7.4? If you can share the fiddler trace, we can review and hopefully find some clues. 

To see attachments, please log in.
Posted: 5 years ago
Posted: 23 Jul 2019 6:43 EDT
Simon Chan (chans3)
PEGA
Senior Principal Engineer, Technical Support - 1:1 Customer Engagement
Pegasystems Inc.
GB

Looking into the server access log file. The client's IP address should stick to one server only if affinity has been configured correctly.

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