I am having a problem with the number of serilized Session Beans jboss is
creating on our server.
JBoss seems to be serializing to disk all active Session Beans every 10
minutes but does not remove any.
We have typically 50 to 100 serialized every 10 min., causing tens of
thousands of files (all in a single directory) in a few days.
I have looked through the jboss source and have found a
SessionObjectOutputStream class (as well as SessionObjectInputStream) that
refers to serializing the EJBObjects according to section 6.4.1 of the
ejb1.1 specification. (They are serialized on ejbPassivate and read back on
ejbActivate.)
The problem is that none of these files are ever removed, which creates a
huge mess.
Should the EJB container be removing the serialized files from disk after a
certain amount of time (or whenever they become invalid)?
Is this configurable?
Do I need to set up a cron job to perform removal of old serialized beans?
Vital Statistics:
JBoss version 2.2
Tomcat version 3.2.1
OS Solaris 8 (SunOS 5.8)
[...appserver/jboss/db/sessions/Inventory]:ls -C1 | wc -l
18250
Thanks for any suggestions or input!
-Sameer Nanda
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
