[
https://issues.apache.org/jira/browse/JS2-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma closed JS2-620.
-------------------------
Resolution: Later
This most likely is because Jetspeed-2 doesn't support session replication
across a cluster, only sticky sessions.
While at some time we might be looking in supporting session replication too,
for now that's not really on the radar.
> Deployment of Jetspeed Portal in Clustered environment using Websphere 6.1
> --------------------------------------------------------------------------
>
> Key: JS2-620
> URL: https://issues.apache.org/jira/browse/JS2-620
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Ajax, Profiler, PSML, SSO
> Affects Versions: 2.0-dev/cvs
> Environment: OS: Window Environment: Clustered using Websphere
> 6.1.0.3 Portal Server: Jetspeed 2
> Reporter: Mahesh Mohan
>
> I am actually trying to deploy my Jetspeed portal in a Clustered environment
> which I have created using Websphere 6.1.0.3.
> All together I have created four clones on two nodes. If just keep one clone
> running at a time, our application works
> fine. But if we bring more than one clone up at a time, for every action the
> application is redirected to the login page
> for authentication. Which means that the session is lost for every new
> request or the same is not getting replicated between all the clones.
> For session replication I am using memory to memory replication technique
> provided by webshere. The clustered environment is working fine as the same
> is tested with a simple J2ee application. But when it comes to Jetspeed,
> sesssion management is not happening in a proper way.
> I am really not sure, what's causing this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
