[
http://jira.jboss.com/jira/browse/JBSEAM-332?page=comments#action_12341343 ]
Keith Naas commented on JBSEAM-332:
-----------------------------------
It appears to be a problem with ANY CGLIB Enhanced class being putinto the session. We
have a test case with just an Enhanced Foo object. The same error message appears in the
server log of the server we are failing over to.
{code}
2006-08-16 12:59:21,908 ERROR [org.jboss.web.tomcat.tc5.session.JBossCacheService]
[http-test1boss-1-2.cns.com%2F106.1.2.232-8080-1] loadSession(): id:
kp6baUKT714I0HrmigWOlw**exception occurred during serialization:
java.lang.ClassNotFoundException: No ClassLoaders found for:
com.biglots.sessiontest.Foo$$EnhancerByCGLIB$$8b71769a
{code}
javabeans in session are not distributable
------------------------------------------
Key: JBSEAM-332
URL:
http://jira.jboss.com/jira/browse/JBSEAM-332
Project: JBoss Seam
Issue Type: Bug
Components: Core
Environment: Seam 1.0, JBoss 4.0.4GA, Windows Server 2003, Cluster of 4 nodes on
2 machines.
Reporter: Keith Naas
Attachments: itpa.ear, itpa.ear
We have an application that makes use of JavaBeans for a lot of our JSF
"actions". When one of our nodes is brought down, the session should Seamlessly
failover to another node. The user is sent to a different node, but the entire session
appears to be in a clean state. We looked through the server logs and saw the
following:
2006-08-15 10:47:36,658 ERROR [org.jboss.web.tomcat.tc5.session.JBossCacheService]
[.......] loadSession(): id: GWrcdSJEASvXSJnX6fNHNg**exception occurred during
serialization: java.lang.ClassNotFoundException: No ClassLoaders found for:
com.ourapp.web.beans.WorksheetBean$$EnhancerByCGLIB$$bf40374c
All of our beans are Serializable, but it appears that there is an issue with the cache
sync of the CGLib proxy classes. This specific bean does have some service properties
that are transients. It also has properties that refer to other Web JavaBeans.
We will be investigating this some more, but we wanted to get this logged since it
appears to be a major issue that prevents us from clustering our Seam apps.
--
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