Hello Brian and Ben,
Do you have any news regarding this session replication mechanism, regarding my last post here?
We're looking forward to your reply.
I think as long as the clustering is only used for failover, allowing a shared session to be clustered should be doable technically.
So the question is really just a policy one -- do we allow a configuration option that people can easily misuse? Personally, I think we should, and just make it clear in the docs that if a shared session is clustered, it should be for failover purposes only, not for concurrent access across servers. Most use cases of http session clustering are for failover anyway.
Ben, what do you think about this?
I am fine with it. In the clustered case, what about sso? Will they be able to share it as well?
The sso is controlled by a cookie scoped to "/", so any webapp associated with the same hostname can participate in the sso. Tomcat has added the ability to scope the cookie to an arbitrary domain (e.g. xyz.jboss.com or jboss.com or even .com), so this will greatly increase flexibility. This is still not in a stable TC release though, and won't be in JBoss until our next release after TC votes another release as stable.
Hello Ben and Brian,
Just wanted to let you know that we do not need to use an arbitrary domain. By now, we just need to use webapps associated with the same hostname. This allows them to participate in the sso, am I right?
Please let me know if the requirements are clear now as well as when this feature is going to be available.
Hi guys. Any progress on this? We really need this feature as well
Sergey L. Sundukovskiy
Sr. Director, Architecture
Hello Brian Stansberry,
May you please inform the current status of this feature implementation?
I checked the link below but nothing is being logged there and planning is not clear as well.
I'm looking forward to your reply.
Juarez Barbosa Jnr - Unisys
This is an old subject now...
Could anybody from the JBoss AS team give us some feed back on session sharing at the ear level and JIRA http://jira.jboss.com/jira/browse/JBAS-2861 ?
A month ago or so, the issue was still on JBoss 4.2.2 AS roadmap. Not any more...
Last reply for this was in 07. Is there a new status? Is this available in any way for jboss-5.1.0.GA? Is this still being worked on? https://jira.jboss.org/jira/browse/JBAS-2861 has not been updated either.
I would very much like to find a contributor to work on this, since for a loooong time now I'm not finding time to do it.
Thanks Brian for answering.
I wish I could and knew how to add that feature. In addition to being brand new to JBoss and not knowing how it all works together yet, I don't have any time available at this time. Otherwise I would volunteer. It would be a great feature to have available.
This would be important for me too.
I am working on a telecom project where we are migrating very old apps from WebSphere Mainframe to JBoss AS.
They have only a login page that sets the session for every directory (a.k.a application) in the server.
So it would be very good if i could migrate the apps and have the sessions shared, as they do in websphere, so i can migrate "as is" (we don't even have sources for most of those apps).
Is there any update on this issue? I see that it was "timed out" in JIRA....
Are you sure it is JBAS-1909?
Ops... it seems that it is now 2861 - https://issues.jboss.org/browse/JBAS-2861
The best solution i found is to modify the session manager to ignore context names.
The current problem is that this is only possible after JBoss ORG 6.0.0 M2:
And i need it on EAP 5.1.1. But i guess that is easier to solve...