Hi, Running RAP on top of Glassfish-4.1.2 (JEE reference implementation) with session-failover enabled (OperationMode.SESSION_FAILOVER), Session-Timeouts occur for the second request even in case only 1 node is active in the cluster.
The issue is caused by RWTClusterSupport.markSessionChanged's call to UISessionImpl.attachToHttpSession() -> setAttribute(). Unlike Tomcat and Jetty, Glassfish fires the HttpSessionBindingListeners for setAttribute although the attribute was already stored in the session with the same key. So the currently active session receives an valueUnbound and terminates itself. The patch ignores valueUnbound events iff caused by markSessionChanged. https://bugs.eclipse.org/bugs/show_bug.cgi?id=521442 https://git.eclipse.org/r/#/c/103742/ Thank you in advance, Clemens _______________________________________________ rap-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rap-dev
