According to the WebSphere doc, Option A is supported but only if you are not running clones (clusters) of the application. In the configuration for individual beans, you can set "Database access" to "exclusive" to get Option A behaviour, or set it to "shared" for Option C behaviour. Again, because the cache is not shared across JVMs or machine nodes, you can't use the "exclusive" setting unless you are running your application on a single JVM. John Zerbe - Mellon Bank Information Technology Solutions - Middleware Team Phone: 412-234-1048 E-Mail:[EMAIL PROTECTED] > -----Original Message----- > From: James Cook [SMTP:[EMAIL PROTECTED]] > Sent: Friday, September 29, 2000 11:01 AM > To: [EMAIL PROTECTED] > Subject: Re: Real-world limitations of simplistic optimistic > concurrency schemes > > I didn't realize that WebLogic and Websphere do not support Commpit Option > A as > defined by the spec. > > jim > > ========================================================================== > = > 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". =========================================================================== 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".
