Announcement!
This is a notification for product news or an alert. If you have a question, please start a new discussion

INFO: Change in behaviour with Syracuse 12.14 potentially impacting external load balancers

In Syracuse versions prior to Syracuse 12.14, Sage X3 sends a "ping" request from the user browser to the server every 60 seconds to check the session status.   This behaviour was found to not be efficient nor as effective due to the changing features and functions within different browser versions, so has now been dropped from Syracuse 12.14.

Whilst this change in behaviour will not have any noticeable impact on the majority of Sage X3 users, those customers who have multiple Syracuse servers and are using an external load balancer and have turned off the Syracuse layer load balancing may then find they suddenly start seeing a lot of issues with users reporting "Fatal errors" and their sessions are destroyed even though they are active well within the Syracuse timeout.   You may also see  "wrongly directed" messages in the Syracuse LB.log file

In this case, you should ensure the external load balancer timeout is set to a value higher than the Syracuse timeout.  For example, if your Syracuse timeout is 20 minutes, your external load balancer timeout should be set to 25 minutes or more to ensure the load balancer session is not destroyed before the Syracuse session.