Hi, The stack trace is weird, it shows an interruption during logging. Doesn't make a lot of sense.
Regarding your architecture, it does make sense to some degree, although you are still sharing network resources for actual replication (bandwidth), etc. So you may be over-engineering things a bit, I would have started with just 2 caches (a replicated one and a local one) until you know for sure that there is contention on shared resources. When using pessimistic locking, locks are per-node so there won't be contention for different entities, as long as they are spread well across the tree structure. Also, I have just tagged 2.2.1.GA and this should be released today - this has some serialization-related performance enhancements that you may find interesting, as well as a faster JGroups library. Also, I'd like to add, have you tried 3.0.0.CR1 with MVCC? It is significantly faster and conceptually more stable than either pessimistic or optimistic locking. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183421#4183421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4183421 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
