>Due to the fact we have no log but this OutOfMemoryError (and no monitor >tools), we can't say it's EJB's fault, but the problem started after the >cluster deploy.
we also had a problem using WL in a cluster, maybe it is similar. The performance was _really_ bad and unreliable, until we took the cluster apart and served on single machines. It turned out to be a problem with the cluster-synchronization.. Writing session data to disk, swapping EJB's in and out of memory, etc. What i'm saying is: maybe you should look at the cluster-synchronization configuration.. hope this helps, jasper v3.12 GCS/C/IT/L/MU/P d-@ s++:-- a-->+++ C++++@ UL+>+++ P+ L+(++)>++++ !E W++(+) N+ !o K?> w O- M(-) V- PS+ PE++ Y+ PGP- t+ 5+ X R+ tv- b++++ DI++++ D+(++)>+++ G>+++ e++(*)>++++ h+() r++ y+ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
