Endevor WebUI crashes back to the log on screen
Article ID: 399636
Updated On:
Products
Issue/Introduction
A sysplex with Tomcat running on each Lpar - Endevor Web Services and Web Interface reside in the same Tomcat, HA is enabled for Tomcat using DVIPA.
User can log onto the Endevor WebUI and select packages but after a few random packages (and random time lapse), user get bounced back to the log on page.
From the WebUI log
2025-05-13 08:10:52.410 ERROR [http-nio-host-port-exec-3] (com.broadcom.endevor.webinterface.exception.EWIException:34) session does not exist, re-authenticate and try again
2025-05-13 08:10:52.412 ERROR [http-nio-host-port-exec-3] (com.broadcom.endevor.webinterface.exception.EWIException:41) java.lang.Exception
Environment
Endevor V19
Endevor Web Interface Version: v1.2.15
Endevor Web Services API version 2.23
Cause
On login into Endevor WebUI, it creates JSESSIONID cookie which binds to a specific WebUI instance/address space. With the current DVIPA routing (by default dvipa does round robin load balancing), it switches to another instance of EWI where the session cookie from the first instance is not valid. For EWI application it's important to establish application affinity when it has HA configuration with DVIPA. In other words, the client who started connection to the EWI, always should connect to the same application in order to keep the same session.
Resolution
Split the Web Services and WebUI applications:
- Endevor web services Tomcat in HA mode, keep it as it is, on the same DVIPA.
- Endevor web interface Tomcat in HA mode, on a separate DVIPA with TIMEDAFFINITY (30 seconds or 60 seconds)
Workaround:
- As an alternative solution, Endevor Web Interface could be moved to a single Tomcat if HA is not required for it.
Additional Information
From IBM document:
The TIMEDAFFINITY parameter on the VIPADISTRIBUTE statement indicates to sysplex distributor that connections to a particular distributed DVIPA need to take into account the client origin. Connections from the same client, as identified by IP address, need to be routed to the same server instance, even when multiple server instances are hosted by a single target stack.
If a nonzero value for the TIMEDAFFINITY parameter is specified on a VIPADISTRIBUTE statement, the first connection from a particular client is routed as normal to a target stack and listening application. At that time, both the sysplex distributor routing stack and the target stack establish an affinity to govern subsequent connection requests from the same client. This affinity maintains a connection count, initially one. As subsequent connection requests for the same distributed DVIPA and port come in from the same client IP address, they are routed to the same server instance and the affinity connection count is incremented. As affinity-based connections, including the first one, are closed, the connection count is decremented.
When the last existing connection is closed and the count gets to zero, a timer of the duration (in seconds) specified by the TIMEDAFFINITY parameter is started. If another connection request is received from the same client to the same distributed DVIPA and port, the timer is stopped and the connection request is routed to the designated server instance. If no connection request is received from that client for the designated distributed DVIPA and port before the timer expires, the affinity is removed from the sysplex distributor routing and target stacks. The next connection request from that client for the distributed DVIPA and port will be routed according to normal sysplex distributor considerations of relative capacity and policies.
Feedback
