In your example, you were using JavaSerialization over remoting (JavaSerializationManager in your stack trace).
So, it looks this is a problem of AOP Proxy Serialization. I will try to replicate this problem on monday. (Althrough I have already used Remote Proxies on Friday. But I will update every single piece of source code I have. Maybe someone changed something) I have seen another thread about AOPProxy serialization being broken. But we still need help replicating this. If you can produce a small application that does it, you can attach it to JIRA at: http://jira.jboss.com/jira/browse/EJBTHREE-423 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923109#3923109 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923109 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
