non-serializable exceptions from oracle or anyone else kill session replication. -------------------------------------------------------------------------------- Key: JBSEAM-4595 URL: https://jira.jboss.org/jira/browse/JBSEAM-4595 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: deanhiller Priority: Critical Clustering is failing on this... 2010-03-09 11:16:29,245 ERROR [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (http-127.0.0.1-8080-6) N/A java.io.NotSerializableException: oracle.net.ns.Message11 2010-03-09 11:16:29,245 WARN [org.jboss.web.tomcat.service.session.InstantSnapshotManager./scripts] (http-127.0.0.1-8080-6) N/A Failed to replicate session xn3bf3V37OMSEzIoPBwedw__ java.lang.RuntimeException: Failure to marshal argument(s) After debugging this, we found out that oracle is throwing an exception that has a field that is not serializable which seam is storing in the conversation...(yes, we should all have all our exceptions serializable but I would not count on that to happen and fixing this should not be that bad though I am not sure why end-conversation was not working which would have helped alot!!!). 2010-03-09 11:16:28,882 INFO [net.voicelog.web.http.LogHttpReqFilter.navigation] (http-127.0.0.1-8080-3) [player][session:wedw__]key=org.jboss.seam.CONVERSATION#12$org.jboss.seam.caughtException valType=class java.lang.IllegalStateException I tried having <end-conversation> but that didn't work at all to clear the entire conversation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira