I had the same problem. This happens when a stateful session bean has been passivated and the serialized form of the bean is removed from the passivation store.
The quick fix is to edit the standardjboss.xml file. In the <container-configuration> element for the Standard Stateful SessionBean, there is a <container-cache-conf> element. Change the value of <max-bean-life> from the default of 1800 to 2147483647. This will guarantee that the .ser file for all stateful session beans will not be deleted until they bean is redeployed. I just picked 2147483647 b/c it's the max value of a Java integer, any large number will do. Jason Gerard Lead Software Engineer ReClaim, LLC 904-731-1998 www.reclaimopl.com Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the Health Insurance Portability and Accountability Act of 1996 or other legal sanction. The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalty. ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
