-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement clustered web-session handling #7529
Comments
got hit by Ignite bug https://issues.apache.org/jira/browse/IGNITE-11662 |
Jetty wants own classloader during deserialization. Fixed it by wrapping SessionData and controlling deerialisation. |
OSGi bundle where jetty de-serialisation happens don't import classes needed (obviously). Workaround: Dynamic-Import |
XP has distinct ports for different servlets. But only one SessionStore. This doesn't work as SessionStore instance must not be shared. Refactored to have SessionStoreFactory |
Unavailable Elasticsearch cluster (In RED state) excludes node from Ignite cluster as well. This generally means RED state of Elasticsearch varnish all data stored Inn Ignite :) |
Extracted Ignite to own activator. To be able to control it's lifecycle regardless of "cluster". For instance, don't start it on some nodes |
ClusterManager is written in a way that it tend to hang if first available Cluster is not Elasticsearch. |
JettyActivator written in a way that it start without Dispatchers. And all dynamically added ones will fail. |
Another issue deserves own bug report.in cluster application stopping/stopped events come to browsers even when only one node in a cluster stopped. This should ugly "connection lost" in ContentStudio, but actually everything is functional |
SessionWrapper was holding reference indefinitely to HttpSession leaving no room for proper handling of invalidated by timeout sessions. See how bad it is here jetty/jetty.project#3913 (comment) |
JCache now version 1.1.1 to simplify OSGi bundling |
Need to understand how WebSockets are affected jetty/jetty.project#3981 Also, probably require to update Jetty again jetty/jetty.project#3913 (Updated Jetty now #7579) |
write missing tests for the only place where okhhtp was used in production
write missing tests for the only place where okhhtp was used in production
incorporated into #7921 |
a second attempt of #6229
The text was updated successfully, but these errors were encountered: