I'm getting rid of the passivation thread and passivation scheduling in the cache. This simplifies the cache tremendously. If I remember correctly the reason for passivation scheduling was for SFSBs being swapped in and out of disk continuously. What a stupid reason, IMHO. (Hope I don't offend anybody).
Passivation happens with SFSBs when you've reached your resource limit. Doing the passivation in a separate thread has no effect on performance on a highly loaded system. Over-engineered, IMHO. BTW, I'm reinstituting entity pooling too. Bill ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
