[
http://jira.jboss.com/jira/browse/JBSEAM-2340?page=all ]
Pete Muir updated JBSEAM-2340:
------------------------------
Component/s: Security
Fix Version/s: 2.0.1.GA
Assignee: Shane Bryzak
Priority: Major (was: Blocker)
Seam failure in high availability cluster deployment.
-----------------------------------------------------
Key: JBSEAM-2340
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2340
Project: JBoss Seam
Issue Type: Bug
Components: Security
Affects Versions: 2.0.0.GA
Environment: All
Reporter: Samuel Doyle
Assigned To: Shane Bryzak
Fix For: 2.0.1.GA
Seam fails when deploying into a high availability clustered environment where session
data is replicated across the cluster.
Using a memory replication based approach for high availability across the cluster
depends on session data being serializable. This issue probably has a dependency on drools
as well which is being used for security. When attempting to replicate a sessions data
across a cluster the following exception results in a failure. Here is an instance of an
exception:
#|2007-12-03T12:09:13.520-0500|INFO|sun-appserver9.1|org.apache.catalina.session.ManagerBase|_Thread
ID=22;_ThreadName=httpSSLWorkerThread-38080-1;|PWC2785: Cannot serialize session
attribute org.jboss
.seam.security.identity for session 0fba09ba81165626f5a35d7a2291
java.io.NotSerializableException:
org.drools.reteoo.ReteooWorkingMemory$WorkingMemoryReteAssertActio
n
In terms of a high availability requirement this is most definitely a show stop which is
why I tagged it as a blocker.
S.D.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira