I've got a stateful EJB that maintain's a user context. It contains data that is visible to both the servlet side and the EJB side of the house. This is information that needs to be consistant across all JVMs in a clustered environment. We'd *really* prefer not to persist the info (some of it is already persisted, some of it is (expensive) business loads from CRM and accounting software, some of it is based on the phase of the moon). Using the servlet session object was great until we needed this consistant view on the EJB side. Section 6.5.6 of the EJB 1.1 spec says that concurrent access to a stateful EJB is "bad" and sure enough, I get exceptions when I try to access the EJB concurrently. The quick solution is to synchronize access to the EJB. I've done this, but it will only guranantee that only one client in a given JVM can get to the EJB. In a clustered environment I cannot gurantee serialized access and that session object can blow up at any time. Any strategies on how to handle this? Suggestions? While this requirement is fine, there are not enough tools to prevent me from shooting myself in the foot. -- -rupa =========================================================================== 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".
