Hi, We have a stateful session bean, and we have deployed it in JBoss 3.2.5 AS. We have noticed that when the server tries to passivate the bean, it tires to serialize the bean (and it's instance variables) to the file system. Some of our instance variables are not serializable and hence we are getting a NotSerializableException during bean passivation.
Why does the server try to serialize the bean to the file system? Can it not store in any other secondary storage, like a cache? What will be the down side of having it that way? Thanks, Kalyan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860836#3860836 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860836 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
