Bill,
yes, I read your answers. I really appreciate them. I'm already doing everything you mentioned (read-only methods etc.). My guts say, that the weblogic default setting is, what you usually would expect. (10K$/CPU and no concurrent access would be too bad). Bad performance is still better than having no concurrent access to entity beans. Cheers Georg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bill Burke Sent: Friday, September 13, 2002 22:51 To: [EMAIL PROTECTED] Subject: RE: [JBoss-dev] [ jboss-Bugs-600435 ] deadlock detected erroneously Georg, Georg, Georg.... Did you read my last response to this? 1. You can declare beans read-only. There will be no pessimistic locking. 2. If the bean isn't entirely read-only, you can mark your read-only methods, and read-only methods will not cause a pessimistic lock. Yes, even with the above, this is SERIALIZED transaction isolation, but at the app-server level. Without pessimistic locking, we can't do caching because Entity beans are not required to be java.io.Serializable. If they were, we could copy beans from cache and do cache-versioning tricks. So, you can use Instance Per Transaction to avoid all transactional locking as you are right now. The downside to this is that you are required to use commit 'B' or 'C'. BTW, weblogic uses Instance Per Transaction and commit 'C' by default. Bill ...other messages deleted... ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
